Created attachment 113718 [details] Typical xorg log on concerned machine Hi, Reproductible : Always, immediate. On a Dell XPS M1330, video card: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) Running Linux Mint 17.1 x86_64, Cinnamon # uname -a Linux alpha 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux xorg Version: 1:7.7+1ubuntu8 xserver-xorg-video-intel Version: 2:2.99.910-0ubuntu1.4 Trying to play a YouTube video in chromium-browser Version: 40.0.2214.111-0ubuntu0.14.04.1.1069 Results in immediate GPU crash with black screen until reboot. Syslog logs : Feb 21 11:44:41 alpha kernel: [ 622.816023] [drm] stuck on render ring Feb 21 11:44:41 alpha kernel: [ 622.816032] [drm] GPU crash dump saved to /sys/class/drm/card0/error Feb 21 11:44:41 alpha kernel: [ 622.816035] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Feb 21 11:44:41 alpha kernel: [ 622.816037] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Feb 21 11:44:41 alpha kernel: [ 622.816039] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Feb 21 11:44:41 alpha kernel: [ 622.816042] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Feb 21 11:44:41 alpha kernel: [ 622.817072] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x82b0000 ctx 0) at 0x82b0f04 Feb 21 11:44:41 alpha kernel: [ 622.912058] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2 Feb 21 11:44:41 alpha kernel: [ 623.324105] [drm:i915_reset] *ERROR* Failed to reset chip. Feb 21 11:45:16 alpha kernel: [ 657.612219] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 Feb 21 11:45:24 alpha console-kit-daemon[1718]: GLib-CRITICAL: Source ID 57 was not found when attempting to remove it Feb 21 11:45:33 alpha console-kit-daemon[1718]: GLib-CRITICAL: Source ID 68 was not found when attempting to remove it Feb 21 11:45:44 alpha console-kit-daemon[1718]: GLib-CRITICAL: Source ID 89 was not found when attempting to remove it But the crash dump file is actually (always) empty : alpha ~ # ll /sys/class/drm/card0/error -rw------- 1 root root 0 févr. 21 11:40 /sys/class/drm/card0/error I will attach a typical (non-crash) xorg log in case it may help...
This bug looks similar to Linux Mint Bug #131542 : https://bugs.launchpad.net/linuxmint/+bug/1313542 And also : http://www.linuxquestions.org/questions/linux-hardware-18/intel-965-and-chromium-make-x11-crash-what-can-i-do-4175525059/ https://bugs.freedesktop.org/show_bug.cgi?id=84818 https://bugs.freedesktop.org/show_bug.cgi?id=85406 Evrybody seems to fall on this... Yet no fix ?
ls lies; use cat /sys/class/drm/card0/error | bzip2 > error.bz2 and attach.
Hi Chris, The machine has been rebooted since, so the requested file in unavailable, and I have changed the accel method from SNA to UXA, per advice from : https://wiki.archlinux.org/index.php/Intel_graphics#Corruption.2FUnresponsiveness_in_Chromium_and_Firefox The Internet is actually filled (i.e. links I added in my 1st comment) with bug reports stating that recent xorg + Intel + chromium + YouTube = DRM crash, so I believe that my bug report is actually a duplicate of others, the issue seems quite famous and infamously unfixed ;-)) so I guess that my own error log wouldn't bring much more about it anyway... Kind regards.
Yes, there are mesa bugs that affect Chromium + gen4, but I didn't want to presume that without an error state. That archlinux page seems to be a load of codswallop though.
The issue is on my 12 years old son's machine, and it's kind of hard to get any log from him before he has just rebooted with rude words to his laptop ;-) Okay, now he told me that it crashed again after I had turned his accel to UXA, but unfortunately, I couldn't have the log.
Mesa 10.5 has some gen4+chrome hang fixes. Presuming this issue was fixed by it. Please reopen if that is not the case, and attach the error log.
Very similar kern.log entries to my bug 92117, fixed by upgrading libgl1-mesa-dri to 10.5.9.
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.