From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Kristen Accardi <kristen.c.accardi@intel.com>
Cc: linux-acpi@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
linux-ide@vger.kernel.org
Subject: Re: 2.6.17-rc5-mm3: oops when ejecting dock
Date: Tue, 06 Jun 2006 16:34:33 -0700 [thread overview]
Message-ID: <44861109.7090502@goop.org> (raw)
In-Reply-To: <1149634494.13089.53.camel@whizzy>
Kristen Accardi wrote:
> So, here is a patch which will fix the bug. The problem that I found
> after I fixed the bug occurs in this circumstance:
> 1. boot in ultrabase
> 2. undock
>
> But not in this case:
> 1. boot outside base
> 2. dock/undock etc.
>
> The symptom of the problem is that you will undock and your machine will
> get a softlockup on a CPU and just hang. Checking the log file (when
> possible) shows lots errors from hdc: and ide: (this ultrabase has a
> cdrom on it which would be hdc). I am using an x40 to duplicate the
> issue, so you may have a different experience than I do. The problem
> seems to be that the cdrom that is on the ultrabase is not unplugging
> gracefully. I may have to hook up with whoever is working on the ide
> hotplug and see if this is something I can fix.
>
> Incidentally, the reason it works fine when you boot outside the base
> and then dock/undock is because the cdrom is also not getting properly
> inserted. So, it appears to power it on, but it is not actually being
> hotplugged.
I've observed this without the acpi dock driver present.
I was wondering if the ibm acpi ultrabay file ("bay") entry could be
used to "eject" the optical device. It doesn't appear on the X60
(listed as "not supported"), probably because the ACPI name changed to
SATA from than IDE0; I haven't really looked into it yet. But I think
the basic problem is that the IDE layer doesn't seem to support hot
add/remove of devices.
I guess that means that at present the acpi dock driver does nothing,
but it at least gives us an event to hang the ata device events off once
the subsystem supports hot (or even warm) device add/remove.
J
next prev parent reply other threads:[~2006-06-06 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4483EB38.30609@goop.org>
[not found] ` <1149554579.6006.10.camel@whizzy>
[not found] ` <4484D244.3010905@goop.org>
2006-06-06 15:50 ` 2.6.17-rc5-mm3: oops when ejecting dock Kristen Accardi
[not found] ` <1149634494.13089.53.camel@whizzy>
2006-06-06 23:34 ` Jeremy Fitzhardinge [this message]
2006-06-07 0:16 ` Kristen Accardi
2006-06-07 11:42 ` Matthew Garrett
2006-06-09 1:15 ` Jeremy Fitzhardinge
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=44861109.7090502@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
/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).