suspend/hibernate

Bug #157916 reported by soccerboy
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
High
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

I am using a Toshiba Satellite M55 and when I set my power management preferences to suspend my computer, and the computer sleeps, my computer goes haywire. When I wake it up, it returns to the desktop for about 15-20 seconds saying that the suspend did not work correctly and then it goes to a black screen with a lot of lines saying stuff about usb. Then the computer turns off. When I turn it back on, and log in, the computer returns to the state that it was in when it suspended except for the fact that network manager can't connect to my wireless network. I have the same problem when my computer hibernates as a result of running low on battery.

I'll provide more information if you need it but am not sure what I need to provide to make solving the problem easier.

Tags: cft-2.6.27
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) 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 https://wiki.ubuntu.com/DebuggingKernelSuspend

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!

Revision history for this message
soccerboy (man88soccer) wrote :

uname -a output

Linux manan 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Revision history for this message
soccerboy (man88soccer) wrote :

dmesg output attached

Revision history for this message
soccerboy (man88soccer) wrote :

lspci output attached

Revision history for this message
soccerboy (man88soccer) wrote :

a new dmesg output attached after a suspend that seemed to go correctly.
I'll attach another one after a suspend initiated by gnome-power-management if it is possible in the small 20 second window.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Ok thank you, please do not forget to follow https://wiki.ubuntu.com/DebuggingKernelSuspend . Thanks.

Revision history for this message
soccerboy (man88soccer) wrote :

I went through the steps on that link and I ended up with only one hash matches statement. Don't know what that means.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Please copy it here, thank you.

Revision history for this message
cement_head (andorjkiss) wrote :

Suspend/Hibernate on Dell i8100 Gutsy Broken causing a KERNEL PANIC; everything else seems okay after upgrade from fiesty

KERNEL DEBUG output

bash: /sys/power/pm_trace: Permission denied
Stopping network connection manager: NetworkManager.
ifdown: failed to open statefile /var/run/network/ifstate: Permission denied
SIOCSIFFLAGS: Permission denied
ifdown: failed to open statefile /var/run/network/ifstate: Permission denied
SIOCSIFFLAGS: Permission denied
ifdown: failed to open statefile /var/run/network/ifstate: Permission denied
SIOCSIFFLAGS: Permission denied
Couldnt get a file descriptor referring to the console
Couldnt get a file descriptor referring to the console
/etc/acpi/suspend.d/80-video-pci-state.sh: line 5: /var/run/vga-pci-0000:01:00.0: Permission denied
open /dev/mem: Permission denied
Failed to initialise LRMI (Linux Real-Mode Interface).
/etc/acpi/suspend.d/80-video-vesa-state.sh: line 7: [: !=: unary operator expected
Shutting down ALSA...warning: 'alsactl store' failed with error message 'alsactl: save_state:1280: Cannot open /var/lib/alsa/asound.state for writing: Permission denied'...failed.
open /dev/mem: Permission denied
Failed to initialise LRMI (Linux Real-Mode Interface).
/etc/acpi/sleep.sh: line 39: /sys/power/state: Permission denied
open /dev/mem: Permission denied
Failed to initialise LRMI (Linux Real-Mode Interface).
/etc/acpi/resume.d/17-video-restore.sh: line 6: [: !=: unary operator expected
open /dev/mem: Permission denied
Failed to initialise LRMI (Linux Real-Mode Interface).
/etc/acpi/resume.d/35-modules-load.sh: line 7: /sys/class/firmware/timeout: Permission denied
/etc/acpi/resume.d/35-modules-load.sh: line 17: /sys/class/firmware/timeout: Permission denied
Sorry, only the superuser can change the Hardware Clock.
open /dev/mem: Permission denied
Failed to initialise LRMI (Linux Real-Mode Interface).
ifup: failed to open statefile /var/run/network/ifstate: Permission denied
ifup: failed to open statefile /var/run/network/ifstate: Permission denied
ifup: failed to open statefile /var/run/network/ifstate: Permission denied
Starting network connection manager: NetworkManagerYou must be root to run NetworkManager!
chvt: Wrong number of args
Couldnt get a file descriptor referring to the console
chvt: Wrong number of args
Setting up ALSA...done.
FATAL: Error removing button (/lib/modules/2.6.22-14-generic/kernel/drivers/acpi/button.ko): Operation not permitted
FATAL: Error removing fan (/lib/modules/2.6.22-14-generic/kernel/drivers/acpi/fan.ko): Operation not permitted
FATAL: Error removing thermal (/lib/modules/2.6.22-14-generic/kernel/drivers/acpi/thermal.ko): Operation not permitted
FATAL: Module acpi_sbs not found.
FATAL: Error removing ac (/lib/modules/2.6.22-14-generic/kernel/drivers/acpi/ac.ko): Operation not permitted
FATAL: Error removing battery (/lib/modules/2.6.22-14-generic/kernel/drivers/acpi/battery.ko): Operation not permitted
FATAL: Module acpi_sbs not found.

Can I unload acpi_sbs? in acpi-support

uname -a
Linux oskar3 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

cement_head : please open a new bug report, thank you.

Revision history for this message
soccerboy (man88soccer) wrote :

[ 15.994442] hash matches device ttyv1
this is the statement that matches in the dmesg.log file.

I'll try running suspend state again and see if I get different results as soon as I get home.

Thanks for your prompt responses.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you very much, I'm marking this as triaged and assigning to the kernel team.

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-acpi
status: Incomplete → Triaged
Revision history for this message
Ben Collins (ben-collins) wrote :

This sounds like a good candidate for the new suspend/resume testing infrastructure going into hardy's kernel.

Changed in linux-source-2.6.22:
assignee: ubuntu-kernel-acpi → timg-tpi
Revision history for this message
Tim Gardner (timg-tpi) wrote :

The released version of 2.6.24 is now in the archive. Please test against that.

Changed in linux-source-2.6.24:
assignee: nobody → ubuntu-kernel-team
status: New → Triaged
Changed in linux-source-2.6.22:
assignee: timg-tpi → nobody
status: Triaged → Won't Fix
Revision history for this message
soccerboy (man88soccer) wrote :

In the 2.6.22, my suspend/resume and hibernation no longer cause a kernel panic but they still give me a message that says that some hardware failed to sleep/hibernate. What do I need to post to help you guys troubleshoot this?

Changed in linux:
importance: Undecided → High
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
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

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

*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: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers