Bug 896073 - thinkpad t520: suspend by closing lid works, opening lid un-suspends and then suspends again.
Summary: thinkpad t520: suspend by closing lid works, opening lid un-suspends and then...
Keywords:
Status: CLOSED DUPLICATE of bug 859227
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-16 15:00 UTC by jnelson+fedora
Modified: 2013-01-30 12:51 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-30 12:51:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
/var/log/messages during a double suspend/resume cycle (36.46 KB, text/plain)
2013-01-28 13:20 UTC, Tommi Kyntola
no flags Details
/var/log/messages during a suspend/resume cycle FAILED CASE (24.24 KB, application/octet-stream)
2013-01-29 16:38 UTC, Tommi Kyntola
no flags Details
/var/log/messages during a suspend/resume cycle OK CASE (17.61 KB, application/octet-stream)
2013-01-29 16:40 UTC, Tommi Kyntola
no flags Details
/var/log/messages during a suspend/resume cycle OK CASE when in tty2 (16.22 KB, application/octet-stream)
2013-01-29 16:41 UTC, Tommi Kyntola
no flags Details
/var/log/messages during a suspend/resume cycle OK CASE suspended from kde menu (16.55 KB, application/octet-stream)
2013-01-29 16:42 UTC, Tommi Kyntola
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 809248 0 unspecified CLOSED lid open fails to wake Thinkpad T410 with i915 graphics 2021-02-22 00:41:40 UTC

Description jnelson+fedora 2013-01-16 15:00:14 UTC
Description of problem:

Suspending the laptop by closing the lid works just fine.
Un-suspending by opening the lid (usually, not 100%) un-suspends, and then immediately suspends again.

Symptoms are the same as this older bug from Fedora 16:
https://bugzilla.redhat.com/show_bug.cgi?id=809248

Version-Release number of selected component (if applicable):

Fedora 18
kernel: 3.7.2-201.fc18.x86_64
Thinkpad T520 with BIOS version 8AET60WW (1.40 ) (fairly recent as of this writing)

I was using Fedora 17 previously, and did not experience the double-suspend.

Comment 1 Tommi Kyntola 2013-01-28 13:20:00 UTC
Created attachment 688964 [details]
/var/log/messages during a double suspend/resume cycle

Fedora 18 running vanilla 3.7.5 on Lenovo Thinkpad X1 Carbon. Same thing happens with fedora kernels.

This is /var/log/messages between such a cycle. I closed the lid, it suspended, I opened up the lid, it woke up a bit (saw console again, no X) and then immediately suspended again, I then pressed the power button to wake it up again, it woke up and everything works fine.

Comment 2 Tommi Kyntola 2013-01-29 16:38:33 UTC
Created attachment 689939 [details]
/var/log/messages during a suspend/resume cycle FAILED CASE

When in X I closed the lid and reopened only to witness the system suspend again. Lid closed and reopened and then it gets back up.

Comment 3 Tommi Kyntola 2013-01-29 16:40:05 UTC
Created attachment 689940 [details]
/var/log/messages during a suspend/resume cycle OK CASE

And about one in five or so it works as expected.

Comment 4 Tommi Kyntola 2013-01-29 16:41:28 UTC
Created attachment 689941 [details]
/var/log/messages during a suspend/resume cycle OK CASE when in tty2

And when in some other tty it works every time.

Comment 5 Tommi Kyntola 2013-01-29 16:42:50 UTC
Created attachment 689942 [details]
/var/log/messages during a suspend/resume cycle OK CASE suspended from kde menu

And if I do the same thing from the KDE menu it also works every time.

Comment 6 Tommi Kyntola 2013-01-29 18:55:46 UTC
Bug 859227 deals with this. Upgrading kde-workspace to a newer version (currently in testing) seems to fix this (with some minor side effects).

Comment 7 Lukáš Tinkl 2013-01-30 12:51:18 UTC

*** This bug has been marked as a duplicate of bug 859227 ***


Note You need to log in before you can comment on or make changes to this bug.