From: Jeff Garzik <jeff@garzik.org>
To: Orion Poplawski <orion@cora.nwra.com>
Cc: linux-kernel@vger.kernel.org,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: sata_mv hotplug flaky?
Date: Tue, 11 Dec 2007 23:17:28 -0500 [thread overview]
Message-ID: <475F60D8.5060903@garzik.org> (raw)
In-Reply-To: <fjn8j2$mji$1@ger.gmane.org>
Orion Poplawski wrote:
> Not sure what the latest status of sata_mv hotplug should be, but it
> seems close. I'm currently running 2.6.24-0.81.rc4.git7.fc9 with a
> MV88SX5081. Pulled a couple drives and re-added. One device got
> re-added, but the other did not. It seems like I got the system to
> probe and re-add the first drive by doing a "mount -a", but haven't been
> able (no idea how) to re-add the second.
>
hotplug made great strides with the introduction of the new-EH code, but
it still needs a bit of work. Mark Lord was looking into that, so you
can sure your report has been noted...
Jeff
next parent reply other threads:[~2007-12-12 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fjn8j2$mji$1@ger.gmane.org>
2007-12-12 4:17 ` Jeff Garzik [this message]
2007-12-12 14:03 ` sata_mv hotplug flaky? Mark Lord
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=475F60D8.5060903@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=orion@cora.nwra.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).