resume from suspend doesn't work (powers off instead) for Acer Aspire 3810T
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
Arch Linux |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Debian) |
Fix Released
|
Unknown
|
|||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Resume from suspend (to RAM) doesn't work (powers off instead on resume, didn't touch the power button) for Acer Aspire 3810T.
WORKAROUND: Add the i8042.reset=1 kernel parameter in GRUB. To do this, change the GRUB_CMDLINE_
GRUB_CMDLINE_
and execute "sudo update-grub"
Seems to be working for Acer Aspire 3810T.
Core 2 Solo (or Duo, both have this problem) ULV, Mobile Intel® GS45 Express Chipset, Intel Wifi 5100.
I have tried 9.04, 9.10 alpha 2 and 3, kernels 2.6.28 to 2.6.31, all 32-bit. BIOSes 1.04 and 1.08 (latest). Nothing works.
There is a single isolated report of suspend working with 64-bit 2.6.30.
https:/
Suspend seems to work perfectly, but when a key is pressed to start resuming, the machine seems to start back up, but automatically powers off afer a few seconds (screen didn't come back up).
Using the "resume-trace" procedure described here does not yield any matches. Unloading all non-essential modules in single user mode doesn't fix it (used /etc/acpi/sleep.sh to initiate suspend).
Suspend is initiated through gnome-power-
Architecture: i386
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
MachineType: Acer Acer Project
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSign
RelatedPackageV
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/27/2009
dmi.bios.vendor: Acer
dmi.bios.version: V1.04
dmi.board.
dmi.board.name: Acer Project
dmi.board.vendor: Acer
dmi.board.version: PSMBOU-1234567
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Acer Project
dmi.product.
dmi.sys.vendor: Acer
summary: |
- resume from suspend doesn't work (powers off instead) for Acer Timeline - 3810t/3410t + resume from suspend doesn't work (powers off instead) for various Acer + Timeline laptops |
description: | updated |
description: | updated |
description: | updated |
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Incomplete |
Changed in linux: | |
status: | Incomplete → In Progress |
Changed in linux: | |
status: | In Progress → Incomplete |
Changed in linux: | |
status: | Incomplete → Fix Released |
summary: |
- resume from suspend doesn't work (powers off instead) for various Acer - Timeline laptops + resume from suspend doesn't work (powers off instead) for Acer Aspire + 3810T |
tags: | added: jaunty karmic needs-upstream-testing |
description: | updated |
description: | updated |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Changed in linux: | |
importance: | Medium → Undecided |
status: | Fix Released → New |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
Changed in linux (Ubuntu Quantal): | |
status: | New → Fix Released |
Changed in linux (Ubuntu Raring): | |
status: | Incomplete → Fix Released |
Changed in linux (Debian): | |
status: | Unknown → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeam/ KernelTeamBugPo licies Thanks in advance!