From: Tejun Heo <htejun@gmail.com>
To: Shane Huang <Shane.Huang@amd.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: Questions about SATA hotplug in linux 2.6
Date: Fri, 21 Dec 2007 16:35:27 +0900 [thread overview]
Message-ID: <476B6CBF.5060607@gmail.com> (raw)
In-Reply-To: <B90463BC30D2E446BA423D888DC85E500881B1@sshaexmb1.amd.com>
Hello, Shane.
Shane Huang wrote:
>>> That's strange. I guess we're forgetting something when forcing the
>>> controller into AHCI mode.
>> Yes, it's strange. This issue also exists on RedHat RHEL5.1 and
> RHEL4.6
>>> What happens if you manually issue re-scan
>>> by doing "echo - - - > /sys/class/scsi_host/hostN/scan" where hostN
> is
>>> the SCSI host for the ATA port you moved the drive?
>> "echo" helps nothing in this issue, the /dev/scd1 still can not
> appear,
>> Here is the log message when do "echo", ata2 is the new SATA port
> connected
>> to SATA HDD after hotplug under native IDE mode:
>
> It seems that this issue has been fixed by our up to date BIOS.
> I will give you more information after further confirmation when
> necessary.
Great, thanks.
--
tejun
next prev parent reply other threads:[~2007-12-21 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 8:14 [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks, V2 David Miller
2007-10-25 8:24 ` [PATCH 0/5]: " Jeff Garzik
2007-10-26 2:27 ` Questions about SATA hotplug in linux 2.6 Shane Huang
2007-10-26 2:41 ` Jeff Garzik
2007-10-26 2:56 ` Tejun Heo
2007-12-18 7:29 ` Shane Huang
2007-12-18 9:18 ` Tejun Heo
2007-12-18 10:52 ` Shane Huang
2007-12-20 6:19 ` Tejun Heo
2007-12-20 9:05 ` Shane Huang
2007-12-20 10:43 ` Shane Huang
2007-12-21 7:35 ` Tejun Heo [this message]
2007-10-25 18:32 ` [PATCH 0/4]: Resolve MSI vs. INTX_DISABLE quirks, V2 Greg KH
2007-10-25 22:27 ` David Miller
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=476B6CBF.5060607@gmail.com \
--to=htejun@gmail.com \
--cc=Shane.Huang@amd.com \
--cc=jeff@garzik.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.