[Lenovo Thinkpad Twist] Won't stay suspended after first suspend

[Aaron Wolf]

I am running 14.04 Trusty Tahr with KDE, so this is *not* a mir or Unity issue. After boot, the system will suspend once, then after that it will wake up on its own immediately after suspend.

WORKAROUND: Running the following will fix the issue until the following reboot:
echo EHC1 | sudo tee /proc/acpi/wakeup

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
CurrentDmesg:
 [ 10.300317] psmouse serio2: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
 [ 12.247478] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
 [ 12.563146] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input14
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=438d66a9-3409-4433-b18a-92b6d483243b
InstallationDate: Installed on 2014-05-03 (4 days ago)
InstallationMedia: KXStudio 14.04 (Live 64bit)
MachineType: LENOVO 33474HU
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-lowlatency root=UUID=82174999-4881-4475-8d12-25652dc0db33 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-24.47-lowlatency 3.13.9
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-lowlatency N/A
 linux-backports-modules-3.13.0-24-lowlatency N/A
 linux-firmware 1.127
Tags: trusty
Uname: Linux 3.13.0-24-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 08/30/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: GDET33WW (1.03 )
dmi.board.asset.tag: Not Available
dmi.board.name: 33474HU
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGDET33WW(1.03):bd08/30/2012:svnLENOVO:pn33474HU:pvrThinkPadTwist:rvnLENOVO:rn33474HU:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 33474HU
dmi.product.version: ThinkPad Twist
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 1316221

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.

[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.15 kernel[0].

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc4-utopic/

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

apport information

[Aaron Wolf (wolftune)]

Thanks, that all makes sense, except I have no optical drive, so I can't use CD/DVD to update the BIOS, and none of the links or anything that I searched for make it clear how to use the BIOS ISO via USB. I don't have any Windows install; I have only Ubuntu. I am happy to update the BIOS if I can figure out how to do it. I could even buy a USB DVD drive but that is not efficient and won't be something I can do quickly. Thanks for the help!

[Aaron Wolf (wolftune)]

Thanks, that all makes sense, except I have no optical drive, so I can't use CD/DVD to update the BIOS, and I tried everything I could with lots of help to get a USB flash drive version working, and that never booted.

I got some confirmation of other people having this issue. It seems there's an issue with the BIOS update and USB flash drives. So until I can get ahold of a USB DVD drive, I can't update. It does appear likely that the BIOS update will indeed fix the issue though.

[Aaron Wolf (wolftune)]

I got the BIOS update complete. The issue seems to be solved, although now I have a couple separate issues. Thanks for the help, I marked the ticket "invalid."

[Aaron Wolf (wolftune)]

I was wrong about the fix, it recurred…

[Aaron Wolf (wolftune)]

I thought it was fixed as I didn't have the issue for a while, but it recurred again just now with the same workaround of that echo command mentioned originally solving it for now.

Output of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date:

GDETA6WW (1.66 )
04/09/2014

[penalvch (penalvch)]

Aaron Wolf, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc5-utopic/ and advise to the results?

If reproducible, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Mr_DNA (mr-dnase)]

I can confirm this problem has existed since at least bios version 1.58, and on Ubuntu 13.04, 13.10, and 14.04. Occassionally the computer will go into proper suspension (and remain there until manually awoken), but most often it will suspend and immediately wake back up.

I am running a Lenovo Thinkpad Twist S230u with bios 1.66, 3.13.0-24-generic kernel, and 64-bit Ubuntu 14.04. I have attached my info following the command line suspend as described on the DebuggingKernelSuspend page.

Note: the command line suspend seemed to result in a successful suspension of the computer. I will attach another dmesg following my next unsuccessful suspension attempt.

[Mr_DNA (mr-dnase)]

Immediately after posting the above messages, I attempted to put the computer into suspend using the GUI dropdown menu button. The computer suspended and immediately woke back up.

I have attached the dmesg following this second attempt, though I do not know if it is of any use.

[Aaron Wolf (wolftune)]

I tried with the latest kernel 3.15 rc5 and I still got the error.

Attached is the dmesg file

[penalvch (penalvch)]

Mr_DNA, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[penalvch (penalvch)]

Aaron Wolf, did this problem not occur in a release prior to Trusty?

[Aaron Wolf (wolftune)]

Hi Chris,

Yes, I had the same problem prior to Trusty. Someone else had posted a report on it as well prior to Trusty, although that report got marked as specific to Unity and you marked it "won't fix" when the original poster indicated perhaps it was fixed for them. I have been using other DE's, so this definitely isn't a Unity issue. Anyway, the link to that original ticket where I had first posted is in my original description for the present ticket.

[penalvch (penalvch)]

Aaron Wolf:
<"Yes, I had the same problem prior to Trusty."

In what earliest release specifically?

[Aaron Wolf (wolftune)]

Before 14.04, I was running 12.04 LTS and had been using it since I got this machine, starting with 12.04.2 I think, not sure, and the last kernel I had installed before updating to 14.04 was Linux 3.11

[penalvch (penalvch)]

Aaron Wolf, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc6-utopic/ , and if reproducible provide both 3. and 4. from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Aaron Wolf (wolftune)]

I hope I'm doing this correctly. For reference, it took me (both this time and last) several tries to reproduce. The first few suspends worked. I restarted again. After a few suspends, it started doing this instant-wake behavior again (which it then will do consistently unless I run that workaround command mentioned in the initial post).

Attached are the files requested (I think). This was with 3.15-rc6 low-latency (I generally use low-latency kernels).

[Aaron Wolf (wolftune)]

and the other file…

[penalvch (penalvch)]

Aaron Wolf, 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 ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.

[Aaron Wolf (wolftune)]

I have the impression this will not be a simple short task. I've never done anything like it before, so it'll take me some time and energy to make sense of it. I'll work on it sometime soon though. Thanks

[Alejandro Virrueta (alejandro-virrueta)]

I am also having similar issues keeping my laptop suspended. When I try to suspend my laptop, 90% of the time it re-wakes within 2 seconds, displays some text on the screen, and sends me back to the log-in screen. The work-around posted here does not work for me. Please help?

[penalvch (penalvch)]

Alejandro Virrueta, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Aaron Wolf (wolftune)]

Hi, I started looking at this, but at https://wiki.ubuntu.com/Bugs/Upstream/kernel it says "booted into the newest available upstream mainline kernel only" — I am still on 14.04 trusty. Do I install the newest thing marked for trusty or go ahead and install a kernel for utopic? Also, I do audio work, can I stick with low-latency kernel? That seems unrelated to the issue here…

[penalvch (penalvch)]

Aaron Wolf, the latest mainline kernel is now 3.18-rc3. If it's reproducible in it, then feel free to report this as previously advised.

[Aaron Wolf (wolftune)]

I don't know if I should mark this as fixed upstream or fixed or whatever. I am having a very hard time reproducing it lately.

Basically, I rarely restart anyway, but I know that within the last couple months, I have experienced this on the 3.13 kernel. However, I installed the 3.18 latest mainline and tried and failed to reproduce. I don't have a guaranteed way to know that it's fixed though, and I can't stay with 3.18 for long time to keep testing since the wifi doesn't work with 3.18.

So, I guess I have to live with saying that *maybe* this is fixed upstream.

[penalvch (penalvch)]

Aaron Wolf, if you tested it on 3.18 (which version number specifically?) and it's not reproducible, then this is considered fixed. As well, this wouldn't be an issue to report upstream, but a downstream (Ubuntu) one.

Hence, the next step is to fully reverse commit bisect from kernel 3.15-rc6 to the 3.18 kernel you tested fixed in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release.

Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Aaron Wolf (wolftune)]

Sorry, I can't make this sensible for testing because I have failed to discover a 100% reliable method for reproduction. My memory is that a while back (when I was on 12.04) I could reproduce it consistently. But now, I could go a while thinking "it's fixed" and then sometime it shows up again (or at least that happened ever). So I no longer feel confident in having any method to reliably reproduce. It becomes a matter of using the computer over a long time and seeing if it ever recurs. That's not a functional way to go through bisecting.

So, I'm going to have to leave it at "not a problem for me now really" and hope that either it just is fixed or that someone else reproduces it reliably… If I ever come upon a totally reliable way to reproduce the bug, then I will try the bisecting.

Thanks for your understanding and help.

[Fen Labalme (fen-openprivacy)]

This is a painfully intermittent problem. I thought it had gone away completely but then it returned with Kernel 3.17.2.

[penalvch (penalvch)]

Fen Labalme, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]