| Summary: | Screen freeze during use of chrome/chromium with acceleration and i915/Haswell | ||
|---|---|---|---|
| Product: | DRI | Reporter: | sibrus |
| Component: | DRM/Intel | Assignee: | Ben Widawsky <ben> |
| Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | christopher.m.penalver, intel-gfx-bugs |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| See Also: | https://launchpad.net/bugs/1294391 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | |||
Created attachment 96325 [details]
Output of /sys/class/drm/card0/error which was referenced in the dmesg output (gzipped)
Would it be possible to try our latest -nightly repository? http://cgit.freedesktop.org/drm-intel/log/?h=drm-intel-nightly We need a new error state from latest kernels, which also dumps the context object. Which is where the issue seems to happen. I predict that this has the form where the context object isn't overwritten (at least not in the first page), but it is dying in the context load (that is my guess). I can give it a shot, it may be a few days until I have a free evening to do it. Are there any instructions for compiling/installing it? Also am I just compiling the driver or do I need to do xorg or anything else? It's the kernel, but nothing else required (it's just a drop-in replacement). Distro's usually have excellent howtos for building random kernels from git and installing them properly, some like Ubuntu even have autobuilders for drm-intel-nightly (called drm-intel-experimental iirc). sibrus@gmail.com, you would wnat to follow install instructions from https://wiki.ubuntu.com/Kernel/MainlineBuilds in installing the latest from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/ . I tested this with the latest kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/ (2014-03-28-trusty) I was able to reproduce the error, or at least a similar error. The behavior upon encoutering the error was a little different. The screen froze once again, however upon unfreezing instead of fully recovering, all the tabs of chrome wouldn't render anything. After restarting chrome it behaved normally again. Created attachment 96575 [details]
Output of dmesg, for 2014-03-28-trusty
Created attachment 96576 [details]
Output of /sys/class/drm/card0/error (gzipped), 2014-03-28-trusty
Right the context (first page of, at least) looks intact, but it has the hallmarks of the same context restore bug as the original. Care to try my patch from: https://bugs.freedesktop.org/show_bug.cgi?id=75724 Hi Ben, I'm willing to give the patch a shot. I saw two patches attached to the bug you linked me. Do I use both or just the latest one? I tried the latest drm-intel-nightly. I downloaded the following commit: http://cgit.freedesktop.org/drm-intel/commit/?h=drm-intel-nightly&id=346aad79969a02f2b9fc77bdade02c7413f42ea9 Then I applied both patches that I found in this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=75724 As soon as I booted with the compiled kernel, I got a few screen freezes, then unity appeared to crash as I lost the unity bar and all window decorations. I did capture the dmesg output and the gfx crash log, which are attached below. Created attachment 96794 [details]
dmesg from drm-intel-nightly with patches
Created attachment 96795 [details]
/sys/class/drm/card0/error output, gzipped, from drm-intel-nightly with patch
*** This bug has been marked as a duplicate of bug 77207 *** |
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.
Created attachment 96324 [details] Output of dmesg immediately following this error My hardware is an Acer C720 (Intel graphics). The symptoms of the problem is the display completely stops updating, except the mouse cursor continues to move. Clicking and any keypresses have no effect. The system remains in this state for about 15-60 seconds, then it recovers and goes back to normal. The problem most commonly happens when using chrome or chromium to do any kind of intesive hardware-accelerated rendering. (Hardware accelerated rendering is enabled in chrome/chromium.) Typically a youtube video or and HTML5 game with lots of animations. The problem tends to happen during periods of high CPU usage. xorg version is 7.7+1ubuntu8 OS is ubuntu 14.04 (amd64)