From: Tomas Carnecky <tom@dbservice.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Zhang Rui <rui.zhang@intel.com>, Steven King <sfking@fdwdc.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
ibm-acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking
Date: Mon, 01 Sep 2008 14:16:44 +0200 [thread overview]
Message-ID: <48BBDD2C.5020804@dbservice.com> (raw)
In-Reply-To: <20080901112816.GA21970@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
> On Mon, 01 Sep 2008, Tomas Carnecky wrote:
>> There is one question though that was never answered: Is there any
>> interaction needed from the userspace when docking/undocking? Something
>
> Yes. umount filesystems on any device in the dock, and issue the "power off
> dock" command (i.e. tell the kernel to *eject* the dock). This is *very*
> important, although the ThinkPad firmware/hardware will _try_ to protect the
> electronics if you just pull the laptop off the dock while it is still
> powered (but it might just not be able to do it, so Don't Do That!).
>
> Anyway, if your dock led is going off before you remove the laptop from the
> dock, you're doing everything correctly as far as the hardware is concerned.
>
> And the kernel will scream bloody murder if you remove a device with live
> filesystems in it, so it should be trivial to check if that part is being
> taken care of by your userspace as well. Not that something like this would
> be an excuse to fail to suspend/resume after being undocked, mind you.
To undock, I press the button on the dock, the led blinks a couple times
and turns green (also, dmesg tells me that all USB devices have been
removed and they indeed stop functioning). Then I take the laptop out of
the dock.
Because the X61 lacks a CDROM drive, I bought a bay CDROM drive along
with the UltraBase. But there is no CDROM inside it (so no mounted
filesystems). I also have an USB keyboard and mouse plugged into the USB
slots in the dock. So it seems the kernel *should* take care of those
things without any userspace interaction.
I just tested suspend/resume with the CDROM drive removed (an empty
bay). Suspend/resume now works just fine, regardless how I dock/undock
the laptop.
Anyway, regarding the additional patches, which tree can I pull them
from? (I'm eager to test them, I very much want my dock to work properly)
thanks
tom
next prev parent reply other threads:[~2008-09-01 12:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 22:35 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking Steven King
2008-09-01 3:17 ` Zhang Rui
2008-09-01 10:50 ` Tomas Carnecky
2008-09-01 11:28 ` Henrique de Moraes Holschuh
2008-09-01 12:16 ` Tomas Carnecky [this message]
2008-09-01 18:34 ` Matthew Garrett
2008-09-01 19:05 ` Steven King
2008-09-03 14:45 ` 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after?undocking Holger Macht
2008-09-03 15:04 ` Tomas Carnecky
2008-09-07 22:39 ` Jeremy Fitzhardinge
2008-09-03 21:28 ` Henrique de Moraes Holschuh
2008-09-05 9:00 ` Holger Macht
2008-09-08 22:17 ` 2.6.26.[1-3] + x61 tablet + x6ultrabase: no resume after undocking Steven King
2008-09-01 11:34 ` Matthew Garrett
2008-09-01 18:21 ` Steven King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48BBDD2C.5020804@dbservice.com \
--to=tom@dbservice.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sfking@fdwdc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).