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: Thu, 20 Dec 2007 15:19:28 +0900 [thread overview]
Message-ID: <476A0970.9090804@gmail.com> (raw)
In-Reply-To: <B90463BC30D2E446BA423D888DC85E50087A77@sshaexmb1.amd.com>
Hello,
Shane Huang wrote:
>>> Do you guys think it's normal? It not, how to make SATA hotplug work
> on
>>> different SATA port? Should it be supported by BIOS or hardware?
>> If you connect it to a different port, the original device will die
> and
>> new device will appear. That's the expected behavior. In the log, I
>> only see ata3.00 is dying. Isn't there any log from different port?
>
> There is no other log from the different port such as the enablement of
> ata2,
> it's strange. I forgot to say that this case appear when the "OnChip
> SATA Type"
> is "Native IDE"(SATA device ID is 4390) in BIOS.
>
> But when I set "OnChip SATA type" into "AHCI" mode(SATA device ID 4391),
> the hotplug can work, and the device name will be changed from "scd0" to
> "scd1"
> during the hotplug. The log messages are attached at the end of this
> mail.
That's strange. I guess we're forgetting something when forcing the
controller into AHCI mode. 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?
Also, after driver is loaded, can you please post the results of "lspci
-nnvvvxxx" with BIOS mode set to IDE and AHCI?
Thanks.
--
tejun
next prev parent reply other threads:[~2007-12-20 6:19 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 [this message]
2007-12-20 9:05 ` Shane Huang
2007-12-20 10:43 ` Shane Huang
2007-12-21 7:35 ` Tejun Heo
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=476A0970.9090804@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.