Suspend to ram works for first time. Second time when I try system freezes. I am not seeing any errors on kernel logs.
I use intel 965GM graphics. And this issue is reproducible all times.
You say it's a regression. From which kernel version? Was 2.6.32 OK?
Yes 2.6.32 was fine. I installed 2.6.32-7 and yesterday. I also installed acpid.
After that I was able to suspend/resume multiple times. Just when I thought it was working again it froze again. But now it appears to be random.
I dont know if acpid is needed at all, I use kde and power related thing was correctly managed by its power manage power devil.
I am npot getting anything in the logs either. I tried to ssh to my host during it froze, but it seems that it froze after network was deactivated.
What is the latest kernel where this never happens, 2.6.32?
What is the earliest kernel where this issues is seen -- 126.96.36.199?
Is it possible to bisect and find the commit that caused the regression?
The earliest I think is 188.8.131.52. Latest I am not sure its 2.6.32 latest working one. It should be 2.6.31
I am having a lot of freezes with 2.6.32 kernel. Suspend is one of them it also happens during shutdown/restart. I ignored them for a while, and I guess I am little bit later in reporting the issue. . Then I saw in arch forums lots of others also having same system freeze under different scenario. So I decided to report the issue here.
(In reply to comment #4)
> The earliest I think is 184.108.40.206. Latest I am not sure its 2.6.32 latest
> working one. It should be 2.6.31
Adding to the list of regressions from 2.6.31.
Could you please test 2.6.33-rc6?
I have the same problem (Sony VGN-CR507E laptop, Debian/squeeze, GM965 graphics). I first noticed the problem around 220.127.116.11, but since 2.6.32 also brought problems with resuming with the iwlagn wireless driver, I hadn't tried to suspend/resume twice.
Suspend/resume the first time works fine, suspending the second time fails with a blank screen, underline cursor in the top left corner. Haven't found a key sequence that does anything, and the only recourse is to power down and restart.
last entries in pm-suspend.log:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95anacron suspend suspend: success.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/etc/pm/sleep.d/99laptop-mode suspend suspend: success.
/usr/lib/pm-utils/sleep.d/99video suspend suspend: disabled.
/etc/pm/sleep.d/action_wpa suspend suspend: success.
Wed Jan 20 22:00:23 EST 2010: performing suspend
I dont know if these are related my system froze during VT switch. Like the nature of this bug I was able to do VT switch multiple times without any issues and it just froze. Dont know how many time I successfully did the switch.
And there was nothing in the logs.
I will upgrade to 2.6.33-rc6 now and check.
I installed 2.6.33-rc6. So far things are good. Did 5 suspend/resume in a row and is working. Also I removed acpid.
Lately there so many random freezes I am facing. So I will monitor for a couple for days and report back.
I got a freeze when rebooting. I downgraded to 18.104.22.168 kernel and everything seems to be working fine.
Problem still in evidence with kernel version 2.6.33.
Today I grabbed the testing 2.6.32 kernels and compiled them all. Tried 2.6.32-rc1 first and had it fail on the second suspend/resume cycle, just like the production 2.6.32 kernels. Looks like the problem is somewhere in the 5.8M of changelog associated with 2.6.32-rc1.
I suspect that the problem is in the graphics system, because that's where it seems to be hanging. The effect I get has changed somewhat: originally I had a blank screen with an underline cursor, but now I get half an X screen (looks like it died halfway though the screensaver painting the screen). Some things have changed in userspace on the laptop, including a new grub that makes more use of weird framebuffer devices.
Any ideas on where to look next?
Is the problem still present in 2.6.37?
It was fixed somewhere around 2.6.34, I think. Sorry, I thought I'd sent an update, but apparently not.