From: Tejun Heo <htejun@gmail.com>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: 2.6.22.6 sata_sil device errors & timeouts
Date: Mon, 17 Sep 2007 11:18:49 +0200 [thread overview]
Message-ID: <46EE4679.7030600@gmail.com> (raw)
In-Reply-To: <76366b180709170135v6c46f3d6qd3586ea79f9abc2@mail.gmail.com>
Andrew Paprocki wrote:
> 1) When built with modules disabled, and libata handling the sata +
> pata (AMD CS5536) connections, the pata drives come _after_ the sata
> drives (i.e. w/ 2 sata drives, the first IDE drive is sdc). This makes
> boot configuration more complicated if booting off the pata drive. Is
> there any way to control which order the drives are assigned when not
> building w/ modules?
Please use mount-by-LABEL or UUID.
> 2) The drives display that they support udma6 in hdparm -I, but only
> udma5 is being used. And hdparm -i only shows up to udma2.. ?
For SATA, UDMA mode doesn't matter at all. As long as you're in DMA
mode, the only thing that matters is PHY link speed and whether NCQ is
enabled.
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x280000 action 0x0
In both cases, SError is indicating transmission problem. Handshake
error and Unrecognized FIS type in the first case, 10b to 8b decode
error and CRC error on the second case. I can't tell why but signals
flying through those redish cables are getting corrupted.
There have been quite a few cases of bad PSU causing transmission
failures on SATA or you might have a bad controller and/or cables. The
best way to debug this kind of problem is by elimination - by swapping
hardware piece by piece you can find out which one is causing the problem.
--
tejun
next prev parent reply other threads:[~2007-09-17 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 8:35 2.6.22.6 sata_sil device errors & timeouts Andrew Paprocki
2007-09-17 9:18 ` Tejun Heo [this message]
2007-09-17 16:04 ` Andrew Paprocki
2007-09-17 17:07 ` Tejun Heo
2007-09-17 19:05 ` Andrew Paprocki
2007-09-17 19:26 ` Andrew Paprocki
2007-09-17 19:35 ` Bruce Allen
2007-09-17 21:06 ` Andrew Paprocki
2007-09-18 5:29 ` Bruce Allen
2007-09-18 14:36 ` Andrew Paprocki
2007-09-18 15:34 ` Bruce Allen
2007-09-27 7:15 ` Tejun Heo
2007-09-28 3:59 ` Bruce Allen
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=46EE4679.7030600@gmail.com \
--to=htejun@gmail.com \
--cc=andrew@ishiboo.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).