From: Tejun Heo <htejun@gmail.com>
To: Thomas Tsai <bthomas.tsai@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Failed to IDENTIFY SATA harddrive on sata_sil24
Date: Tue, 03 Jul 2007 16:52:17 +0900 [thread overview]
Message-ID: <468A0031.3040709@gmail.com> (raw)
In-Reply-To: <6a3d41200706270814o7675909dtbdafe4a4fa68943c@mail.gmail.com>
Thomas Tsai wrote:
> Hi,
>
> Does anyone familiar with SiliconImage 3132 SATA controller?
> I'm running siliconimage 3132 as e-Sata controller on my ARM-based board.
> My kernel version is 2.6.18.6. I built libata and sata_sil24 as kernel
> module.
> After I insert libata and sata_sil24 module, and plug external
> harddrive via e-Sata.
> sata_sil24.c can detect phy changed, and found a ATA device.
> And then it will issue IDENTIFY(0xec) command but time out to get
> command completion.
> And Sil3132 seems dead or enter into an unknown state.Since it will
> not issue any interrupts even I remove and replug the e-Sata cable.
> Does anyone have experienced this situation, or any suggestion.
> Thanks.
You need to post the kernel log at least.
--
tejun
prev parent reply other threads:[~2007-07-03 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 15:14 Failed to IDENTIFY SATA harddrive on sata_sil24 Thomas Tsai
2007-06-27 18:16 ` Jeff Garzik
2007-07-03 7:52 ` 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=468A0031.3040709@gmail.com \
--to=htejun@gmail.com \
--cc=bthomas.tsai@gmail.com \
--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).