[Lenovo IdeaPad S10-S] Unable resume system from suspend

[Victor Dorokhov]

My system is unable to resume from suspend.
I'm using and learning Ubuntu since Maverick, and since that time when I'm initiating suspend system can't wake up normally. Just disk activity indicator is flashing for short time, screen remains black.
I read the topic here about similar situation, but there the problem was in encryption of /home. I don't use encryption.
So after latest update and small investigation with no effect, i used Phil's V. advice and wrote this report.
Hope you'll help me.

I tested Linux kernels 3.3.1 and 3.4.0rc1 - suspend function doesn't work properly.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-20-generic 3.2.0-20.33
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu1
Architecture: i386
Date: Fri Mar 30 21:40:13 2012
HibernationDevice: RESUME=UUID=f4189eeb-ce7c-4480-a140-3fbda549957c
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: LENOVO S10-3
ProcEnviron:
 LANGUAGE=ru:en
 TERM=xterm
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=36153c45-1e0e-4f46-98b8-679e8ba4da48 ro quiet splash vt.handoff=7
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-03-13 (17 days ago)
dmi.bios.date: 08/12/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 2ACN34WW
dmi.board.name: Mariana3A
dmi.board.vendor: Lenovo
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr2ACN34WW:bd08/12/2010:svnLENOVO:pnS10-3:pvrLenovo:rvnLenovo:rnMariana3A:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: S10-3
dmi.product.version: Lenovo
dmi.sys.vendor: LENOVO

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/

[Joseph Salisbury (jsalisbury)]

Also, have you had this problem since Maverick?

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Victor Dorokhov (vitekd88)]

Joseph,
i've just done it. I looked through the list of kernels and chose 3.3.1 as it was not marked as daily build or rc and it has most recent date.
I installed kernels image and two headers package. Rebooted. And found my problems remained.

Yes, i had this problem with all distributions since Maverick.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Victor Dorokhov (vitekd88)]

Joseph,
Юрий Чудновский pointed to me that there is other other reports with similar (or exactly the same) problem:
https://bugs.launchpad.net/linux/+bug/640100
https://bugzilla.kernel.org/show_bug.cgi?id=21952
May be it is better to connect existing reports then to open new one, it is seems that i am and all these people has same problem.

[Victor Dorokhov (vitekd88)]

Actually a have two problems with Ubuntu on my netbook. Another one is with wi-fi. I opened two bug reports and have been told to provide kernel bisection to find out what patch causes problem with wireless devise.
If i'll be able to make it i can also provide bisection to investigate issue with suspend if it's needed. Does bisection process needed to solve bug with suspend?

[Miguel (nombrecreativo)]

In my Lenovo S10-3 with Ubuntu 12.04 and kernel 3.2.0-23-generic 64-bit the issue was "solved" with the (now) classic "intel_idle.max_cstate=" workaround, in this case with the value "3". In Ubuntu 11.10 it worked only with "0". I have no idea about the possible consequences of this (right now, after the first successful resume, I'm watching carefully the battery indicator...). Volume and brightness keyboard controls, and wireless, work fine. The only problem is... I lost my touchpad :(

[Benji (benjim)]

I got the same issue with a Lenovo S10: After suspend the display remains black and I can't get it waked up. Also SSH connections fails.
I tried kernel 3.4 RC4, which doesn't help. Also the proposted workarround with intel_idle.max_cstate=0 isn't working on my 32-bit machine.

[Dave Cheney (dave-cheney)]

I am glad to confirm that

% grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=3 nohpet"

allows my S10-3 to wake from sleep under 12.04.LTS/amd64

[Victor Dorokhov (vitekd88)]

I'm very sorry for my slowpokeness.
intel_idle.max_cstate=3 is really the salvation for the problem as i checked on my netbook.
So this bug report may be closed i think. Thanks!

[madbiologist (me-again)]

This should be fixed in the just-released upstream 3.5 kernel. From the changelog:

author Deepthi Dharwar
Mon, 25 Jun 2012 21:59:54 +0000 (23:59 +0200)
committer Rafael J. Wysocki
Wed, 27 Jun 2012 18:18:53 +0000 (20:18 +0200)
commit 75cc52358799bd6001e7d1a47847f997f5ae99f0
tree 3e8a4c0d94b4a4c7881f77404841d65de4370276
parent 1f758b23177d588a71b96ad02990e715949bb82f

PM / ACPI: Fix suspend/resume regression caused by cpuidle cleanup.

Commit e978aa7d7d57d04eb5f88a7507c4fb98577def77 ( cpuidle: Move
dev->last_residency update to driver enter routine; remove dev->last_state)
was breaking suspend on laptops, as reported in the below link
- https://lkml.org/lkml/2011/11/11/164

This was fixed in commit 3439a8da16bcad6b0982ece938c9f8299bb53584
(ACPI / cpuidle: Remove acpi_idle_suspend (to fix suspend regression)
by removing acpi_idle_suspend flag.
- https://lkml.org/lkml/2011/11/14/74

But this did fix did not work on all systems
as Suspend/resume regression was reported on Lenovo S10-3
recently by Dave.
- https://lkml.org/lkml/2012/5/27/115
It looked like with commit e978aa7d broke suspend and
with commit 3439a8da resume was not working with acpi_idle driver.

This patch fixes the regression that caused this issue
in the first place. acpi_idle_suspend flag is essential on
some x86 systems to prevent the cpus from going to deeper C-states
when suspend is triggered ( commit b04e7bdb984 )
So reverting the commit 3439a8da is essential.

By default, irqs are disabled in cpu_idle arch specific call
and re-enabled in idle state return path . During suspend,
the acpi_idle_suspend flag is set, which
prevents the cpus from going to deeper idle states,
it is essential to enabling the irqs in this return path too.

To address the suspend issue,
we were not re-enabling the interrupts while returning from
acpi_idle_enter_bm() routine if acpi_idle_suspend flag is set.
and this caused suspend failure.

In addition to the above, to improve the readability of the code,
return of -ENIVAL is replaced with -EBUSY in acpi_idle_suspend
return path. Implying that the system is currently busy when suspend
is in progress, which prevents the cpus from entering deeper C-states.

Reported-and-Tested-by: Dav Hansen
Tested-by: Preeti Murthy
Signed-off-by: Deepthi Dharwar
Reviewed-by: Srivatsa S Bhat
Signed-off-by: Rafael J. Wysocki

[Kevin (wittyman37)]

I can confirm Dave Cheney's post helped me to fix my problem with Lenovo S10-3 running Edubuntu 12.04.2 on kernel 3.2.0-38-generic-pae 32-bit! I have been seaching for a solution to this for months and months!!

[code]
sudo gedit /etc/default/grub
# edit and save this line ---> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=3 nohpet"
sudo update-grub
[/code]

[madbiologist (me-again)]

@Victor - if you remove the workaround you described in comment #12, do you still have this issue on Ubuntu 12.10 "Quantal Quetzal" with the latest updates? If you do, can you please test Ubuntu 13.04 "Raring Ringtail"? If the issue is gone can you please change the status of this bug from Fix Committed to Fix Released?

[penalvch (penalvch)]

Victor Dorokhov, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Victor Dorokhov (vitekd88)]

Thank you for your work! I completely forget about this bug and just didn't use suspend on my Ubuntu 12.04.

Today i found time to test 14.04 alpha:

Xubuntu 14.04 daily build (07.01.14)
Kernel 3.12.0-7-generic

Suspend mode activation and resume works properly and very fast.