Kernel - git 07/07/09
Intel Driver/mesa - git master
On resume from a suspend, x freezes. I am presented with an image of what my desktop looked like before I suspended (I do not use a lock screen), and cannot interact with the machine in any way. I do not have the ability to test and see if network access still works, however the numlock/capslock keys are both responsive. The mouse does not move however and there is nothing at all of interest in logs after a freeze. So far the only way I have found out of it is a hard reset.
Will you please try the patch in https://bugs.freedesktop.org/show_bug.cgi?id=21719#C8 on the latest linus git tree and see whether the issue still exists?
I can't say with 100% certainty, but thus far my suspend/resume has worked minus hitting bug #22426. However restarting my WM after a resume clears that up and is therefore a small issue as I dont lose any data. However this would be a major ticket item for normal users as it sure looks funky...
I can now say with 100% certainty that patch did not fix the issue. After letting my computer sleep for a couple hours after work today (drive home) it froze on resume. The issue is not resolved =/
I remembered some additional informaiton I should have included with the initial report. This bug started after receiving an update to the xorg intel driver, around 3 weeks ago I think. I would prefer not to have to perform a bisect of the driver (largely since I suck at git), but will do so if someone can give me instructions.
(In reply to comment #3)
> I can now say with 100% certainty that patch did not fix the issue. After
> letting my computer sleep for a couple hours after work today (drive home) it
> froze on resume. The issue is not resolved =/
Will you please do the following test to narrow down this issue?
a. kill the process using /proc/acpi/event
b. dmesg >dmesg_before; echo mem > /sys/power/state; dmesg >dmesg_after; sync;
c. wait for about one or two hours and press the power button to wake up the system. This is to simulate that the box is in sleeping state for a couple hours.
d. If the system can't be booted, please reboot the system and see whether there exists the file of dmesg_after.
Will do tonight, thank you for the input!
Created attachment 27653 [details]
So the results are in. I do in fact get a dmesg_after as a result, however there does not appear to be anything interesting in there.
(In reply to comment #8)
> So the results are in. I do in fact get a dmesg_after as a result, however
> there does not appear to be anything interesting in there.
As there exists the file of dmesg_after, it seems that the system can be resumed from the sleeping state. And the remaining issue is that sometimes X will freeze on resume.
It will be great if you can attach the Xorg log when it freezes.(BTW: this should be obtained when the system enters the console mode in the next startup).
Will you please confirm whether it can be resumed correctly under console mode?
The patch in comment #1 is required.
Created attachment 27673 [details]
xorg log after crash
Here you go, this is the xorg log from after a crash, I dont think there is too much of interest in there unfortunately. Trying to suspend from console and see if I can reproduce that way.
Ok so suspend from console works fine, however sometimes when I try to switch back into X it will lock immediately after displaying the contents in X
(In reply to comment #11)
> Ok so suspend from console works fine, however sometimes when I try to switch
> back into X it will lock immediately after displaying the contents in X
Will you please also attach the xorg.log with KMS disabled? Of course please enable the modedebug in xorg.conf.
It will be great if you can attach the output of vbios dump.
Will you please try the following patches and see whether the
issue still exists?
Patch : drm/i915: Check that the relocation points to within the target
i965: Fix relocation delta for WM surfaces (in mesa)
Since there is no response for more than two months, this bug will be rejected.
If the issue still can be reproduced, please reopen it again.