https://bugs.winehq.org/show_bug.cgi?id=45092
Bug ID: 45092 Summary: Crash to Powerr Off Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: drazil.tembero@gmail.com Distribution: ---
I have been experiencing a problem with graphical applications run under wine switching my computer off.
Haha, where to elaborate. 3d Graphical applications native to linux run perfectly, perpetually for me, or at least not a timeframe I can measure. However should I run (even a multi-platform) graphical application from wine (on any wine version or linux distribution) the computer will switch off (dead). This does however even apply to graphical applications run under virtualbox i.e. dos games 2D or 3D. Graphics work properly & perpetually from a dual-boot into windows.
My graphics card is an AMD R7 series, it has been fairly hammered by usage, also the fan although working has a severed cable, this is the reason for my assumption to a graphics issue between application software and driver software. I can only presume that the fan cable maybe a speed or temperature monitor and although windows or linux native has an override or failsafe for missing hardware communications, emulators have no such fallback.
I do however believe that this was not an issue with wine under kubuntu 17.04, although on a fresh install of 14.04 with wine 1.6, this event is occurring now. In addition just notably now this occurs ripping a movie from dvd, although not on a playback (LOTR extended is fine).
Thans in advance for any measure of assistance
Kind Regards
Basil Dazz
https://bugs.winehq.org/show_bug.cgi?id=45092
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Since virtualbox too is affected, I assume it's a driver bug, not a wine bug. Wine shouldn't be able to accidentally switch the computer off.
If I were you, I'd gather information about the crash - linux does have logging for that case.
https://bugs.winehq.org/show_bug.cgi?id=45092
--- Comment #2 from dragon on the razil drazil.tembero@gmail.com --- OK I had a little scan through through the kern.log in /var/logs. It seems that through running Vbox and the crash occurs, one of the final entries is [138987.399366] radeon_dp_aux_transfer_native: 32 callbacks suppressed.
Through a bit of googling there is a similar occurence, https://bugs.freedesktop.org/show_bug.cgi?id=103726, although mine literally is akin to pulling the power plug. This other occurence decribes the problem as occurring after a GPU reset command was removed from the kernel very recently, also explaining why I did not find the problem imediately after my 'little hardware incident'.
Wine however does not output to this log, I cannot verify this sequence of events, although I can easily reproduce the scenario. It would seem to happen quicker with hardware intensive programs, further suggesting a control circuit.
Thanks for the correspondence, given the unique nature of the hardware degradation, I doubt anyone will miss out on solution escaping to the ether, let's hope I can go without second breakfast this month and maybe there's a commercial solution.
https://bugs.winehq.org/show_bug.cgi?id=45092
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #3 from joaopa jeremielapuree@yahoo.fr --- Driver bug. Can an administrator close this bug as NOTOURBUG?
https://bugs.winehq.org/show_bug.cgi?id=45092
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|NEEDINFO |CLOSED
--- Comment #4 from Jeff Zaroyko jeffz@jeffz.name --- If you can still reproduce this issue with latest drivers for the same setup, then file a bug upstream. It is typically not something wine can resolve as it lays outside the project.
https://bugs.winehq.org/show_bug.cgi?id=45092
--- Comment #5 from dragon on the razil drazil.tembero@gmail.com --- Over further time the issue resolved to being a problem with the solder, melting with heat and retracting from the contacts on the graphics card chip. This had however proved that Wine runs a graphics card a few degrees hotter, as the problem was to occur more slowly on the windows dual boot.
https://bugs.winehq.org/show_bug.cgi?id=45092
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Resolution|NOTOURBUG |INVALID
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello folks,
resolution 'NOTOURBUG' is certainly not appropriate here. OP had broken/dying hardware. No (upstream) software problem.
Regards
https://bugs.winehq.org/show_bug.cgi?id=45092
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal Summary|Crash to Powerr Off |Running various software | |causes computer crash/power | |off (hardware problem, | |broken AMD R7 series | |graphics card)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla