From: Phil Dibowitz <phil@ipom.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_promise ata exceptions (2.6.20.6)
Date: Mon, 9 Apr 2007 15:02:33 -0700 [thread overview]
Message-ID: <20070409220233.GA3088@ipom.com> (raw)
In-Reply-To: <200704092133.l39LXtrM022972@harpo.it.uu.se>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
On Mon, Apr 09, 2007 at 11:33:55PM +0200, Mikael Pettersson wrote:
> The error decodes as:
> port_status 0x20200000: Drive Error during Packet Command Cycle
> (the drive signalled an error to the controller)
>
> SErr 0x380100: CRC error, Disparity error, 10B-to-8B decoding error,
> non-recoverable transient data integrity error.
>
> My conclusion is that the link between the controller and the drive
> is corrupting messages. This is almost certainly a hardware problem,
> and could be a broken motherboard (you wrote that you hadn't used
> the mobo's Promise chip before), bad cables, bad drives, a bad power
> supply, or electrical interference.
Mikael,
Thanks for the quick response. I appreciate your help. I guess I'm buying a
SATA PCI card!
Looks like my choice of reasonably-priced known-brands is Highpoint and
Promise (specifically a Highpoint ROCKETRAID1520 or a Promise SATA300 TX4) -
are one of these brands better from a Linux compatibility or hardware-bug
standpoint?
Thanks again.
--
Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-09 22:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 21:33 sata_promise ata exceptions (2.6.20.6) Mikael Pettersson
2007-04-09 22:02 ` Phil Dibowitz [this message]
2007-04-09 22:42 ` Greg Freemyer
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 7:42 Mikael Pettersson
2007-04-14 9:27 Mikael Pettersson
2007-04-14 12:46 ` Tomi Orava
2007-04-13 21:21 Mikael Pettersson
2007-04-14 7:13 ` Tomi Orava
2007-04-19 10:55 ` Tomi Orava
2007-04-09 10:18 Mikael Pettersson
2007-04-09 16:01 ` Phil Dibowitz
2007-04-09 20:26 ` Phil Dibowitz
2007-04-10 12:49 ` Tomi Orava
2007-04-13 18:36 ` Tomi Orava
2007-04-16 6:55 ` Phil Dibowitz
2007-04-16 7:02 ` Tomi Orava
2007-04-16 7:47 ` Phil Dibowitz
2007-04-07 23:41 Phil Dibowitz
2007-04-08 10:43 ` Ansgar Knappheide
2007-04-09 6:13 ` Phil Dibowitz
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=20070409220233.GA3088@ipom.com \
--to=phil@ipom.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).