From: Tejun Heo <htejun@gmail.com>
To: rweeks@razorwire.ca
Cc: 'Jim Paris' <jim@jtan.com>, linux-ide@vger.kernel.org
Subject: Re: sata-nv hotplug feature
Date: Mon, 12 Mar 2007 14:41:57 +0900 [thread overview]
Message-ID: <45F4E825.6050603@gmail.com> (raw)
In-Reply-To: <000401c762de$7baf5b60$6400a8c0@foxbat>
Hello,
Russ Weeks wrote:
> Thanks, Jim, Tejun. Upgrading to 2.6.20 solved all my problems.
Great.
> What I observe now is that once the drive is plugged in again, 2-3
> minutes may pass before the device entry appears in /dev. This isn't a
> problem for me, but if you have time to explain I'd be interested to
> know why.
Please post the result of dmesg and lspci -nn.
> Also, if you have any tips on 'best practices' for drive yanking, I'd
> appreciate 'em. So far I'm just doing 'sdparm --command=stop'.
That should do the job.
--
tejun
prev parent reply other threads:[~2007-03-12 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 4:39 sata-nv hotplug feature Russ Weeks
2007-03-08 8:21 ` Tejun Heo
2007-03-08 9:38 ` Jim Paris
2007-03-10 6:36 ` Russ Weeks
2007-03-12 5:41 ` Tejun Heo [this message]
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=45F4E825.6050603@gmail.com \
--to=htejun@gmail.com \
--cc=jim@jtan.com \
--cc=linux-ide@vger.kernel.org \
--cc=rweeks@razorwire.ca \
/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).