gnome-power-manager: (user) suspend failed on Toshiba Portege R500

Bug #176544 reported by Ketil
10
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

I am running an updated Ubuntu 7.10 on my Toshiba Portege R500 11-B. I am running logged on as the user "ketil", which is the standard initial user on my Ubuntu system.

When I close my laptop's lid, it tries to suspend. It seems to manage at first, and goes silent and switches off all indicator lights, but it immediately resumes again. Then I get a popup from the power icon saying:

Sleep Problem
Your computer failed to suspend.
Check the help file for common problems.

as I was trying to reproduce this, I've also gotten the following popup from the power icon. I'm not sure I got it copied correctly word for word. It seems to show up if I open the lid just after the computer starts resuming when suspend fails.

Action forbidden
Policy timeout is not valid. Please wait a few seconds and try again.

My /var/log/messages says:

....
Dec 15 14:34:35 ketil-laptop kernel: [ 8219.596000] sr 10:0:0:0: Attached scsi generic sg1 type 5
Dec 15 14:34:41 ketil-laptop gnome-power-manager: (ketil) Resuming computer
Dec 15 14:34:41 ketil-laptop gnome-power-manager: (ketil) suspend failed

So it takes around 6 seconds from suspend is done until it has decided that suspend failed.

Revision history for this message
Dima Ryazanov (dima-gmail) wrote :

I get the message "Policy timeout is not valid. Please wait a few seconds and try again" once in a while, too.
I'm running Gutsy on a Thinkpad T43p. Most of the time, suspend works fine. But about 5% of the time, it doesn't do anything and the power manager shows that message.

I don't see any errors in /var/log/messages, though. Here is what I get during the failed suspend:

Dec 26 16:44:29 localhost gnome-power-manager: (dimaryaz) Suspending computer because the suspend button has been pressed
Dec 26 16:44:30 localhost ifplugd.agent[31506]: Stopping ifplugd for eth1
Dec 26 16:44:30 localhost kernel: [222174.140000] ACPI: PCI interrupt for device 0000:0b:02.0 disabled
Dec 26 16:44:30 localhost kernel: [222174.148000] ath_pci: driver unloaded
Dec 26 16:44:30 localhost kernel: [222174.152000] wlan: driver unloaded
Dec 26 16:44:30 localhost kernel: [222174.152000] ath_hal: driver unloaded
Dec 26 16:44:31 localhost ifplugd.agent[31548]: Stopping ifplugd for eth0
Dec 26 16:44:31 localhost kernel: [222174.568000] ACPI: PCI interrupt for device 0000:02:00.0 disabled
Dec 26 16:44:55 localhost kernel: [222178.596000] Stopping tasks ...
Dec 26 16:44:55 localhost kernel: [222198.600000] Restarting tasks ... done.
Dec 26 16:44:56 localhost kernel: [222199.488000] ieee80211: 802.11 data/management/control stack, git-1.1.13
Dec 26 16:44:56 localhost kernel: [222199.488000] ieee80211: Copyright (C) 2004-2005 Intel Corporation <email address hidden>
Dec 26 16:44:56 localhost kernel: [222199.516000] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.0kmprq
Dec 26 16:44:56 localhost kernel: [222199.516000] ipw2200: Copyright(c) 2003-2006 Intel Corporation
Dec 26 16:44:56 localhost kernel: [222199.520000] ACPI: PCI Interrupt 0000:0b:02.0[A] -> GSI 21 (level, low) -> IRQ 23
Dec 26 16:44:56 localhost kernel: [222199.520000] ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
Dec 26 16:44:56 localhost gnome-power-manager: (dimaryaz) Resuming computer
Dec 26 16:44:56 localhost kernel: [222199.964000] ipw2200: Detected geography ZZA (11 802.11bg channels, 13 802.11a channels)
Dec 26 16:44:56 localhost kernel: [222199.968000] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
Dec 26 16:44:56 localhost kernel: [222199.976000] wlan: 0.8.4.2 (0.9.3.2)
Dec 26 16:44:56 localhost kernel: [222199.980000] ath_pci: 0.9.4.5 (0.9.3.2)
Dec 26 16:44:56 localhost kernel: [222199.992000] tg3.c:v3.77 (May 31, 2007)
Dec 26 16:44:56 localhost kernel: [222199.992000] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16

(Btw, why does it unload and load ath_pci? I don't have an Atheros wireless card here.)

Revision history for this message
John Cooper (choffee) wrote :

I am also getting this on a R500 running Gutsy. Suspend goes through it shutdown and then the system is quiet for a second or two then it starts to load up again.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/

Changed in gnome-power-manager:
assignee: nobody → sourcercito
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
John Cooper (choffee) wrote :

Hi,

I tried with the latest Hardy alpha4 and it still does exactly the same. Goes through the suspend, turns the power light to orange then just starts back up again.

john

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi John
Could you please read https://wiki.ubuntu.com/DebuggingGNOMEPowerManager and follow the instructions to obtain the debugging information so you can include in this report as separated attachments?. This will greatly help us in tracking down your problem.

Thanks in advance

Revision history for this message
Torsten Spindler (tspindler) wrote :

The attached report is for Hardy, all available updates applied (2008-03-03). I'll attach dmesg output next.

Revision history for this message
Torsten Spindler (tspindler) wrote :

Following the process described on wiki.ubuntu.com/DebuggingKernelSuspend the attached dmesg was generated. Not sure if the included magic number is really relevant:
[ 9.702287] Magic number: 0:810:724

After a reboot I get another Magic number:

[ 9.052404] NET: Registered protocol family 1
[ 9.052442] Using IPI No-Shortcut mode
[ 9.052477] registered taskstats version 1
[ 9.052616] Magic number: 0:466:876
[ 9.052659] hash matches device ptyx0
[ 9.052790] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 9.052792] EDD information not available.
[ 9.053123] Freeing unused kernel memory: 364k freed

Revision history for this message
Torsten Spindler (tspindler) wrote :

Output of $ sudo report-hw is attached.

Revision history for this message
John Cooper (choffee) wrote :

Looks like this now works under Hardy beta.

You need to add "ehci_hcd" to the "SUSPEND_MODULES" line in /etc/pm/config.d/modules so I now have one line in the file:

SUSPEND_MODULES="kvm kvm_intel ehci_hcd"

Thanks guys

Revision history for this message
Torsten Spindler (tspindler) wrote :

This solution works for me too, thanks John.

Revision history for this message
Ketil (ketil-froyn) wrote :

Thanks John, that works here as well.

Since you also have a portege R500 - do you have trouble connecting to new WLANs too? I usually need to reboot to connect to a newly configured WLAN (I don't even get an IP with DHCP, despite running ifdown wlan0; ifup wlan0 again and again, but rebooting works), and the System -> Administration -> Network tool doesn't list the available networks unless I run "sudo iwlist wlan0 scan" in a terminal window at the same time, and still then they often disappear before I am able to click the one I need.

Regards,
Ketil

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in gnome-power-manager:
assignee: sourcercito → nobody
status: Incomplete → Invalid
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.