Created attachment 320604 [details]
Log of X server starting normally.
Description of problem:
When using the Intel X driver, the system crashes on resume. The display reappears, but then the system just hangs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start X
2. Suspend machine
Display appears, but machine locks up
Proper resume to usable system.
This is the first kernel version in which using the intel driver works at all, so good work there.
I tried getting some output with netconsole, but apparently the e1000e driver wasn't up at that point.
I haven't tried i915.modeset=1
Crashes on resume from hibernate as well.
i915.modeset=1 seems pretty broken, which I guess is expected.
If I switch to a text vt before suspending, and then resume, the machine works fine. When I switch to X, it works normally for several seconds (animated icons, pointer moves, etc) before the machine locks up.
I'll try to see if anything appears on netconsole next time.
- nothing appears on netconsole when it crashes
- switching to a text vt and using pm-suspend will resume properly; when switching to the X vt, there's a fairly good chance it will resume properly without hanging (maybe ~60% of the time it works)
can you try in order:
open a console, become root (su -) and write:
pm-suspend --quirk-s3-bios --quirk-s3-mode
let me know.
OK, I tried all those. The first one just hangs immediately on resume, leaving the screen blank and no activity other than the fan blowing.
The rest have the same symptom as nothing at all: X resumes, I see what was on the screen at suspend time, but the machine is completely locked up.
try the following site:
I looked over that, but I don't see anything I haven't already tried. I think this is pretty clearly a kernel bug at some level, but I don't have any idea how to make more progress on this.
It is, however, a pretty serious blocker for me, as it breaks suspend/resume on my laptop (the only workaround is that hibernate works reliably, albeit painfully slowly).
I saw mention of the same problem on an Ubuntu thread and someone suggested a script in /etc/pm/sleep.d/ that disabled extra CPUs during suspend/resume.
I tried this on my X200 with Intel driver, and set the script to sleep for 60 seconds on resume before reenabling the extra core. I was able to use the X desktop for that 60 seconds, and then it froze up. :-)
Anyway, a workaround for your laptop is to use the "vesa" driver instead of "intel" if you need suspend to work in the short term. Of course, you don't get all the acceleration.
Do you have compiz/desktopeffects enabled? I'm having the same issue but it goes away when I disable desktop effects (this is also on rawhide x86_64 - on a dell m1330).
I have the same hardware as Jeremy, and I definitely don't use compositing, but I see the same problem.
(In reply to comment #9)
> Do you have compiz/desktopeffects enabled? I'm having the same issue but it
> goes away when I disable desktop effects (this is also on rawhide x86_64 - on a
> dell m1330).
No, I'm not using anything like that.
According to http://bugs.freedesktop.org/show_bug.cgi?id=18049#c10 this patch will fix the problem: http://lists.freedesktop.org/archives/intel-gfx/2008-November/000508.html
I have not tried it yet.
it should be included in kernel 188.8.131.52-101 which is building now.
Thanks, 184.108.40.206-101 resumes properly for me now.
(In reply to comment #14)
> Thanks, 220.127.116.11-101 resumes properly for me now.
2.6.27-5.101 worked once for me, and hung the second time. My configuration is an X200s with compiz enabled.
Can you confirm it works reliably for you?
Just tried now with 18.104.22.168-101:
* with no 3D running, I can reliably suspend and resume.
* If I suspend when glxgears is running, on resume the glxgears window
remains black until I drag it around.
* Running compiz makes the system freeze occasionally even without suspend.
It has been reasonably stable when I don't use 3d (I don't habitually use compiz).
Its much less reliable using 3d. I ran googleearth for a while (much better performance than last time I tried), but after a while the textures started getting corrupted, then the whole screen, then X crashed, then the machine.
Similarly running a 3D windows game under Wine - worked OK, but it destabilized the machine after a while.
So I think this particular bug is fixed, but there are still general stability issues with 3D.
resume fixed closing.