From: Tejun Heo <htejun@gmail.com>
To: Marc Bowes <marcbowes@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-ide@vger.kernel.org
Subject: Re: SATA: link online but device misclassified
Date: Sat, 20 Jun 2009 21:34:00 +0900 [thread overview]
Message-ID: <4A3CD738.1080105@gmail.com> (raw)
In-Reply-To: <cfa4e840906190238m4cca2c73pece279bb642bfd1f@mail.gmail.com>
Marc Bowes wrote:
> Hi,
>
> Tejun, the motherboard is a Gigabyte EP45-DQ6. Attached are dmidecode
> and a new dmesg.txt, as I have enabled AHCI mode.
Yeah, you have 2 sil5723's hanging off the jmicron controller. If you
have harddisks connected to those ports it will be okay. If not,
they'll keep the link online but timeout on SRST. Hmmm... not really
sure what to do yet. Maybe we can do some sort of blacklisting. I
wonder how windows copes with this. Hmmm...
--
tejun
next prev parent reply other threads:[~2009-06-20 12:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 0:15 SATA: link online but device misclassified Marc Bowes
2009-06-11 4:27 ` Robert Hancock
2009-06-11 9:31 ` Marc Bowes
2009-06-11 19:01 ` James Bottomley
2009-06-11 19:32 ` Marc Bowes
[not found] ` <cfa4e840906160759m31db333cr555104ca0e3c6255@mail.gmail.com>
2009-06-16 15:03 ` Marc Bowes
2009-06-16 15:21 ` James Bottomley
[not found] ` <cfa4e840906160946qc998331p308624ac10f15060@mail.gmail.com>
[not found] ` <1245171448.3965.46.camel@mulgrave.site>
2009-06-16 18:13 ` Marc Bowes
2009-06-19 1:38 ` Robert Hancock
2009-06-19 4:00 ` Tejun Heo
2009-06-19 9:38 ` Marc Bowes
2009-06-19 9:44 ` Marc Bowes
2009-06-20 12:34 ` Tejun Heo [this message]
2009-06-20 13:13 ` Marc Bowes
2009-06-25 13:54 ` Tejun Heo
2009-06-29 10:20 ` Tejun Heo
2009-07-01 8:07 ` Marc Bowes
2009-07-01 23:31 ` Tejun Heo
2009-07-02 9:22 ` Marc Bowes
2009-07-08 4:14 ` Tejun Heo
[not found] <cfa4e840906101331q71532d72v5361a72e9b77ce63@mail.gmail.com>
2009-06-10 20:34 ` Matthew Wilcox
2009-06-10 20:40 ` Marc Bowes
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=4A3CD738.1080105@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=marcbowes@gmail.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).