machine does not wake up after suspend

[Hubert Figuiere]

I just upgraded to Edgy.

I have kernel linux-image-2.6.17-10-386

The machine is a ThinkPad Z60t.

I did suspend the machine Fn-F4. It didn't wake up. The "sleep" light stayed, nothing reacted.

I was running linux-image-2.6.15-19-386 without glitch.

Behaviour is different from https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/49078 that I reported a few month back

Note: the original reporter indicated the bug was in package 'linux-image-2.6'; however, that package was not published in Baltix.

[Hubert Figuiere (hub)]

closing on baltix. Apparently the Ubuntu bug reporter does not default to ubuntu.

[Hubert Figuiere (hub)]

reproducable 100%

I open the lid, the HD led blinks, then NOTHING.

[Hubert Figuiere (hub)]

Edgy is likely to be the second release after Dapper that have broken suspend/sleep on this laptop while it worked *out of the box* with Flight 2.

[joe williams (joetify)]

I am having the same issue on my z60t. Dapper worked fine for me but after the upgrade the system would go into suspend and not come out. Also, note that hibernate works fine for me. I have tried both the 386 and generic kernels to no avail.

[villejuho (villejuho)]

I'm having this same issue with asus a6f laptop.. The system goes to sleep(the sleep light flashes) but doesnt come back :/

[Martin Ramsin (martin-ramsin-deactivatedaccount)]

I have the same issue on HP nc6000. It seams to only happen when running on batteries.

[Per Buer (perbu)]

I had the same issue on my z60t until i blacklisted the sdhci and the mmc_core modules. They seem broken on the z60t.

[Damian Melniczuk (quantumdamage)]

I have the same issue on toshiba satellite 1800. In addition swap partition is broken after try to run after hibernation.

[Thomas Wolfe (tomwolfe)]

just fyi, it is working now in feisty-fawn with kernel 2.6.19
only problem now seems to be that network manager after resuming says it cannot find any networking devices.

[pablodiazgutierrez (pablo-ics)]

Exactly the problem here with a Toshiba Portege m400, running 2.6.17-10. Waiting anxiously for the next release...

[Alexander Kopf (kopf-alexander)]

 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? Can you try with latest Ubuntu release? Thanks in advance.

[velikson (velikson)]

I installed Ubuntu 8.04 on my desktop a week ago . Same thing. Does not wake up from either sleep or hibernation. I do not have other systems on this computer.

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, please note that this report will remain open against the actively developed kernel. Thank you for your continued support and help as we debug this issue.

[Nick Ellery (nick.ellery)]

Does this problem still occur on the latest kernel for Hardy or Intrepid?

[velikson (velikson)]

yes it does. Hardy. No way to suspend on Toshiba A100.

On Sun, Jul 27, 2008 at 7:40 PM, Nick Ellery <email address hidden> wrote:

> Does this problem still occur on the latest kernel for Hardy or
> Intrepid?
>
> --
> machine does not wake up after suspend
> https://bugs.launchpad.net/bugs/63967
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Confirmed
> Status in "linux-source-2.6.17" source package in Ubuntu: Won't Fix
> Status in "linux-source-2.6.19" source package in Ubuntu: Fix Released
> Status in Baltix GNU/Linux: Invalid
>
> Bug description:
> I just upgraded to Edgy.
>
> I have kernel linux-image-2.6.17-10-386
>
> The machine is a ThinkPad Z60t.
>
> I did suspend the machine Fn-F4. It didn't wake up. The "sleep" light
> stayed, nothing reacted.
>
> I was running linux-image-2.6.15-19-386 without glitch.
>
> Behaviour is different from
> https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/49078that I reported a few month back
>
>
>
> Note: the original reporter indicated the bug was in package
> 'linux-image-2.6'; however, that package was not published in Baltix.
>

[Kzin (wmkzin)]

Toshiba Satellite A100-LE1
2.6.24-19-generic
ro quiet splash noapic acpi=force irqpoll
Ubuntu Hardy Heron 8.04

When system suspended the console power light and syslog indicate the system has entered suspend.
On resume console lights indicate the system has resumed, HDD light flashes.
Screen remains black, HDD light shows no activity (have seen it frozen on and frozen off)

If Fn F6 or F7 are pressed (Brightness controls) the Fn indicator light is frozen on.

Following is the syslog, including dmesg attachment.
Jul 30 18:55:36 ModylBot gnome-power-manager: (kzin) Suspending computer. Reason: The lid has been closed on AC power.
Jul 30 18:55:52 ModylBot NetworkManager: <info> Going to sleep.
Jul 30 18:55:54 ModylBot avahi-daemon[4883]: Interface ath0.IPv4 no longer relevant for mDNS.
Jul 30 18:55:54 ModylBot avahi-daemon[4883]: Leaving mDNS multicast group on interface ath0.IPv4 with address 192.168.9.100.
Jul 30 18:55:54 ModylBot avahi-daemon[4883]: Withdrawing address record for fe80::216:e3ff:fe1b:bd0d on ath0.
Jul 30 18:55:54 ModylBot avahi-daemon[4883]: Withdrawing address record for 192.168.9.100 on ath0.
Jul 30 18:55:54 ModylBot dhclient: receive_packet failed on ath0: Network is down
Jul 30 18:55:54 ModylBot dhclient: There is already a pid file /var/run/dhclient.ath0.pid with pid 5801
Jul 30 18:55:54 ModylBot dhclient: killed old client process, removed PID file
Jul 30 18:55:55 ModylBot dhclient: wifi0: unknown hardware address type 801
Jul 30 18:55:55 ModylBot dhclient: wifi0: unknown hardware address type 801
Jul 30 18:55:55 ModylBot dhclient: DHCPRELEASE on ath0 to 192.168.9.254 port 67
Jul 30 18:55:55 ModylBot dhclient: send_packet: Network is unreachable
Jul 30 18:55:55 ModylBot dhclient: send_packet: please consult README file regarding broadcast address.
Jul 30 18:55:55 ModylBot NetworkManager: <debug> [1217469355.953639] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00
_16_e3_1b_bd_0d').
Jul 30 18:55:56 ModylBot NetworkManager: <info> Deactivating device ath0.
Jul 30 18:55:56 ModylBot kernel: [ 935.075547] ACPI: PCI interrupt for device 0000:02:04.0 disabled
Jul 30 18:55:56 ModylBot kernel: [ 935.075598] ath_pci: driver unloaded
Jul 30 18:55:56 ModylBot kernel: [ 935.215478] ACPI: PCI interrupt for device 0000:02:07.0 disabled
Jul 30 18:55:57 ModylBot NetworkManager: <WARN> nm_device_802_11_wireless_get_mode(): error getting card mode on ath0: No such device
Jul 30 18:55:57 ModylBot NetworkManager: <debug> [1217469357.414749] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00
_16_e3_1b_bd_0d_0').
Jul 30 18:55:57 ModylBot NetworkManager: <debug> [1217469357.414850] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00
_a0_d1_3b_25_03').
Jul 30 18:55:57 ModylBot NetworkManager: <info> Deactivating device eth0.
Jul 30 18:55:57 ModylBot kernel: [ 936.791924] ACPI Error (evxfevnt-0383): Could not disable RealTimeClock events [20070126]
Jul 30 19:01:34 ModylBot syslogd 1.5.0#1ubuntu1: restart.

[Leann Ogasawara (leannogasawara)]

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.

[Kzin (wmkzin)]

I tested and the problem persists with the same behavior =(

I tried 2.6.27-2-generic but when I booted back up into 2.6.24-19-generic, I got a crash report.
See https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/263765 for the report (I just let the automated post a bug system do its thing, and it created a new bug).
I wonder if that is related?

[Kzin (wmkzin)]

Ok, I doubt that bug in the last post is related at all; it is some known bug that a lot of people have reported already.

I added noapic acpi=force irqpoll back onto my kernel parameters with the 2.6.27-2-generic kernel and I managed to get an error message when I pressed the suspend button.

The screen turns black w/ a flashing cursor, after a few seconds an error jumps up, a little too quick to see, and then another error, also too quick to see...

The second one was something along the lines of "Freezing of tasks failed after 20 seconds, SERR action 0x0, DRDY err ata4.00
Thats about all I could see.

Then the awesome part; I can't get it to give me the error again, it is now doing the same old suspend light comes on, flashes, won't resume w/out disconnecting power and battery then restarting.

I am adding the kernel log just in case it helps anything, its unedited so its pretty big.

[hbernard (hbernard)]

Confirmed on a Toshiba A100 (suscribing for further testing)

[Kzin (wmkzin)]

Confirmed working or confirmed broken?
What kernel did you use?

[hbernard (hbernard)]

Confirmed broken. My Toshiba A100 doesn't resume after suspend
Current Kernel : 2.6.24-21-generic

I will try with the kernel 2.6.27 as soon as I have some time.

[Leann Ogasawara (leannogasawara)]

Thanks everyone. Hubert, since you are the original bug reporter, would you be able to test the latest Alpha5 release. You should be able to test Suspend via a LiveCD. Please let us know your results. Thanks.

[Kzin (wmkzin)]

I have something interesting to report.

I did an apt-get update, apt-get dist-upgrade today. Down came the 2.6.27-3 generic. The machine still doesn't wake up after suspend, (with or without the noapic acpi=force irqpoll) BUT, the computer was on and running doing its regular thing when the battery died. So the machine went into either hibernate or suspend because when I plugged in the adapter and powered on, the system load splash said "Waking up. Please wait... ".

This prompted me to attempt hibernate instead of suspend.

I switched the lid switch to go to hibernate and sure enough hibernate works now. Suspend is still broken, but at least I can make my puter save its running state when I close the lid now.
= ^ . ^ =

[Damian Melniczuk (quantumdamage)]

Maybe this will help: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293288/comments/5

[Wil (wiljohnson38)]

Thanks for the update -- I hope this will be incorporated in the next release.

-----Original Message-----
From: "Damian Melniczuk" [<email address hidden>]
Date: 01/22/2009 05:40 PM
To: <email address hidden>
Subject: Re: [Bug 63967] Re: machine does not wake up after suspend

Note: Original message sent as attachment

------------------------------------------------------------
Medical Transcription Training
Become a medical transcriptionist at home, at your own pace.
http://tagline.excite.com/fc/BK72PcZanRiEraHFBnhkBXwE0KuyadCZNqcTfcf7QRzdz3Vf6Hwxp3/

Maybe this will help:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293288/comments/5

--
machine does not wake up after suspend
https://bugs.launchpad.net/bugs/63967
You received this bug notification because you are a direct subscriber
of a duplicate bug.

5LVZ1bGY

[TJ (tj)]

The key to this issue may be given by the following clue from /var/log/kern.log:

ACPI Error (evxfevnt-0383): Could not disable RealTimeClock events [20080609]
ACPI: RTC can wake from S4

Which, if it is indicating the root cause, indicates a 'bad' ACPI DSDT.

If you're experiencing this issue with Hardy, Intrepid or Jaunty could you please search the logs after recovering from this issue and report the results:

grep '\(ACPI Error\|RealTimeClock\|RTC can wake\)' /var/log/kern.log{,.0} | tee /tmp/lp63967.log

If that shows results attach /tmp/lp63967.log to this bug report.

[Wil (wiljohnson38)]

Could not find that particular error but did find these errors in kern.log:
(log attached)
Mar 7 19:31:15 wil-desktop kernel: [ 917.900170] ACPI handle has no context!
Mar 7 19:31:15 wil-desktop kernel: [ 919.192908] ohci_hcd 0000:00:02.0: wake-up capability disabled by ACPI
Mar 7 19:31:15 wil-desktop kernel: [ 986.505392] WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
19:31:15 wil-desktop kernel: [ 986.505392] WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80() state_store+0x0/0xd0
Mar 7 19:33:04 wil-desktop kernel: [ 0.000000] ACPI Warning (tbfadt-0442): Optional field "Pm2ControlBlock" has zero address or length: 0000000000000000/1 [20080609]

-----Original Message-----
From: "TJ" [<email address hidden>]
Date: 02/27/2009 04:58 PM
To: <email address hidden>
Subject: Re: [Bug 63967] Re: machine does not wake up after suspend

Note: Original message sent as attachment

------------------------------------------------------------
Learn digital and video photography techniques, lighting and printing. Click now.
Photography School
http://tagline.excite.com/fc/FgElN1g44JfaVnAdM8BpgO3oxkjYV13Kio6dTfbXf1ksfU6OQkU64Z5z8qM/

The key to this issue may be given by the following clue from
/var/log/kern.log:

ACPI Error (evxfevnt-0383): Could not disable RealTimeClock events [20080609]
ACPI: RTC can wake from S4

Which, if it is indicating the root cause, indicates a 'bad' ACPI DSDT.

If you're experiencing this issue with Hardy, Intrepid or Jaunty could
you please search the logs after recovering from this issue and report
the results:

grep '\(ACPI Error\|RealTimeClock\|RTC can wake\)'
/var/log/kern.log{,.0} | tee /tmp/lp63967.log

If that shows results attach /tmp/lp63967.log to this bug report.

--
machine does not wake up after suspend
https://bugs.launchpad.net/bugs/63967
You received this bug notification because you are a direct subscriber
of a duplicate bug.

YnVud!

[Andi (andi2005)]

Linux turbix 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux

[Ruud (spamming-email)]

I have the same problem.
I've installed Ubuntu 9.10 on a Laptop (Asus K70IO)
I have set the power settings to "When the laptop lid is closed": Suspend
Everytime when I close the lid, the laptop is goes in standby, but when I start the laptop again, the screen stays blank and the only i can do is to hold the power button for 5 seconds so the laptop gets a hard power off.
I've attachted a part of the /var/log/kern.log

It says that the wakeup process is completed:
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.210131] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.263914] ata1.00: configured for UDMA/133
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.263928] ata1: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x9 t4
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.263931] ata1: irq_stat 0x00400040, connection status changed
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.267943] ata1.00: configured for UDMA/133
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.267947] ata1: EH complete
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.284137] PM: resume devices took 0.920 seconds

So it seems to be the process after wakeup.
Than it produces the following messages at it hangs:

Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.301372] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.343993] ata2.00: configured for UDMA/100
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.344888] ata2: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x9 t4
Nov 24 00:44:12 RUUD-LAPTOP2 kernel: [15922.345100] ata2: irq_stat 0x40000001

~$ dmesg

[ 1.700064] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.700081] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.704785] usb 1-5: configuration #1 chosen from 1 choice
[ 1.717517] ata2.00: ATAPI: TSSTcorp CDDVDW TS-L633C, AS00, max UDMA/100, ATAPI AN
[ 1.717532] ata2.00: applying bridge limits
[ 1.734063] ata2.00: configured for UDMA/100
[ 1.745275] ata1.00: ATA-8: ST9320325AS, 0002SDM1, max UDMA/133
[ 1.745280] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 1.747360] ata1.00: configured for UDMA/133
[ 1.747526] scsi 0:0:0:0: Direct-Access ATA ST9320325AS 0002 PQ: 0 ANSI: 5
[ 1.747651] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.747666] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 1.747709] sd 0:0:0:0: [sda] Write Protect is off
[ 1.747711] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.747734] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.747853] sda:
[ 1.749395] scsi 1:0:0:0: CD-ROM TSSTcorp CDDVDW TS-L633C AS00 PQ: 0 ANSI: 5
[ 1.755272] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 1.755277] Uniform CD-ROM driver Revision: 3.20
[ 1.755397] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 1.755459] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 1.757029] sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
[ 1.794330] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.794347] Freeing unused kernel memory: 660k freed
[ 1.794605] Write protecting the ...

[Regulas (regulas1)]

My Acer Extensa now has problems waking up from sleep with 9.10 64 bit. There was no issue on this subject using 8.10 or 9.04 32 bit with the same laptop. When I open up my laptop hit a key to wake the computer, I have to wait for it to noisily check my empty DVD drive before it will give me login screen then about 90% of the time when I start to log in it goes black and back into sleep mode. It always works the second though.

[Orhan Ocal (orhanocal)]

Same thing happens on my HP Pavillion dv9000 laptop with Ubuntu 9.10 Karmic Kaola.

[Mark Gould (mark-e-gould)]

Unlike many of those posting, the failure to wake from hibernation or sleep has been persistent, from original installation through updates on my netbook, Dell Mini Inspiron 1012. I am hoping for a fix someday that will prevent me from having to have all my work frozen and to reboot, or, to remember to shut down the computer every time I use it.

(That's really the only problem I have.. I love Ubuntu!)

Mark

[Luke Caputo (l.caputo)]

i have been using ubuntu consistently since 2006-2007 and i have never owned a computer that would wake from sleep. it is a pretty annoying bug that has sat on the back-burner for years.

i also have a dell mini 1012 and can duplicate the comment from @Mark.

Dell Mini 1012
Ubuntu 10.10

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Chris Cantwell (cjc1103)]

I have been unable to get various versions of Ubuntu to suspend on three different laptops over the years: Unbuntu 10.10 and 11.04 on a Dell Latitude 630, Ubuntu 11.10 and Xubuntu 12.04 on a Dell Latitude E6500, and now Xubuntu 12.10 on a Dell E6510. After the laptop goes into suspend mode, it won't wake up - just displays a blank screen, sometimes a mouse under a cursor. From the posts on this and other websites, it seems like a lot of people are having similar problems on all kinds of different laptops and Ubuntu versions. Obviously the suspend function is broken. Maintainers should not need all kinds of debugging information, they should be able to reproduce this on their own laptops. Does anyone have a laptop that handles wakeup from suspend mode properly with Ubuntu (any version/flavors)?

[Charlie Kravetz (cjkgeek)]

My Asus seems to work fine, with all xubuntu versions since 8.04. Of course, maybe it just isn't new enough to have issues with suspend. I have been unable to reproduce this issue, myself. I have one laptop and two desktops that seem to be able to wake from suspend.

[velikson (velikson)]

Well, I do not know in what world you live. Most computers I tried DO NOT
WAKE UP AFTER SUSPEND on Ubuntu, any version. It is so frequent that few
people even try to install Ubuntu on a laptop - simply because on a desktop
it is easier to live with that, you can just systematically turn it off.
Most of us user have simply given up. This is real world.

On Sun, Oct 28, 2012 at 7:16 PM, Charlie Kravetz <email address hidden>wrote:

> My Asus seems to work fine, with all xubuntu versions since 8.04. Of
> course, maybe it just isn't new enough to have issues with suspend. I
> have been unable to reproduce this issue, myself. I have one laptop and
> two desktops that seem to be able to wake from suspend.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/63967
>
> Title:
> machine does not wake up after suspend
>
> Status in “linux” package in Ubuntu:
> Won't Fix
> Status in “linux-source-2.6.17” package in Ubuntu:
> Won't Fix
> Status in “linux-source-2.6.19” package in Ubuntu:
> Fix Released
> Status in Baltix GNU/Linux:
> Invalid
>
> Bug description:
> I just upgraded to Edgy.
>
> I have kernel linux-image-2.6.17-10-386
>
> The machine is a ThinkPad Z60t.
>
> I did suspend the machine Fn-F4. It didn't wake up. The "sleep" light
> stayed, nothing reacted.
>
> I was running linux-image-2.6.15-19-386 without glitch.
>
> Behaviour is different from
> https://launchpad.net/distros/ubuntu/+source/linux-
> source-2.6.15/+bug/49078 that I reported a few month back
>
>
> Note: the original reporter indicated the bug was in package 'linux-
> image-2.6'; however, that package was not published in Baltix.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/63967/+subscriptions
>