Acer Aspire One 721Ubuntu Maverick 10.10 beta, 32bit When putting the laptop into standby, everything works - the screen and -backlight are deactivated and the power led flashes slowly. When trying to resume, the power light comes back to it's normal state, but neither the harddrive LED nor the screen are reactivated. This happens every time. I ran the system through this test: https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume stage 1: The system does start going into standby (deactivating screen), but does not really go into standby (where the power LED would slowly blink). After the screen goes on again, I have the following problems: - touchpad running wild (touching it opens multiple new windows, etc) - wireless is deactivated in nm-applet Stage 2 test: - no resume possible (any button presses have no effect), the system stays in standby (no return of the power LED from slowly flashing to "on" state) Stage 3 test - same effects as the normal standby: no resume possible (the power LED comes back from slowly blinking to "on" state, but screen stays blank) **** 2.6.37-rc2 tested, not working *****
> When putting the laptop into standby, everything works can you show me the steps you did to put the laptop into standby?
Zhang, Press the Suspend hot-key. You may also disconnect AC power and close the lid to cause it to suspend. You may need verify your options in your power management preferences. I have mine set to suspend if I hit the suspend hot-key, and to hibernate if I hit the power button. While on battery, I also have it set to suspend when I close the lid. --Steve
so I assume you are talking about "suspend to memory" when you said "standby" in comment #0. could you please tell me what exactly you did in the stage 1,2,3 test?
ping.
Reply-To: steve@codersteve.com Yes, different hardware manufacturers and different operating systems call it different things. My acer refers to it as the "Sleep" button. This problem also applies to hibernating. I am not the one who filed the original report. I don't know anything about the stage 1,2,3 tests referred to in comment #0, but it would appear these stages refer to the instructions in the link provided there, in comment #0. I presume the author of comment #0 can be contacted through the originating bug report at bugs.launchpad.net #642091 <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642091?comments=all>, which was derLars. I suppose someone pasted his comment #0 from that report into this new kernel bug report. There is a great deal of information in the originating bug report, maybe some of the answers you seek are there? Anyway, you might get a better response by asking your questions there, at least until more of the participants realized that this problem has been assigned to a different forum. --Steve On 12/26/2010 08:06 PM, bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=24032 > > > > > > --- Comment #4 from Zhang Rui<rui.zhang@intel.com> 2010-12-27 02:06:43 --- > ping. >
Workaround: boot with nohpet. The failure to resume from ACPI S3 (Suspend to RAM) seems to be related to the HPET subsystem. I had this problem: suspend worked, and on resume the light would stop blinking orange and go solid blue, but the screen would stay off and the system was not responsive to input - had to hold the power switch down for four seconds to cycle power. I've submitted it on the kernel mailing list, but in the meantime, booting with the "nohpet" option on the kernel command line allows resume to work for me. Alternatively, make sure CONFIG_NO_HZ and CONFIG_HI_RES_TIMERS are not set in your kernel. These two options (in Processor Type and Features) seem to expose this bug.
Thank you, James. The 'nohpet' workaround works perfectly on Acer Aspire One 721 running Ubuntu with 2.6.35-24-generic x86_64. Both ACPI states (S3 and S4) are usable now.
Credit belongs to Borislav Petkov, at amd64.org, but I'm glad to hear it worked for you. Cheers, James
Zhang, do you still need more info, or can we update the status of this bug? --Steve
I am seeing the same thing in 2.6.38-rc4. The system is Dell Latitude E6510. It seems to go to sleep with the power led blinking slowly but when I wake it up, the power led comes on (no blinking anymore) but the system is sort of dead. No keys work. I can't hear any sounds like any fans running. Of course, there is no display and sysrsq doesn't work either. Only way out is to long press the power button. The only other kernel I have is 2.6.36 which suspends and resumes fine. Let me know what information your need to debug this.
It's great that kernel bugzilla is back. can you please verify if the problem still exists in the latest upstream kernel?
bug closed as there is no response from the bug reporter. please feel free to reopen it if the problem still exists in the latest upstream kernel.