Hibernate doesn't work

Bug #128440 reported by sem
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I click on hibernate and it seems like it's going to work, but then it begins repeating the message that a program is accessing the hardware directly.

Here is your bug report number

Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Revision history for this message
TJ (tj) wrote :

I asked the user to create this report after discussion on IRC #ubuntu

Revision history for this message
sem (semitones) wrote :

After the screen dims, the keyboard number and caps lock lights blink off and on, and this message repeats:

atkbd.c: Spurious ACK on isa0060/serio0. Some program may be trying to access the hardware directly.

Scary, huh.

Revision history for this message
Oleksij Rempel (olerem) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? If so, please reopen the bug. Thanks in advance.

Changed in linux-source-2.6.20:
status: New → Invalid
Revision history for this message
sem (semitones) wrote :

Hibernate still flashes the screen, and displaces cryptic messages about the usb, but it does eventually power down, and resumes naturally. If you want to work with the screen flashes and stuff, keep it open. But those are minor problems, and I'll understand if you close it. I'm just glad that the update to gutsy seems to have fixed hibernate. (I hadn't tried hibernating in awhile because it never worked).

There hasn't been any activity because no-one did anything about it... but I'm sure there are much more important bugs to work on.

Revision history for this message
sem (semitones) wrote :

still some rough spots, but the computer does actually hibernate now.

Changed in linux-source-2.6.20:
status: Invalid → New
Revision history for this message
Oleksij Rempel (olerem) wrote :

According to this link:
http://www.linuxquestions.org/questions/linux-general-1/kernel-panicatkbd.c-spurious-ack-on-isa0060serio0-507224/

Seems like this issue coused by some brocken modules not related keyboard , for example sata controller. Please can you recompile you kernel with module sata_nv build in?

Revision history for this message
Ralph Janke (txwikinger) wrote :

Could you please test if this still occurs in the latest hardy kernel?

Thanks

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
sem (semitones) wrote :

I installed hardy on a spare partition

~$ uname -a
Linux ubuntualpha 2.6.24-11-generic #1 SMP Fri Feb 29 21:26:31 UTC 2008 x86_64 GNU/Linux

now hibernate is basically broken --
When I click hibernate, the screen darkens, I get a blinking cursor, and then two "[...]activation failed" messages. Then the computer powers down. So far, nothing is that bad

However when I reboot, the screen has a double left-right image, starting with usplash (which used to happen from time to time on gutsy), but not going away! Ctrl Alt Backspace didn't fix the problem. I forced shutdown.

Revision history for this message
sem (semitones) wrote :

@fishor - I don't know how to recompile the kernel, but I will look for instructions if you want.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
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.