Suspend fails on Ideapad S205

[Hansen]

Laptop testing Raring Ringrale (64AMD)on Lenovo Ideapad S205 AMD E-450, suspend fails.
---
ApportVersion: 2.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mads 1930 F.... pulseaudio
 /dev/snd/controlC0: mads 1930 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=3f8eb1eb-e922-4eec-aa30-39ccd17fe056
InstallationDate: Installed on 2012-12-12 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121211)
MachineType: LENOVO 1038D4G
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-5-generic root=UUID=a8c6a21c-1475-4502-b80f-2e9ab743a976 ro quiet splash
ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/mads not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.7.0-5-generic N/A
 linux-backports-modules-3.7.0-5-generic N/A
 linux-firmware 1.98
StagingDrivers: rts5139
Tags: raring staging
Uname: Linux 3.7.0-5-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/10/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 4BCN24WW
dmi.board.asset.tag: Base Board Asset Tag Unknown
dmi.board.name: Inagua
dmi.board.vendor: LENOVO
dmi.board.version: 109-B78210-00A
dmi.chassis.asset.tag: Chassis Asset Tag Unknown
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Chassis Version Unknown
dmi.modalias: dmi:bvnLENOVO:bvr4BCN24WW:bd08/10/2011:svnLENOVO:pn1038D4G:pvrIdeapadS205:rvnLENOVO:rnInagua:rvr109-B78210-00A:cvnLENOVO:ct10:cvrChassisVersionUnknown:
dmi.product.name: 1038D4G
dmi.product.version: Ideapad S205
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1089339

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Hansen (moteprime)]

apport information

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu laptop testing tracker.

A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/1089339

[Hansen (moteprime)]

Tested with kernel "Linux Raring-Ideapad-S205 3.7.0-030700rc8-generic #201212031649"

[Hansen (moteprime)]

Bug are the same:
On 12.04: #985528, #1015642
On 12.10 #1022974

I believe it needs to be reported as a Kernel bug to. But i am not skilled enough to do so, please advice.

[penalvch (penalvch)]

Hansen, could you please test the latest upstream kernel available (v3.7-raring) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory 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.7

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.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Hansen (moteprime)]

Hi.
Did i use the wrong kernel?

[Joseph Salisbury (jsalisbury)]

@Hansen,

The Raring kernel has since been rebased to upstream v3.7. Can you either please test the latest Raring kernel or the upstream v3.7, which was mentioned in comment #19?

[René Fleschenberg (rene.f)]

I don't have access to the hardware at the moment, so it would be nice if Hansen could test this.

[René Fleschenberg (rene.f)]

Is this a duplicate of #1015642? #1015642 has been reported to upstream: http://bugzilla.kernel.org/show_bug.cgi?id=43881

[Hansen (moteprime)]

I'm sorry i do not understand 100% what you meen. I tested with the newest kernel available. "v3.7-rc8-raring".
Which one should i try?
Thanks you.

[penalvch (penalvch)]

Hansen, the newest kernel available is v3.7-raring, which is newer than v3.7-rc8-raring.

[Hansen (moteprime)]

OK! -Thank you.
I have now tested with 3.7-raring.
"3.7.0-030700-generic #201212102335 SMP Tue Dec 11 04:36:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux"
Wake up from suspend are still not possible without removing battery.

[penalvch (penalvch)]

Hansen, thank you for testing the newest mainline kernel. Did this problem not occur in a release prior to Raring?

[Hansen (moteprime)]

Thanks.
This bug has been there since 11.04. I have tried reporting bugs (see above), ubuntu forums, ask ubuntu and lots of other places/things.
It all ends up in no replies, it it very frustrating.

Is it a kernel problem??

[penalvch (penalvch)]

Hansen, thank you for your response. Did this issue occur in Lucid?

[Hansen (moteprime)]

I bought this laptop two years ago, and suspend did not work. Somewhere along the way it did work for 1-2 months, but stopped again after some kernel update. I have with help from others tried to find out which setup workes to but with no luck. We tried the last four versions of Ubuntu with lots of kernels.
I don't no what to do. No distros have working suspend on this laptop.
Please advice.

[penalvch (penalvch)]

Hansen, could you please test for this problem in a live environment of Lucid via http://releases.ubuntu.com/lucid/ ?

[ppq (ppq)]

Hi,
I'm having exactly the same issue with my Ideapad S205 and Ubuntu 12.04, 12.10 and 13.04. (Back then it worked for some time in 11.04 and 11.10, though. Now it does not work anymore with this releases.)

I just tested http://releases.ubuntu.com/lucid/ubuntu-10.04.4-desktop-amd64.iso which I copied to a USB key using usb-creator-gtk within precise.
First, it gave me an error message regarding "gfxboot" and a boot: prompt. After pressing return a few times, it did boot, anyway.

Waking up from Suspend didn't work in Lucid Live, either; I had to remove the battery, just like before.

[Hansen (moteprime)]

Hi Benedikt Haus! -thank you very much for participating! :-)
I have not had the time to perform the test yet.

@ Christopher M. Penalver: Is it enough that Benedikt Haus did the test, or do you want me to test it as well.
I'm quiet sure the result will be the same.
Thank you.

[penalvch (penalvch)]

Hansen, could you please provide the information requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089339/comments/31 ?

Benedikt Haus, 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.

[Hansen (moteprime)]

Waking up from Suspend didn't work in Lucid Live, either; I had to remove the battery, just like before.

[penalvch (penalvch)]

Hansen, thank you for testing the Lucid live environment. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Stephen (belrik)]

Experiencing same problem; cannot suspend, shutdown or hibernate on an S205.

Not sure what the problem is, beyond this being an EFI system. Routine seems to start and the dots scroll then they freeze and I have to hold the power button. Rather annoying, I'd be happy just to shut it down gracefully.

[Hansen (moteprime)]

Used the command:
sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend"
booted, and "dmesg > dmesg.txt"
But the file does not contain the 'hash matches' lines.
Did i do it right?

[Hansen (moteprime)]

Wasn't concentrating. Used wrong OS installation.
Will test again. -Right this time.

[Hansen (moteprime)]

Ok, did the same thing:

Used the command:
sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend"
booted, and "dmesg > dmesg.txt"

But the file does not contain the 'hash matches' lines.

The "wrong" OS installation was 12.10, and have now tried with 13.04. the behaviuor are the same.

[penalvch (penalvch)]

Hansen, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

Marking Triaged as newest mainline tested, tested for regression to Lucid, and suspend debugging information provided.

[penalvch (penalvch)]

Hansen, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-raring/ ?

[Hansen (moteprime)]

Hi there.
I gave up on this crappy laptop, there's to many things that does not work in Ubuntu with it.
I bought another that works 100%
Should i mark the bug invalid?

[András Korn (kornandras)]

Please don't mark this bug as invalid. The fact that one of the people it affected bought different hardware and is no longer experiencing the problem didn't make the bug go away.

FWIW, suspend worked for me at least once with kernel 3.10.5, booting with the 'noefi' argument. I haven't been able to reproduce it yet, but it definitely suspended and resumed successfully once.

[András Korn (kornandras)]

OK, I can reproduce it: booting 3.10.5 vanilla (but see https://bugzilla.kernel.org/show_bug.cgi?id=43007) with 'noefi', I can suspend and resume my S205.

Of course, 'noefi' makes it impossible to upgrade grub2, and there may be other issues, but it's certainly a workaround for the suspend problem.

[penalvch (penalvch)]

András Korn, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the official Ubuntu documentation:
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Community: https://wiki.ubuntu.com/ReportingBugs

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

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

Thank you for your understanding.