Bug 599138 - Suspend failure (thinkpad docking stations)
Summary: Suspend failure (thinkpad docking stations)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-02 18:14 UTC by Akshay Dua
Modified: 2012-02-29 14:30 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-27 17:54:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Akshay Dua 2010-06-02 18:14:55 UTC
Description of problem:

I have a dual monitor setup via a ThinkPad docking station for my X61 laptop. After pressing the "prepare to release" button on the docking station, and then hitting suspend causes the crescent shaped suspend light to continue blinking. I have waited for about two minutes but the laptop does not suspend and the light keeps on blinking. Suspending under normal conditions is really fast and quick in FC13. This use-case used to work in Fedora 12, but does not anymore.

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

How reproducible:

Every time.

Steps to Reproduce:
1. Press button to prepare laptop for release from docking station
2. Hit Fn-suspend
  
Actual results:

Suspend light keeps blinking but laptop does not suspend.

Expected results:

Light stops blinking and laptop suspends.

Additional info:

This may or may not be useful: there is an error (existed in FC12 as well) where if I release my X61 laptop from the docking station, the notification area displays an error similar to "Cannot switch Monitor configuration CRTC 63". In FC12, suspend would not work after I got that error. However, it would work after pressing the prepare to release button and before actually releasing the laptop.

Comment 1 Jiri Skala 2010-06-03 08:46:20 UTC
Hi,
is the issue reproducible only in combination with docking station? Does it work fine outside docking station?

Comment 2 Akshay Dua 2010-06-03 18:09:29 UTC
Hi and thanks so much for responding.

I checked, and it looks like the problem only occurs when the laptop is on the dock.

In fact, after disconnecting the external monitor from the laptop to restore my dock setup, and then docking my laptop back gave me a blank screen on both monitors. Only the mouse pointer was there and I could move it, but nothing else. Only thing I could do is go to another terminal (ctrl + alt + f1) and then kill the XOrg server.

Comment 3 Jiri Skala 2010-06-04 05:25:25 UTC
I use ThinkPad T61. The system frozen trying to undock my laptop. I've fixed it disabling docking station in bios. Try to check for your bios setup.

Comment 4 Jiri Skala 2010-06-04 08:54:13 UTC
Which kernel version do you have?

Comment 5 Akshay Dua 2010-06-04 19:09:08 UTC
I checked my bios settings but did not see anything regarding a docking station. Am I looking for the correct field?

My kernel version is: 2.6.33.5-112.fc13.i686.PAE #1 SMP

Comment 6 Jiri Skala 2010-06-07 07:20:50 UTC
I suppose this is kernel issue...

Comment 7 Jorge Gallegos 2010-06-09 17:51:15 UTC
This also happens to me with a thinkpad R61 (a couple of years old) and a docking station:

 - If you try to undock the laptop, will freeze
 - If you try to change the output device (Fn + F7 in my case), will freeze. This used to cycle between laptop screen, external screen, both.
 - Closing the lid while docked will freeze it. This used make the external display the main display
 - If the laptop is not docked, these symptoms are not present, but I can dig further if needed.

I checked the xorg and messages logs but no meaningful messages are there... it would seem as if the system completely locks up.

Comment 8 Ted Felix 2010-06-10 19:33:44 UTC
There are many things that can cause acpi-related problems.  One easy thing to try would be to kill acpid:

  sudo killall acpid

Now try your various keys and see if they work.  If so (or if the system no longer hangs), then it is very likely that acpid was the problem.

We did have a problem at one point with acpid going into an endless loop for certain keypresses due to the contents of some config files.  While this sounds similar, I think it may have been a Debian problem.

acpi events (roughly) follow a path through the following:

1. hardware
2. BIOS
3. kernel/drivers
4. acpid
5. window manager

There are other steps in there too, like dbus, but those are the biggies.  Two more ideas:  First, try running without X and your window manager.  Do the symptoms change?  Second, try the "kacpimon" utility that comes with the acpid source.  This will show you what acpi messages are coming from the kernel.  Are you getting the expected messages?

Comment 9 Bug Zapper 2010-07-30 11:47:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Kamil Páral 2010-09-08 13:57:02 UTC
Similar issue for Thinkpad T500 and Fedora 13.

* Booting and suspending outside of docking station works fine.
* Booting and suspending inside docking station works fine.
* Booting inside docking station, undocking and then suspending makes the suspend light blink indefinitely and laptop is frozen.
* Booting inside docking station, undocking, docking again and then suspending makes the suspend light blink indefinitely and laptop is frozen.

However, I have a feeling that not every time this holds for 100%. But usually it "works" this way.

Comment 11 Bug Zapper 2011-06-02 12:18:34 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 12 Kamil Páral 2011-06-02 13:09:24 UTC
I think this could be related to NFS. Since the time I disabled NFS mounts on my machine I get this problem really rarely (but still happens sometimes nevertheless).

Fedora 14

Comment 13 Dave Jones 2011-10-11 19:36:52 UTC
There is ongoing work to improve NFS/suspend interaction. This isn't going to get fixed in F14.

Akshay, can you confirm whether you were also using NFS ?

Comment 14 Josh Boyer 2012-02-27 17:54:35 UTC
No update in 4 months.  Also there were fixes for NFS and CIFS for suspend/resume that went into later kernels.

If you are still having issues with the 2.6.42.7 or newer kernel, please open a new bug with relevant details.

Comment 15 Kamil Páral 2012-02-29 14:30:50 UTC
I could not reproduce this on Fedora 16 while using autofs (NFS directories opened in Nautilus) and docking station. It seems fixed.


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