Suspend does not work on my laptop (Dapper)

Bug #49396 reported by Ryan T. Sammartino on 2006-06-11
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.15-23-686

Configuring my laptop to suspend on lid close, or selecting Suspend from the System|Quit menu, causes the laptop to suspend properly (or so it seems), but it never wakes (all the way) up.

Suspend seems OK as the audio makes a little "click", the fans turn off, the hard drive stops spinning, and the Power LED starts flashing (which means "suspended").

However, clicking the power button to resume (or opening the lid) results in the following behaviour:

- Audio clicks again (sound card turning back on?)
- Hard drive spins, some activity is noticed
- Fans start blowing
- Power LED goes solid green (which means "normal activity, plugged into AC")
- Screen stays black
- Caps lock light goes on, off when pressing Caps lock, which seems to indicate that the kernel and X are alive. However, after a minute or two, this stops working (kernel dies? X dies?), and the only way to get the system back is to power down.

I will attach all the relevent entries in /var/log/ pertaining to the suspend event, as well as dmesg and lspci output.

You will note in the log that it looks like networking tries to come back up after wake up, but no matter how quick I was I could not ping or ssh into the machine from another on my network.

None of the options in /etc/default/acpi-support (and restarting acpid, acpi-support) make any difference to the behaviour. Adding "Option VBERestore true" to /etc/X11/xorg.conf, as suggested by some articles found while Googling, did not help.

This laptop was also running Breezy where suspend didn't work either (except under Breezy, the laptop would show no signes of life after attempting to wake it up).

lscpi output for this laptop.

dmesg output

Chuck Short (zulcss) wrote :

What kind of laptop is this?

Changed in linux-source-2.6.15:
status: Unconfirmed → Needs Info
Matthew Garrett (mjg59) wrote :

Can you test with the nv driver rather than the nvidia one?

Using the nv driver actually performs worse; upon (attempted) resume, the Caps Lock key does nothing, indicating dead kernel and/or X.

Stéphane Marguet (stemp) wrote :

Are you still experiencing this issue ?

Any attempts to suspend with an up-to-date Edgy install on this laptop result in the screen just locking. When I unlock with my password, a pop-up informs me that suspend failed.

So, at least I don't need to reboot.

Launchpad Janitor (janitor) wrote :

[Expired for linux-source-2.6.15 (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers