| Bug ID | 88968 |
|---|---|
| Summary | Unit mouseover in World of Warcraft (wine, D3D) freezes up the entire system |
| Product | Mesa |
| Version | git |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | rubykuby@gmail.com |
| QA Contact | dri-devel@lists.freedesktop.org |
I'm not sure if I selected all the right bug tracker things, or whether this is a Mesa or X11 bug. I have an AMD Radeon HD 7950, which is practically identical to the R9 280. When running World of Warcraft in wine, everything works fine until I mouseover a unit. This mouseover should trigger a glow effect around the unit, but instead freezes up the entire system, forcing me to reboot. This bug does not occur in standard Ubuntu 14.10. It does occur in Ubuntu 14.10 with the oibaf/graphics-drivers PPA added. It also occurs in Manjaro 0.9. Ubuntu 14.10 versions: libgl1-mesa-glx - 10.3.0-0ubuntu3 xserver-xorg-video-ati - 1:7.4.0-2ubuntu2 Oibaf versions: mesa - 10.5~git1502040730.6fd4a6~gd~u xserver-xorg-video-ati - 1:7.5.99+git1501140731.c80ea1~gd~u Manjaro 0.9 versions: mesa - 10.4.3-1 xf86-video-ati - 1:7.5.0-1 This bug does not occur when turning on the OpenGL mode within WoW. This bug does not occur in the Catalyst drivers. I do not know how to gather debug information, but I'd be glad to provide them if given instructions.
So it seems like it's a regression between Mesa 10.3 and 10.4.= Any chance you could bisect between those?
A web search for "git bisect howto" should get you s= tarted.
Nailed down the bug to commit 1f6c0b55df9f3553b18062ad2c7e2dc0=
21d4c731:
radeonsi: set number of userdata SGPRs of GS copy shader to 4
It only needs the constant buffer with clip planes and read-write resou=
rces
for the GS->VS ring and streamout. That's 2 pointers.
Reviewed-by: Michel D=C3=A4nzer <michel.daenzer@amd.com>
The commit before that commit (68d36c0bb532987db27a596408e0326f20ca0365) do=
es
not crash and burn.
Used the following configure command for each build:
./autogen.sh --prefix=3D/usr/local \
--sysconfdir=3D/etc \
--with-dri-driverdir=3D/usr/lib/xorg/modules/dri \
--with-gallium-drivers=3Dr300,r600,radeonsi,nouveau,svga,swr=
ast \
--with-dri-drivers=3Di915,i965,r200,radeon,nouveau,swrast \
--with-egl-platforms=3Dx11,drm,wayland \
--disable-xvmc \
--enable-llvm-shared-libs \
--enable-egl \
--enable-gbm \
--enable-gallium-llvm \
--enable-shared-glapi \
--enable-glx \
--enable-glx-tls \
--enable-dri \
--enable-osmesa \
--enable-gles1 \
--enable-gles2 \
--enable-texture-float \
--enable-xa \
--enable-vdpau \
--enable-omx \
--enable-nine \
--enable-opencl \
--enable-opencl-icd \
--with-clang-libdir=3D/usr/lib
Followed by make and make install.
Running on Arch Linux currently, with the following package versions:
xorg-server - 1.16.4-1
xf86-video-ati - 1:7.5.0-1
linux - 3.18.6-1
This bug is no longer reproducible on my system. Two variables have changed: I'm now running Mesa 10.4.6 (small point update) & WoW has had an update to version 6.1.
(In reply to rubykuby from comment #5) > This bug is no longer reproducible on my system.= Two variables have changed: >=20 > I'm now running Mesa 10.4.6 (small point update) & WoW has had an = update to > version 6.1. So can I close this?
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | FIXED |
Closing. Please reopen if you still get the freezes.