Created attachment 96389 [details] Content of /sys/class/drm/card0/error System is barely usable. I am losing part, or all, of my GUI all the time. A crash as below will eat all keyboard inputs and only allow ctrl-alt-f1 and the like. As per dmesg: [ 2207.681554] [drm] stuck on render ring [ 2207.681558] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 2207.681558] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 2207.681559] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 2207.681560] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 2207.681560] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 2207.684342] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xedf7000 ctx 1) at 0xedf7514 [ 2213.676422] [drm] stuck on render ring [ 2213.676485] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xfe61000 ctx 1) at 0xfe61214 [ 2213.676487] [drm:i915_context_is_banned] *ERROR* context hanging too fast, declaring banned! richih@eudyptes ~ % dpkg -l | grep linux-image | grep '^ii' ii linux-image-3.13-1-amd64 3.13.6-1 amd64 Linux 3.13 for 64-bit PCs ii linux-image-amd64 3.13+56 amd64 Linux for 64-bit PCs (meta-package) richih@eudyptes ~ % uname -a Linux eudyptes 3.13-1-amd64 #1 SMP Debian 3.13.6-1 (2014-03-19) x86_64 GNU/Linux richih@eudyptes ~ %
PS: `top` is reasonably happy, yet my fan is running and the system experiences frequent slowdowns.
Same problem here kern.log: Mar 25 22:56:18 Tuxedo kernel: [ 77.405050] [drm] stuck on render ring Mar 25 22:56:18 Tuxedo kernel: [ 77.405058] [drm] GPU crash dump saved to /sys/class/drm/card0/error Mar 25 22:56:18 Tuxedo kernel: [ 77.405060] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Mar 25 22:56:18 Tuxedo kernel: [ 77.405061] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Mar 25 22:56:18 Tuxedo kernel: [ 77.405062] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Mar 25 22:56:18 Tuxedo kernel: [ 77.405064] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Mar 25 22:56:23 Tuxedo kernel: [ 83.431319] [drm] stuck on render ring Mar 25 22:56:29 Tuxedo kernel: [ 89.444223] [drm] stuck on render ring Mar 25 22:56:35 Tuxedo kernel: [ 95.390385] [drm] stuck on render ring Mar 25 22:56:41 Tuxedo kernel: [ 101.450022] [drm] stuck on render ring ~$ inxi -v3 System: Host: Tuxedo Kernel: 3.13-6.towo-siduction-amd64 x86_64 (64 bit gcc: 4.8.2) Desktop: KDE 4.12.3 (Qt 4.8.6) Distro: siduction 13.1.0 Firestarter - kde - (201305211844) Machine: Mobo: Notebook model: W230ST Bios: American Megatrends v: 4.6.5 date: 07/16/2013 CPU: Quad core Intel Core i7-4702MQ CPU (-HT-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 17565 Clock Speeds: 1: 2200 MHz 2: 2211 MHz 3: 2200 MHz 4: 2443 MHz 5: 2200 MHz 6: 2200 MHz 7: 2200 MHz 8: 2201 MHz Graphics: Card: Intel 4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Display Server: X.Org 1.15.0 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 10.1.0 Direct Rendering: Yes Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 04:00.1 IF: eth0 state: down mac: xx:xx:xx:xx:xx:xx Card-2: Intel Wireless 7260 driver: iwlwifi v: in-tree: bus-ID: 03:00.0 IF: wlan0 state: down mac: xx:xx:xx:xx:xx:xx Drives: HDD Total Size: 1120.2GB (38.9% used) 1: model: HGST_HTS721010A9 2: model: Crucial_CT120M50 Info: Processes: 218 Uptime: 27 min Memory: 1138.2/15975.4MB Init: SysVinit runlevel: 5 Gcc sys: 4.8.2 Client: Shell (bash 4.3.01) inxi: 2.1.7
Created attachment 96391 [details] Content of /sys/class/drm/card0/error
*** This bug has been marked as a duplicate of bug 75724 ***
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.