[Acer TravelMate 4000] suspend/resume failure during wakeup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HAL |
Fix Released
|
Medium
|
|||
hal (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
system apparently goes to sleep fine.
when I hit a key
- fan start
- backlight turns on
- hdd-led flashes a couple of times
thats it. no image, no reaction to caps-lock.
I managed to get resume to work with the proprietary fglrx driver, so its probably an ati graphics issue. I'll provide more detailed debugging infomation later today.
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
InterpreterPath: /usr/bin/python2.6
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
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: Acer TravelMate 4000
Package: linux-image-
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/
Tags: resume suspend
Title: [Acer TravelMate 4000] suspend/resume failure
UserGroups:
Changed in hal: | |
status: | Unknown → Confirmed |
Changed in hal: | |
status: | Confirmed → Fix Released |
affects: | linux (Ubuntu) → hal (Ubuntu) |
Changed in hal: | |
importance: | Unknown → Medium |
Changed in hal: | |
importance: | Medium → Unknown |
Changed in hal: | |
importance: | Unknown → Medium |
As explained here: /wiki.ubuntu. com/DebuggingKe rnelSuspend
https:/
I ran pm_trace; pm-suspend
sudo -i; sync; echo 1 > /sys/power/
As expected resume would work, as detailed above. after powering down, rebooting, loggin in, and starting a terminal dmesg produced dmesg.txt
There is no line matching "hash matches". did I do something wrong?