http://bugs.winehq.org/show_bug.cgi?id=31800
Bug #: 31800 Summary: DirectX games crash in r300_dri.so with Gallium Product: Wine Version: 1.5.13 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: rene.kijewski@fu-berlin.de Classification: Unclassified
Created attachment 41832 --> http://bugs.winehq.org/attachment.cgi?id=41832 WINEDEBUG=+relay,-debug backtrace
I cannot run DirectX games since I switched to the "xorg-edgers" PPA, with uses bleeding edge Xserver/Mesa packages and employs the Gallium renderer for my Radeon Xpress 200M card. The debug traces show that crash happens in r300_dri.so code: "Unhandled exception: page fault on read access to 0x74dd3598 in 32-bit code (0x7d10623a)."
Repeatable: always. System: Ubuntu Precise using x64 on a Samsung R40 laptop Wine: Self-built, newest tag (1.5.13), with C(XX)FLAGS = -g3 -ggdb -O0
http://bugs.winehq.org/show_bug.cgi?id=31800
--- Comment #1 from René Kijewski rene.kijewski@fu-berlin.de 2012-09-25 19:23:04 CDT --- Created attachment 41833 --> http://bugs.winehq.org/attachment.cgi?id=41833 glxinfo output
http://bugs.winehq.org/show_bug.cgi?id=31800
--- Comment #2 from René Kijewski rene.kijewski@fu-berlin.de 2012-09-25 19:24:31 CDT --- Created attachment 41834 --> http://bugs.winehq.org/attachment.cgi?id=41834 es2_info output
http://bugs.winehq.org/show_bug.cgi?id=31800
--- Comment #3 from René Kijewski rene.kijewski@fu-berlin.de 2012-09-25 19:25:43 CDT --- Created attachment 41835 --> http://bugs.winehq.org/attachment.cgi?id=41835 lspci output
http://bugs.winehq.org/show_bug.cgi?id=31800
--- Comment #4 from René Kijewski rene.kijewski@fu-berlin.de 2012-09-25 19:27:17 CDT --- Created attachment 41836 --> http://bugs.winehq.org/attachment.cgi?id=41836 Xorg.log
http://bugs.winehq.org/show_bug.cgi?id=31800
--- Comment #5 from René Kijewski rene.kijewski@fu-berlin.de 2012-09-25 19:30:10 CDT --- Created attachment 41837 --> http://bugs.winehq.org/attachment.cgi?id=41837 /proc/iomem
http://bugs.winehq.org/show_bug.cgi?id=31800
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #6 from joaopa jeremielapuree@yahoo.fr 2012-09-25 20:04:15 CDT --- The driver should not crash. Bug in driver => This bug can be closed as INVALID.
http://bugs.winehq.org/show_bug.cgi?id=31800
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #7 from Dan Kegel dank@kegel.com 2012-09-25 20:38:57 CDT --- You might want to file this bug with xorg-edgers.
http://bugs.winehq.org/show_bug.cgi?id=31800
René Kijewski rene.kijewski@fu-berlin.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #8 from René Kijewski rene.kijewski@fu-berlin.de 2012-09-25 20:43:05 CDT --- I wasn't sure whom to inform. I thought Wine might be the one responsible, since no other application manages to trigger the segfault. I'll file a bug at freedesktop.org.
http://bugs.winehq.org/show_bug.cgi?id=31800
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |UPSTREAM
--- Comment #9 from Austin English austinenglish@gmail.com 2012-09-25 21:22:24 CDT --- Driver bugs are UPSTREAM, not INVALID.
http://bugs.winehq.org/show_bug.cgi?id=31800
--- Comment #10 from Henri Verbeet hverbeet@gmail.com 2012-09-26 05:18:42 CDT --- (In reply to comment #8)
I wasn't sure whom to inform. I thought Wine might be the one responsible, since no other application manages to trigger the segfault. I'll file a bug at freedesktop.org.
It's not always easy to tell, but as a general rule, if the backtrace starts inside the driver, file the bug at the freedesktop.org bug tracker first. (Your backtrace is also missing debug symbols for the driver, you'll want to install those before filing a bug a fd.o.)
http://bugs.winehq.org/show_bug.cgi?id=31800
--- Comment #11 from René Kijewski rene.kijewski@fu-berlin.de 2012-09-26 06:23:34 CDT --- One last comment (if someone find this bug by googling):
I noticed the strangest thing right now: I can play [1] if and only if I use WINEDEBUG=+relay,-debug, and then only if I don't pipe the output into /dev/null. I.e. I use 2>&1 >/dev/null the same error occurs, but if I pipe the trace into /dev/urandom, Caesar 3 works. Other games are still affected, though.
[1]: http://www.gog.com/en/gamecard/caesar_3
https://bugs.winehq.org/show_bug.cgi?id=31800
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=31800
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #13 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Sorry for the spam.
-
wine-bugs＠winehq.org