Unable to Suspend/Hibernate

Bug #163247 reported by Osiris2258 on 2007-11-17
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Undecided
Unassigned

Bug Description

Attempting to suspend returns the system to the logon, as if the suspend had been successful and the system had been returned.
Attempting to hibernate results in a lockup, necessitating hard reboot. The system does not cleanly unmount in this instance, often resulting in errors in both Ext3 and NTFS mounted file systems which must be repaired by the respective disc recovery software during subsequent boot-up.

Osiris2258 (void2258) wrote :

After taking the steps given at https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend, the hibernate results have changed to an auto shutdown, rather than a freeze. Also, the file corruption problem appears to have gone away.

Still unable to successfully suspend or hibernate.

Oleksij Rempel (olerem) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please follow the steps described in https://wiki.ubuntu.com/DebuggingKernelSuspend and add the resulting "Magic number" and "hash matches" lines to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

Osiris2258 (void2258) wrote :

1. Output of "uname -a" : Linux kuromizu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Osiris2258 (void2258) wrote :

The results of "dmesg > dmesg.log" are attached.

Osiris2258 (void2258) wrote :
Osiris2258 (void2258) wrote :

trying to do the last part causes the computer to return to a state wherein, while the mouse cursor moves, nothing responds to either mouse or keyboard input.

Oleksij Rempel (olerem) wrote :

another explanetion of the latest part:

1. execute "sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force"
WARNING: after this step you have only 3 minute before the debug data will be lost.

2. try to resume the PC and if it freeze reboot it

3. after boot, get dmesg and post it here.

Oleksij Rempel (olerem) wrote :

you may wont to read this file and try different options according to comments:

sudo vi /etc/default/acpi-support

this can make your suspend work.

Osiris2258 (void2258) wrote :

The dmesg from <1min after trying to suspend and coming right back to the password prompt.

Osiris2258 (void2258) wrote :

I don't know enough about graphics or memory to know what the comments in acpi-support mean, so I have no idea what I could try there.

Oleksij Rempel (olerem) wrote :

Ok. We have:
[ 9.632000] Using IPI No-Shortcut mode
[ 9.632000] Magic number: 15:73:337
[ 9.632000] hash matches device ttyzc
[ 9.632000] hash matches device tty58

Reassign to kernel team.

Brian Murray (brian-murray) wrote :

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team

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!

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.

Graham Bennett (graham33) wrote :

FWIW, I have installed the Intrepid Ibex release candidate on my Sony VAIO TZ, and I now how have no problems with suspend and hibernate. Thanks everyone.

Graham

Osiris2258, since you are the original bug repoter, care to confirm this is resolved for you with Intrepid? Thanks.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers