[HP nx9010] laptop won't resume from suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Never successfully managed to get suspend or hibernation working with my laptop whilst host O/S is Ubuntu. Recently installed 9.04 (Jaunty) and noticed this wiki page:
[url]https:/
Followed the instructions for starting Apport and then ran:
> sudo bash /usr/share/
First test was a 20 sec suspend:
1) My laptop suspended ok, but failed to wake-up/resume.
2) It is very repeatable, failing at the same point.
3) Both suspend and hibernate have worked with MS Windows but never Ubuntu.
4) No flashing caps lock. Once resume started fans came on, hard drive light flickered once, but no display.
5) Battery was about 60% full, but for first test AC cord was attached.
Let me know if you need any more info from my setup. Hopefully the Apport report gets attached here...
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/
Failure: suspend/resume
HibernationDevice: RESUME=
InterpreterPath: /usr/bin/python2.6
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard HP nx9010 (DJ347A)
Package: linux-image-
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux
Tags: resume suspend
Title: [Hewlett-Packard HP nx9010 (DJ347A)] suspend/resume failure
UserGroups:
affects: | ubuntu → linux (Ubuntu) |
Could you please follow the triage and debugging guide (https:/ /wiki.ubuntu. com/DebuggingKe rnelSuspendHibe rnateResume) and report back here. From the logs attached it seems we got all the way to suspend and never came back at all, so you can probabally skip to the more detailed debugging later in the page. Thanks!