| Summary: | Wine games crash with r300 gallium (r300_get_swizzle_combined+0x21) | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | demon <demon> |
| Component: | Drivers/Gallium/r300 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Log
Log 2 Backtrace of a crash - mesa compiled with debugging Another backtrace Zuma backtrace |
||
Zuma DeLuxe (besides Star Trek Armada 2) also crashes. Created attachment 39901 [details]
Log 2
I've been playing Zuma Deluxe over here and I don't get any crashes. Well, my wine crash, obviously. If I use classic driver, they work just fine. Is there any way I can make more useful data? Please compile Mesa from git with --enable-debug and post the backtrace you will get. It should contain more information than is in your logs. Created attachment 39915 [details]
Backtrace of a crash - mesa compiled with debugging
Created attachment 39916 [details]
Another backtrace
I don't know if this can, it's a backtrace from another game. It isn't the same as with other games...
These are the compilation flags:
./autogen.sh --prefix=/usr \
--with-dri-driverdir=/usr/lib/xorg/modules/dri \
--with-dri-drivers=swrast,radeon,r200,r300,r600 \
--with-state-trackers=dri,egl,glx \
--with-egl-platforms=x11,drm \
--enable-glx-tls \
--with-driver=dri \
--enable-gles1 \
--enable-gles2 \
--enable-gles-overlay \
--enable-xcb \
--enable-glx-tls \
--disable-glut \
--enable-gallium-llvm \
--enable-gallium-swrast \
--enable-gallium-radeon \
--enable-gallium-r600 \
--enable-debug || return 1
The logs are not backtraces. A backtrace is actually a call stack. r300_get_swizzle_combined+0x21 is the first line of it. Could you possibly use this HOWTO to get the whole backtrace? http://wiki.winehq.org/Backtraces Created attachment 39924 [details]
Zuma backtrace
I'm sorry, this is everything I could get. I know it's not the thing you need. But I tried following that HOWTO without success.
Is this issue still present with the current Mesa master branch? Hi Marek. I've switched to r600 card in the meantime, so I can not give any further details. Sorry. Because nobody else can reproduce this bug, I am closing it. Feel free to reopen it if you test r300g again and the issue is still present. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 39900 [details] Log ...and it works just fine with classic driver, so I woukd say it's a bug in gallium driver, not in game itself or in wine.