upgrade to linux-image-2.6.24-15.27 broke suspend to ram

Bug #213723 reported by Roberto Cássio Jr.
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have upgraded Hardy from linux-image-2.6.24-15.26 to linux-image-2.6.24-15.27 from the official repositores, just some few hours ago. Afer this, computer was not returning from Suspend to Ram anymore (not even the video display came back). It was always working fine since I started testing Hardy.

When booting from linux 2.6.24-14, suspend to ram works normally. I can't try booting again from 2.6.24-15.26, because I see no option for it, but I'm sure it was working, I even tested it today before going to work (and tested other times too).

My motherboard is an Intel DP35DP. I don't know what useful info can I provide - since the system hangs after trying to resume, I don't know which system logs wouldn't be overwritten when the computer restarts. I'm attaching an lspci -vv output so you can check my hardware. Feel free to request any additional info.

Revision history for this message
Roberto Cássio Jr. (rcsdnj) wrote :
Revision history for this message
James Troup (elmo) wrote :

I'm seeing the same thing with a Compaq NC6320. Suspend/resume was working flawlessly with -14, but has failed to resume twice now since I upgraded to -15.

Changed in linux:
status: New → Confirmed
Revision history for this message
Roberto Cássio Jr. (rcsdnj) wrote :

Maybe it's important to add that resuming from Hibernate isn't working also (although I didn't test with the last kernel before this bug, so I can't be sure it was working before).

Also, I'd like to say that, in some of the times I tried to suspend to ram, the computer has hanged BEFORE the suspend operation complete, leaving the screen with a single blinking cursor only; but most of the times, the suspend operation seemed to go fine and the problem ocurred only when trying to make the computer return from it (the monitor didn't turn on back).

Revision history for this message
Roberto Cássio Jr. (rcsdnj) wrote :

Last update (linux 2.6.24-16.30) resolved this problem. I think it was due to the "tsc prevent time going backwards" change, which was reverted.

I'm marking it as fixed.

Changed in linux:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.