Kernel Bug Tracker – Bug 43088
[965GM] hang at DPMS time
Last modified: 2012-04-18 22:12:24 UTC
Created attachment 72873 [details]
I have the Ubuntu 12.04 beta2 x86_64 with a mainline kernel 3.2.14 installed on a FUJITSU SIEMENS ESPRIMO Mobile M9400 notebook with an Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (lspci -vvnn attached), and I'm experiencing GPU hangups several times a day (dmesg output attached).
Everything is well as long as I don't leave the computer for long enough for a DPMS powersaving to kick in (set to 5 minutes in Unity). If I'm away long enough, there is a good chance I'll find the GPU hanged up upon return. Unfortunately, I'm not able to reproduce this issue at will and have to wait for it to happen.
If there is anything I can do to help to resolve this, I'll gladly do so.
Created attachment 72874 [details]
Well, first can you please try 3.4-rc2 (or newer) and rehang your system? That improves the error handling and should dump you a big i915_error_state into debugfs somewhere when the issue happens. Please grab that file and attach it to the bug report.
Likely to be danvet/drm-intel-fixes:
Author: Chris Wilson <firstname.lastname@example.org>
Date: Tue Apr 3 17:58:35 2012 +0100
drm/i915: Finish any pending operations on the framebuffer before disabling
Created attachment 72875 [details]
Wait for pending fb operations before any modeset.
In addition it would also be useful to try this patch on top of what we already have queued for drm-intel-fixes. Oh, and there is a further patch in xf86-video-intel/sna to reduce the race window even further.
I would like to thank you both for your quick response and suggestions.
I have tried kernel version 3.4 before submitting this bug and it was much better than version 3.2. There was only one hang in several days. However, version 3.4-rc2 looks even better and offered a hang-free experience for the last six days. I will be testing other release candidates when available and report if they hang on my system.
You need 3.4-rc3 for the patch mentioned in comment #3.
Cool, sounds like it's fixed then. Thanks for testing! Please re-open if 3.4-rc3 or newer still gives you trouble.