Created attachment 99013 [details] /sys/class/drm/card0/error I am experiencing hangs while browsing on the new WebGL version of Google Maps or even browsing http://get.webgl.org/ using Chromium. Versions involved are: xorg-server: 1.15.1 xf86-video-intel: 2.99.911 mesa: 10.1.3 chromium: 34.0.1847.132 dmesg reads: [ 254.743750] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 254.743758] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 254.743760] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 254.743761] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 254.743762] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 254.743763] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 259.744595] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 280.756142] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring [ 328.768255] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring /sys/class/drm/card0/error is attached. I also get a backtrace in my journal: May 14 09:10:37 dain slim[461]: (EE) [mi] EQ overflow continuing. 200 events have been dropped. May 14 09:10:37 dain slim[461]: (EE) May 14 09:10:37 dain slim[461]: (EE) Backtrace: May 14 09:10:37 dain slim[461]: (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x57c858] May 14 09:10:37 dain slim[461]: (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x44d0d2] May 14 09:10:37 dain slim[461]: (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f58d9400000+0x5a1d) [0x7f58d9405a1d] May 14 09:10:37 dain slim[461]: (EE) 3: /usr/bin/X (0x400000+0x72a08) [0x472a08] May 14 09:10:37 dain slim[461]: (EE) 4: /usr/bin/X (0x400000+0x9aabd) [0x49aabd] May 14 09:10:37 dain slim[461]: (EE) 5: /lib64/libpthread.so.0 (0x7f58dd9ee000+0xf540) [0x7f58dd9fd540] May 14 09:10:37 dain slim[461]: (EE) 6: /usr/bin/X (0x400000+0x180680) [0x580680] May 14 09:10:37 dain slim[461]: (EE) 7: /lib64/libpthread.so.0 (0x7f58dd9ee000+0xf540) [0x7f58dd9fd540] May 14 09:10:37 dain slim[461]: (EE) 8: /lib64/libc.so.6 (ioctl+0x7) [0x7f58dc32f6f7] May 14 09:10:37 dain slim[461]: (EE) 9: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f58dac19000+0x22a5c) [0x7f58dac3ba5c] May 14 09:10:37 dain slim[461]: (EE) 10: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f58dac19000+0x2b3bc) [0x7f58dac443bc] May 14 09:10:37 dain slim[461]: (EE) 11: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f58dac19000+0x38c5d) [0x7f58dac51c5d] May 14 09:10:37 dain slim[461]: (EE) 12: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f58dac19000+0x43f7b) [0x7f58dac5cf7b] May 14 09:10:37 dain slim[461]: (EE) 13: /usr/bin/X (0x400000+0x16da33) [0x56da33] May 14 09:10:37 dain slim[461]: (EE) 14: /usr/bin/X (0x400000+0xbf5a5) [0x4bf5a5] May 14 09:10:37 dain slim[461]: (EE) 15: /usr/bin/X (0x400000+0xce1dc) [0x4ce1dc] May 14 09:10:37 dain slim[461]: (EE) 16: /usr/bin/X (0x400000+0xcf1c8) [0x4cf1c8] May 14 09:10:37 dain slim[461]: (EE) 17: /usr/bin/X (0x400000+0x3645e) [0x43645e] May 14 09:10:37 dain slim[461]: (EE) 18: /usr/bin/X (0x400000+0x3a29a) [0x43a29a] May 14 09:10:37 dain slim[461]: (EE) 19: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f58dc272ad5] May 14 09:10:37 dain slim[461]: (EE) 20: /usr/bin/X (0x400000+0x25a3e) [0x425a3e]
It reports both pipes as off. Do you have the complete dmesg and Xorg.0.log? I suspect it is more likely a failure in the error capture, but if not, it would definitely cause the hang.
I will attach Xorg.0.log, dmesg and the systemd journal from *another instance* of this happening.
Created attachment 99019 [details] Xorg.0.log
Created attachment 99020 [details] dmesg
Created attachment 99021 [details] /sys/class/drm/card0/error
Created attachment 99022 [details] systemd journal
Any news on this? As it turns out, this not only happens with WebGL, but also on other websites. I mostly use Chrome and xterm on this machine, so I'm not sure if this also happens with other programs.
this happens with glamor enabled and disabled.
Chrome does not trigger this error any more. I think they are using software rendering on my machine now or have disabled webgl entirely. Also, no one cares.
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.