Created attachment 100831 [details] Content of /sys/class/drm/card0/error after hang Hi, from time to time i'm noticing GPU freezes / hangs on Ubuntu 14.04 which needs a switch to the tty1 and a restart of the whole system. According to the pasted entries in the kernel.log below i should report a bug in here. Specs: Thinkpad T410s Ubuntu 14.04 64bit lspci -v output: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21c1 Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at f2000000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] I/O ports at 1800 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 kernel.log entries: [drm] stuck on render ring [drm] GPU crash dump saved to /sys/class/drm/card0/error [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xca83000 ctx 0) at 0xca83344 [drm] stuck on render ring Watchdog[21201]: segfault at 0 ip 00007f88b906cb88 sp 00007f88a9e2c720 error 6 in libcontent.so[7f88b8908000+fd7000] [drm] stuck on render ring Watchdog[23966]: segfault at 0 ip 00007f4a822adb88 sp 00007f4a7306d720 error 6 in libcontent.so[7f4a81b49000+fd7000] [drm] stuck on render ring [drm] stuck on render ring [drm:intel_pipe_set_base] *ERROR* pin & fence failed
There's a wild write. Please first update your ddx and mesa as Ubuntu 14.04 doesn't ship with the latest releases.
Hi, unfortunately i wasn't able to reproduce this reliable so i can't do a step by step writeup or provide more infos. I'm also not able to update this system to the latest drivers at the moment so this report probably can be closed until some one else is stumbling over the same problem.
We'll assume it was the mesa bug fixed in later 10.1 releases until we get a report with the current stack.
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.