Cant wakeup the Computer from sleep

[The Liquidator]

Thanks

Here's the output from an attempt I just made to suspend. Suspend appeared successful until I tried to wake it up. Does this tell you anything helpful?

There are a number of files (5) in var/log incorporating PM. 3 realte to suspend and the other 2 to powersave. A couple of them seem quite old.

I'll try the other kernel options and come back.

[SecretCode]

The line that concerns me is

Having NetworkManager put all interaces to sleep...Failed.

I would have expected this to make the suspend itself not complete, but it's as likely to be an explanation for resume not working.

What is your network hardware according to lspci?

[SecretCode]

There are a number of files (5) in var/log incorporating PM. 3 realte to suspend and the other 2 to powersave. A couple of them seem quite old.

I meant lines in the file /var/log/messages ... but I see to my surprise that my current installation doesn't have such a file. Odd. Try

grep PM /var/log/syslog
grep PM /var/log/dmesg

[lindaonline15]

And the same thing happens when you hibernate too?

sometimes, yes.
I also have to point out here this problem with both sleep and hibernate actually comes and goes..

[SecretCode]

You mean sleep and hibernate sometimes work and sometimes fail? That makes it harder! (As I commented in another discussion, I think here, "intermittent" problems are the worst kind.)

It probably means that it's a timeout issue - some component (e.g. the wireless interface, that seems to be the culprit most often) does not always go into the requested low-power or power-off state quickly enough, and then the state is inconsistent on resume.

You can sometimes overcome this by getting more explicit control of the powering-off and powering-on through scripts in /etc/pm/ but it seems to be a black art to me with every case being different. - Nevertheless, knowing your exact hardware (lspci) can help with web searches for possible solutions.

[lindaonline15]

it just happened just now...
laptop was sleep, i tried to wake it up by pressing a button, it was still black, suddenly the fan's noise went so high you would think its gonna explode! and it shutted down itself!!
i just looked at the logs and pasted in paste bin here:

#grep PM /var/log/syslog:
http://pastebin.com/APLaFPxc

#grep PM /var/log/dmesg:
http://pastebin.com/Spseprnv

my lspci is:

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
01:00.0 VGA compatible controller: ATI Technologies Inc Manhattan [Mobility Radeon HD 5400 Series]
01:00.1 Audio device: ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series]
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller
03:00.1 System peripheral: Ricoh Co Ltd Memory Stick Host Controller
03:00.4 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller
04:00.0 Ethernet controller: Marvell Technology Group Ltd. Yukon Optima 88E8059 [PCIe Gigabit Ethernet Controller with AVB] (rev 11)
3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

[lindaonline15]

i have to add... the incident happened on 13:04... so in syslog do look for that timestamp... which i think the exact line is line #102 in syslog pastebin in my previous post...

[SteveRiley]

it just happened just now...
laptop was sleep, i tried to wake it up by pressing a button, it was still black, suddenly the fan's noise went so high you would think its gonna explode! and it shutted down itself!!

I have recently noticed the same problem on my Thinkpad X1. It started occurring last week, and happens every time. Thus, I've disabled sleep for now.

[SecretCode]

I don't have much time to look into possible workarounds at the moment, but it does look like it could be related to particular hardware.

Did you manage to try with those kernel boot options (a few posts back)?

One other thing to try is booting with an earlier kernel. I had a problem with Ubuntu 10.10 where I could only successfully hibernate and resume on kernels 2.6.35-25 or earlier - so I couldn't use the later updated kernels

[The Liquidator]

I've just tried the boot options, here is what happened:

acpi=off

On reboot display was cut back from 1280x800 to 1024x768 with no possibility of changing it. On pressing the battery icon and selecting sleep I got absolutely nothing

pcie_aspm=off

This was interesting. I got my full-size screen back. On clicking sleep it went to sleep or appeared to do so - the powered up LED going on and off very slowly. On wake-up I got the following

Full desktop (couldn't check it was working)
2 seconds later black desktop with working cursor
5 seconds later full desktop again but almost immediately got the following error message:
"The process for the desktop protocol died unexpectedly". At this point the desktop had frozen completely and the only input that seemed to do anything was REISUB.

[SecretCode]

I am astonished that the acpi option would change the screen resolution ... weird. But I can see that it might prevent the power features from working at all (although if I'd thought that in advance I wouldn't have bothered suggesting it!)

pcie_aspm looks more promising. I think a slow-blinking power LED is definite confirmation of sleep state.
The failure to restart might be something fixable ... unfortunately there are hundreds of bug reports and forum threads for that error message so I think it's one of those generic messages.

[The Liquidator]

Yes, I am quite happy that the computer goes to sleep - so far as I can recall when trying it has always exhibited the slow blinking LED- but since I got it 6 years ago I have never done a successful wake-up. Hibernation (my shut lid option) is a different matter - that works fine.

[SecretCode]

So the pcie_aspm option didn't really make any improvement?

[The Liquidator]

Afraid not

[SecretCode]

All I have left is trying earlier kernels ... or searching high and low across the net for possible scripts to add to /etc/pm/ for your particular hardware ...