[Lenovo B570e Notebook] Resume from suspend to blank screen

[Mustafa Muhammad]

When I resume from suspend on my Kubuntu, it only show a black screen, nothing works, not even ctrl+alt+F2.

WORKAROUND: Change the system time from RTC to UTC.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mustafa 1633 F.... pulseaudio
Date: Fri Oct 12 20:22:41 2012
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926.3)
MachineType: LENOVO HuronRiver Platform
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=22466810-dec6-45b9-a6aa-8868218c04e9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.94
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 44CN42WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnLENOVO:bvr44CN42WW:bd09/22/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570e:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: Lenovo B570e
dmi.sys.vendor: LENOVO

[penalvch (penalvch)]

Mustafaa al-Hamdaani, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

As well, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

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 text:
needs-upstream-testing

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.

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

[Mustafa Muhammad (mustafa.muhammad)]

Hi,
I did the procedure in https://wiki.ubuntu.com/DebuggingKernelSuspend and I got dmesg file, the lines are:

[ 0.664690] Magic number: 0:460:740
[ 0.664694] hash matches /build/buildd/linux-3.5.0/drivers/base/power/main.c:658

and I don't know what to do with them, now I will test upstream kernel.

[Mustafa Muhammad (mustafa.muhammad)]

Using upstream kernel linux-image-3.6.2-030602-generic the problem still exist.

[Mustafa Muhammad (mustafa.muhammad)]

Hi, this is dmesg, however, without changing anything (not even update), it resumes normally now!! (using the shipped kernel), but still not working using upstream kernel, I don't know why.

[Mustafa Muhammad (mustafa.muhammad)]

I didn't know that, thanks for the information.
No, I don't remember it happening in 12.04, but I am distro-hopping and 3.6.2 works well in Fedora, so may be not totally upstream issue.

[Mustafa Muhammad (mustafa.muhammad)]

I noticed that I had a very low space on my root partition, could that be the cause?

[penalvch (penalvch)]

Mustafa Muhammad, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066060/comments/9 :
>"I noticed that I had a very low space on my root partition, could that be the cause?"

Before further troubleshooting, it is best to free up some disk space to rule this out as a problem.

The next step would be to run a 30-50 suspends in a row to find out if you still have an intermittent suspend problem. Could you please do this following https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting ?

[Mustafa Muhammad (mustafa.muhammad)]

The test fails to resume automatically, should I continue doing it manually?

mustafa@mustafa-Lenovo-B570e:~$ sudo bash test-suspend --full
[sudo] password for mustafa:
This script will attempt to suspend and resume your computer a number of times.
Should the machine fail to resume, first attempt to manually resume it. If
that fails power your system off and on which will generate an apport bug
report automatically.

Press CTRL-C now to abort testing ...

*** TEST 1 -- suspend triggered via dbus message
*** machine will suspend for 20 seconds
*** press return when ready

SUSPEND FAILED, did not go to sleep
*** no BATTERY detected ac tests skipped ...
*** no BATTERY detected power test skipped ...

*** TEST 2 -- 30 iteration variable delay suspend/resume stress test
*** machine will suspend for 20 seconds
*** NOTE: there will be no further user interaction from this point
*** press return when ready

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds

[Mustafa Muhammad (mustafa.muhammad)]

mustafa@mustafa-Lenovo-B570e:~$ sudo bash test-suspend --full
[sudo] password for mustafa:
This script will attempt to suspend and resume your computer a number of times.
Should the machine fail to resume, first attempt to manually resume it. If
that fails power your system off and on which will generate an apport bug
report automatically.

Press CTRL-C now to abort testing ...

*** TEST 1 -- suspend triggered via dbus message
*** machine will suspend for 20 seconds
*** press return when ready

SUSPEND FAILED, did not go to sleep
*** no BATTERY detected ac tests skipped ...
*** no BATTERY detected power test skipped ...

*** TEST 2 -- 30 iteration variable delay suspend/resume stress test
*** machine will suspend for 20 seconds
*** NOTE: there will be no further user interaction from this point
*** press return when ready

delay 60 ...
SUSPEND FAILED, did not go to sleep
wait for 60 seconds
delay 58 ...
SUSPEND FAILED, did not go to sleep
wait for 58 seconds
delay 56 ...
SUSPEND FAILED, did not go to sleep
wait for 56 seconds
delay 54 ...
SUSPEND FAILED, did not go to sleep
wait for 54 seconds
delay 52 ...
SUSPEND FAILED, did not go to sleep
wait for 52 seconds
delay 50 ...
SUSPEND FAILED, did not go to sleep
wait for 50 seconds
delay 48 ...
SUSPEND FAILED, did not go to sleep
wait for 48 seconds
delay 46 ...
SUSPEND FAILED, did not go to sleep
wait for 46 seconds
delay 44 ...
SUSPEND FAILED, did not go to sleep
wait for 44 seconds
delay 42 ...
SUSPEND FAILED, did not go to sleep
wait for 42 seconds
delay 40 ...
SUSPEND FAILED, did not go to sleep
wait for 40 seconds
delay 38 ...
SUSPEND FAILED, did not go to sleep
wait for 38 seconds
delay 36 ...
SUSPEND FAILED, did not go to sleep
wait for 36 seconds
delay 34 ...
SUSPEND FAILED, did not go to sleep
wait for 34 seconds
delay 32 ...
SUSPEND FAILED, did not go to sleep
wait for 32 seconds
delay 30 ...
SUSPEND FAILED, did not go to sleep
wait for 30 seconds
delay 28 ...
SUSPEND FAILED, did not go to sleep
wait for 28 seconds
delay 26 ...
SUSPEND FAILED, did not go to sleep
wait for 26 seconds
delay 24 ...
SUSPEND FAILED, did not go to sleep
wait for 24 seconds
delay 22 ...
SUSPEND FAILED, did not go to sleep
wait for 22 seconds
delay 20 ...
SUSPEND FAILED, did not go to sleep
wait for 20 seconds
delay 18 ...
SUSPEND FAILED, did not go to sleep
wait for 18 seconds
delay 16 ...
SUSPEND FAILED, did not go to sleep
wait for 16 seconds
delay 14 ...
SUSPEND FAILED, did not go to sleep
wait for 14 seconds
delay 12 ...
SUSPEND FAILED, did not go to sleep
wait for 12 seconds
delay 10 ...
SUSPEND FAILED, did not go to sleep
wait for 10 seconds
delay 8 ...
SUSPEND FAILED, did not go to sleep
wait for 8 seconds
delay 6 ...
SUSPEND FAILED, did not go to sleep
wait for 6 seconds
delay 4 ...
SUSPEND FAILED, did not go to sleep
wait for 4 seconds
delay 2 ...
SUSPEND FAILED, did not go to sleep
wait for 2 seconds

*** Please report your results on the Ubuntu WIKI:
    https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting

mustafa@mustafa-Lenovo-B570e:~$

[penalvch (penalvch)]

Mustafa Muhammad, let us hold off on the auto suspend test for now. Regarding your dmesg attachment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066060/comments/6 , was this for a failed suspend or a successful one?

If it was the successful one, we would need you to attach a dmesg for a failed suspend.

[Mustafa Muhammad (mustafa.muhammad)]

It was after a failed resume, I powered off then booted and copied dmesg, as for the automatic reset, I changed my system's RTC to UTC, and now it sleeps and resumes normally, but still says:
"SUSPEND FAILED, did not go to sleep"
strange.

[Mustafa Muhammad (mustafa.muhammad)]

Did you analyze the dmesg or from the auto suspend test? Does the test complete successfully with you?

[penalvch (penalvch)]

Mustafa Muhammad, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066060/comments/15 :
>"Did you analyze the dmesg or from the auto suspend test?"

I did notice in the auto test article how it suggested changing the system time from RTC to UTC. As well, the fact that you changed this and suspend starts working has put me in unfamiliar triage territory. Hence, I set it back to Confirmed for someone else to take a look at this.

"Does the test complete successfully with you?"

Suspend works for my hardware.

[Mustafa Muhammad (mustafa.muhammad)]

I meant does it also says:

"SUSPEND FAILED, did not go to sleep"

like mine or not (suspends then resumes then says suspend failed!!!!!)?

[Mario Veygel (mario-streiber)]

I appear to have the same issue here with a freshly installed 12.10 on a brand-new HP g6-2245sg. When resuming after suspend, the display stays dark, while the rest of the box seems to do the resume properly. The fan starts, the status LEDs go on etc, I can even log on per ssh. So everything seems to work except of the display.

> WORKAROUND: Change the system time from RTC to UTC.

This doesn't work for me, or I didn't understand what I should have done here. I changed the system clock in the BIOS so that it should reflect UTC. I'm in CET so UTC is my time - 1 hour. Is there anything else I should have done?

[Mario Veygel (mario-streiber)]

Tried upstream kernels 3.6.3 and 3.7.0rc2 but same thing. On top of this, with 3.7.0rc2 the display was very slow before the suspend. I went back now to the stock kernel 3.5.0-17.28

[penalvch (penalvch)]

Mario Veygel, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Mario Veygel (mario-streiber)]

many thanks for this pointer, didn't know about ubuntu-bug.

[James (james-ellis-gmail)]

Hi

I'm searching for a similar issue that's happening on my Kubuntu 12.10 system - resume from suspend fails. In my case there is a single line on the screen on failure - "drm nouveau .... " (sorry, it's only there for a short time) - looks like a line from a log.

This behaviour changed between KDE 4.9 releases and 4.10 - in 4.9 the system would fail to resume and there would be no way to get back to desktop without a restart (Ctrl + ALt + Del at that point triggers a restart - found that out through chance) or hard power off.
In 4.10 the login manager reappears but the KDE session from last time is no longer available post login.

I tried the instructions here:
https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting

... but the system fails to resume as above and there are no test results.

dmesg for a failed resume attached.

$ uname -a
Linux box 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:05:29 UTC 2013 i686 i686 i686 GNU/Linux

I'll try SSHing into the laptop to see what's running but aside from installing another kernel, not really sure how to debug this further so any pointers appreciated.

Thanks!

[penalvch (penalvch)]

James, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[James (james-ellis-gmail)]

Here you go Christopher:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1153809

 I've always understood that the creation of duplicate bug reports is naughty and the original report seems to describe the same issue.

[penalvch (penalvch)]

Mustafa Muhammad, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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.11-rc4

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Mustafa Muhammad (mustafa.muhammad)]

I tested the latest Ubuntu and Kubuntu daily images, and they are working fine, this bug no longer exists in them, should I test other kernels too?

[penalvch (penalvch)]

Mustafa Muhammad, no need to test the mainline kernel at this point. Would you need a backport to a release prior to Saucy, or may we close this as Status Invalid?

[Mustafa Muhammad (mustafa.muhammad)]

I don't need any previous release, so I will close it as invalid, thank you.