Ubuntu
linux-source-2.6.20 package

Acer Aspire 5652 WLMi doesn't wake up from suspend to ram

Bug #46292 reported by Marcel Saatkamp
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

The system enters the low-power state without any problem but you can't wake it up again.

Revision history for this message
Tero Karvinen (karvinen+launchpad) wrote :

Please be more specific. What works after wake up, what does not? Can you change caps light state, is fan running, can you ssh to machine, is screen backlight on... Also, how did you know that the computer entered suspend-to-ram? How did you initate suspend?

I have a very similar prolem on Acer Travelmate 3000 on bug #46064. Hope it gets a fix soon.

Revision history for this message
Marcel Saatkamp (marcel-saatkamp) wrote :

It's hard to say what works and what not. The screen stays black. The fans don't run but thats normal. They only run when playing games.

Maybe just the screen stays black. I don't know.

I initiate suspend by clicking Log out -> "Ruhezustand" (German Ubuntu)

You could try this:
http://www.ubuntuforums.org/showthread.php?p=1046684#post1046684

I can't atm.
Plz say if it helps.

Sorry for my poor english.

Revision history for this message
Marco Rodrigues (gothicx) wrote :

The same happen to my ACER Aspire 5633 WLMi at Feisty with all updates. If developers need someone for testing, I can do it...

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please 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" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "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 http://wiki.ubuntu.com/KernelTeamBugPolicies

Thanks in advance!

Changed in linux-source-2.6.20:
importance: Medium → Low
Revision history for this message
Kees Cook (kees) wrote :

Also, please see https://wiki.ubuntu.com/DebuggingACPI and https://wiki.ubuntu.com/DebuggingKernelSuspend

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.