Laptop does not wake up from S3 suspend mode

Bug #86852 reported by Rune Evjen
18
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned
linux-source-2.6.22 (Baltix)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

This bug has occurred under the following setups:

Ubuntu Edgy with 2.6.17.10-generic kernel
Ubuntu Edgy with suspend2 patched kernel
Ubuntu Feisty with 2.6.20-8-generic kernel
Ubuntu Feisty with suspend2 patched 2.6.20-6-generic kernel

It has been tested with nv and nvidia driver (nvidia-glx package).

My laptop is a Lenovo 3000 N100 type 0768-BJG with the latest BIOS firmware.

On Edgy I got dmesg error messages about DSDT table, but they dissappeared running feisty.

Under Edgy the laptop does not resume, nothing happens except for giving me a "unlock dialog" from Gnome.
In Feisty the laptop does suspend, but when i hit the power button to resume the sleep led disappears, the fan spins up and down and the cd-rom spins up for a couple of seconds and then nothing happens.

The screen remains black and the computer does not respond. Hitting caps lock key does not light the Caps Lock led indication.

Hibernation works using Feisty kernels without suspend2 patch, using stock nv driver and using nvidia driver when using agp=off as a kernel parameter.

Hibernation does not work under Edgy.

I got a mysterious "tick" sound from my hard driver every couple of minutes under edgy, so I went for running only feisty since it seems stable on my computer.

I can provide any relevant log needed using Feisty kernels.

My Feisty installation is stock except for running Compiz and VMWare server.

Regards,

Rune Evjen

Revision history for this message
Rune Evjen (rune-evjen) wrote : Attachments: Laptop does not wake up from S3 suspend mode

Looking through other S3 posts I attach the following:

Revision history for this message
Rune Evjen (rune-evjen) wrote :
Revision history for this message
Rune Evjen (rune-evjen) wrote :
Revision history for this message
Rune Evjen (rune-evjen) wrote :
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

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

Please include the information requested from https://wiki.ubuntu.com/DebuggingACPI as separate attachments.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

* Change Package of Ubuntu to linux-source-2.6.20.
* Change Status of Unconfirmed to Needs Info.
* Change "Assigned To" of Nobody to Cristian.

Revision history for this message
Rune Evjen (rune-evjen) wrote :

Thank you for your reply!

BIOS is updated to latest version. (V2.03, 6 dec 2006)

uname -a:
Linux feisty-laptop 2.6.20-6-generic #1 SMP Mon Feb 5 15:42:24 CET 2007 i686 GNU/Linux

Revision history for this message
Rune Evjen (rune-evjen) wrote :
Revision history for this message
Rune Evjen (rune-evjen) wrote :
Revision history for this message
Rune Evjen (rune-evjen) wrote :
Revision history for this message
Rune Evjen (rune-evjen) wrote :

When I read kern0.log I noticed that it didnt't include the last two days, so here is ker.long if this helps you.

Thanks for helping out!

Rune

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

* Change "Assigned To" of Cristian to kernel-bugs

Changed in linux-source-2.6.20:
assignee: caravena → kernel-bugs
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Change "Assigned To" of kernel-bugs to ubuntu-kernel-team.

Changed in linux-source-2.6.20:
assignee: kernel-bugs → ubuntu-kernel-team
Revision history for this message
Rune Evjen (rune-evjen) wrote :

I searched a bit and followed the guide in https://wiki.ubuntu.com/DebuggingKernelSuspend

I captured the dmesg output and got 2 lines similar to the Wiki page:

[ 1.814882] ACPI: (supports S0 S3 S4 S5)
[ 1.815497] Magic number: 15:874:554
[ 1.815649] hash matches device ptya0

The Wiki page says that the only solution is to remove the module, but I am not sure how to do this with ptya0, which is not a module but a pseudo-tty ?

Hope this is useful.

Regards,

Rune Evjen

Revision history for this message
Tim Gardner (timg-tpi) wrote :

'[ 1.815649] hash matches device ptya0' is a false positive. We are still working on this kind of resume failure.

Revision history for this message
Ben Collins (ben-collins) wrote :

Bugs assigned to the kernel team should only be Confirmed. Needs Info should be assigned to person that requested the info.

Changed in linux-source-2.6.20:
status: Needs Info → Confirmed
importance: Undecided → Medium
Revision history for this message
Vivian Stewart (vivichrist) wrote :

I also have this problem but only when I have some sort of opengl related screensaver, compiz, beryl etc. and would like to know if there is a work around.

HP Compaq v6001au - nvidia 6150

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

vivichrist:
You probably want bug #96240 ...

Rune:
If disabling AGP helps then this sounds like Bug #34043 ...

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

Lenovo N100, I confirm all the problems reported.

Revision history for this message
Aethralis (aethralis) wrote :

I confirm: Lenovo 3000 N100 0768 does not wake up from either suspend or hibernate (7.10 Gutsy Gibbon beta)

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

Same problem on Gutsy 64bit. Are the things ever going to change?

Revision history for this message
Jackdaw28 (simoncsoka) wrote :

Forgive me if I'm teaching you to suck eggs, but have you tried the options here: https://help.ubuntu.com/community/NvidiaLaptopBinaryDriverSuspend

Option "NvAGP" "1" did it for me with a Samsung X10 and nvidia-glx under both feisty and gutsy.

Revision history for this message
Vivian Stewart (vivichrist) wrote :

there's a bit more to it than that. for me its modal specific stuff. like adding quirks and installing pm-utils as well as what you just mentioned that fixed it

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

I hate so say this, but none of the provided solutions allowed me to wake from suspend-to-ram on 64bit Gutsy.

Revision history for this message
Vivian Stewart (vivichrist) wrote :

for me the provided solutions make things better but still get the odd non-responding resume

Revision history for this message
Vivian Stewart (vivichrist) wrote :

my advice is to use xserver-xgl which has its own set of problems but ....

Revision history for this message
Vivian Stewart (vivichrist) wrote :

na still happens

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron Alpha2 release will be coming out soon. It will have an updated version of the kernel. It would be great if you could test with this new release and verify if this issue still exists. I'll be sure to update this report when Alpha2 is available. Thanks!

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Closing suprious task against Baltix.

Changed in linux-source-2.6.22:
status: New → Invalid
Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

Hardy Alpha2 tested. The issue still persists in all glory.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Per the kernel team's bug policy, can you please attach the following information for the newer Hardy kernel:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :
Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :
Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :
Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Also, as mentioned in an earlier comment, the following wiki might help: https://wiki.ubuntu.com/DebuggingKernelSuspend . Can you follow the "Debugging procedure" section and attach your dmesg output after you attempt to suspend/resume. It might provide more useful information. Thanks!

Revision history for this message
Vivian Stewart (vivichrist) wrote :

On gutsy this problem seems to be linked to the mouse cursor. I recently changed my settings but ended up with the default X cursor (Artwiz in my case) and this seems to have fixed the problem. for me any way.

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

I duly apologize for not reporting in for two weeks — the New Year and Christmas (which is January 7 in Russia) kicked me off a good deal. Well, now I finally have a lot of new information here.

First of all, I should say that running the latest Hardy available at this moment (that is, 2.6.24-3-generic 64bit kernel) I finally succeeded to wake up from STR! There's no sound after resume (the corresponding lines follow), but otherwise resuming went just grand.

 * Setting up ALSA... [ OK ]
FATAL: Module acpi_sbs not found.
FATAL: Module acpi_sbs not found.

I should mention that Hardy currently fails to load ipw3945 kernel module, thus denying the WLAN functionality (see bug #181638 for details). This can well be the WLAN that didn't allow the system to wake up previously (but that surely is my own ill-based guess).

Anyway, I guess we suddenly have a serious progress on the matter, and I'm eager to provide any information that can help solving STR problems completely before Hardy hits the mirrors. To my great pity, I'm not that good on debugging myself, so I need to be guided by someone who knows what needs to be done. Leann?

Revision history for this message
Rune Evjen (rune-evjen) wrote :

I am currently running Gutsy, but tested with the hardy kernel, using this link: http://ubuntuforums.org/showthread.php?t=646755

uname -a: Linux rune-laptop 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux

Resume from suspend now works, but after resuming the touchpad and wireless is not working.
The wireless interface name has changed from eth1 tom wlan0_rename after switching kernels, but the above link lists this as a registered bug.

Wireless works before I suspend, lsmod shows:
rune@rune-laptop:~$ lsmod | grep 3945
iwl3945 167400 0
mac80211 163352 1 iwl3945

After resuming the same modules are listed, and dmesg shows that the card is detected, but NetworkManager fails to identify it. Maybe this can be solved easily ?

Attatched: dmesg - which shows an error message after resuming regarding the touchpad.

My Laptop is a Lenovo 3000 N100 type 0768-BJG.

Rune

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

After today's update of linux-restricted-modules in Hardy the wireless functionality is available again. Even more pleasant is the fact that the system resumes from STR just fine, WLAN functionality is available after wake-up, and so is sound.

Right at this moment with latest Hardy updates it looks like the only STR problem my laptop experiences is the lack of touchpad after resume. Personally I am considering an upgrade of my production system as soon as the touchpad issue is resolved.

And as long as the touchpad issue is not covered by this particular bugreport, I suppose it's a good idea to change this bug's status. As of now, the bug doesn't exist in Hardy, but still exists and is hardly going to be solved in Feisty and Gutsy.

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

And yes, the touchpad issue is easily solved by adding i8042.reset as a kernel booting option. I reckon the advice to upgrade to 8.04, even though it is still alpha, should be seriously considered by all the "happy" 3000 N100 owners.

Revision history for this message
Rune Evjen (rune-evjen) wrote :

Evgeny,

thank you for your tip regarding the touchpad.

Regarding my last post, my wireless network card is still detected and modules are loaded for it after resume, but KNetworkManager does not see the network interface. I have only upgraded the kernel, haven't upgraded to hardy as it seems mythtv-frontend is not available.

Is your network card fine in (K)NetworkManager after resume ?

If so, have you upgraded just your kernel or the complete system ?

Rune

Revision history for this message
Rune Evjen (rune-evjen) wrote :

Resume works after upgrading to hardy.

Touchpad works after resume as well after adding i8042.reset as a kernel booting option.

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

I have performed a complete Hardy upgrade. The NetworkManager can see and operate the wireless card, though the wireless LED is always off.

Revision history for this message
Robert Schumann (robert-cantab) wrote :

I installed the Hardy kernel () while still running Gutsy as suggested by Rune Evjen on 2008-01-10. This did NOT solve the problem - my laptop (Lenovo 3000 N100 0768-6XG) still does not resume from suspend. The hard drive light comes on, the fan activates, but the screen stays dark and capslock does not work.

The fact that it works for others and not for me could potentially be related to my /etc/default/acpi-support or my kernel boot options.

I realise that Hardy + Gutsy is not a supported configuration, but I thought it was worth pointing out anyway.

Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

I suggest a complete upgrade to Hardy. I never tried upgrading the kernel in Gutsy, but Hardy works just fine.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Evgeny,

Sorry for the delayed response. Thanks for testing and the updates. I'm glad to hear things are working much better with the Hardy Alpha release. I'm going to close this specific report and mark it Fix Released against the Hardy kernel. Regarding the other issues you are noticing regarding loss of touchpad functionality after resume, etc. can you open a new bug report for each issue?

Also just a small side note. You actually might want to consider switching to using the iwlwifi drivers (iwl3945) included in the mainline kernel rather than the ipw3945 driver from linux-restricted-modules. The reason I say this is that development focus has switched from ipw3945 to iwlwifi. For more information see: http://ipw3945.sourceforge.net/

Thanks again! Please continue to report any future bugs that you may find.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

closing tasks against linux-source-2.6.20 and linux-source-2.6.22

Changed in linux-source-2.6.20:
status: Confirmed → Won't Fix
Changed in linux-source-2.6.22:
status: New → Won't Fix
Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

Thank you, Leann. There may be a point in switching to iwlwifi, but as long as ipw3945 is preferred by default Ubuntu installation, and as long as restricted-manager defaults to suggest installing it, I suppose the bugs are worth reporting. This is not just my own profit I'm eager to report and solve bugs, but for other fellow owners of that same hardware, and some of those people may not be experienced enough, so I believe we need those things that are supposed to "just work" actually working. So you may be sure I will continually add more work to Bug Squad :)

Those other issues I've mentioned are of course already reported as separate bugs, and all critical ones are indeed already solved.

Thank you for supervising this bug. We all appreciate the enormous job you all are doing to sort the bugs out. Thank you!

Revision history for this message
Robert Schumann (robert-cantab) wrote :

Bug status on Linux (current release = 2.6.24) changed from Fix Released to Confirmed.

I'm afraid upgrading to Hardy doesn't fix it for me. I have exactly the same problem: it suspends-to-RAM just fine, and the "Sleep" LED lights up on the laptop, but it will not restart. When I press the power button, fans start, hard disk spins, LEDs light up... but the screen stays dark and the keyboard remains inactive.

I'm on

[robert@mujuno: ~] uname -a
Linux mujuno 2.6.24-4-generic #1 SMP Mon Jan 14 17:30:39 UTC 2008 i686 GNU/Linux

Debugging attachments to follow.

Changed in linux:
status: Fix Released → Confirmed
Revision history for this message
Robert Schumann (robert-cantab) wrote :
Revision history for this message
Robert Schumann (robert-cantab) wrote :
Revision history for this message
Robert Schumann (robert-cantab) wrote :
Revision history for this message
Robert Schumann (robert-cantab) wrote :
Revision history for this message
Evgeny Kuznetsov (nekr0z) wrote :

Works for me, though...
$ uname -a
Linux evgkuz 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux

Revision history for this message
Rune Evjen (rune-evjen) wrote : Re: [Bug 86852] Re: Laptop does not wake up from S3 suspend mode

It works on my Lenovo 3000 N100 type 0768-BJG , with all kernels (e.g
2.6.24-X-generic) after upgrading to Hardy.

It also worked using Gutsy with the 2.6.24-X-generic series kernels, except
for the wireless network card which didn't work after resuming from suspend.

Robert Schumann, is your Lenovo the same type/model ?

Rune

On 25/01/2008, Evgeny nekr0z Kuznetsov <email address hidden> wrote:
>
> Works for me, though...
> $ uname -a
> Linux evgkuz 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64
> GNU/Linux
>
> --
> Laptop does not wake up from S3 suspend mode
> https://bugs.launchpad.net/bugs/86852
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
hilsen Rune Evjen
mailto:<email address hidden>

Revision history for this message
Robert Schumann (robert-cantab) wrote :

My laptop (that is not resuming from sleep) is a Lenovo 3000 N100 0768-6XG. And I have a vanilla install of acpi-support (no config tweaks that might have upset S3 suspend.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Robert,

Can you actually open a new bug report. It's helpful to the kernel team if bug reports target one specific issue on a specific set of hardware. It seems you have a different system than the original bug reporter. Although you may be experiencing the same symptom of this particular bug, failure to Suspend, the issue is specific to the hardware used. So while many may have the same symptom they really should be different bugs. The new bug report should contain the information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Additionally, it would be great if you made the titles of a new bug report contain information about your system. I apologize for any inconvenience this might cause but appreciate your cooperation. I'm flipping the status of this specific bug report back to 'Fix Released' as the original bug reporter has confirmed this is no longer an issue on their hardware. Thanks!

Changed in linux:
status: Confirmed → Fix Released
Revision history for this message
Robert Schumann (robert-cantab) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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

Other bug subscribers

Remote bug watches

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