From: Phil Dibowitz <phil@ipom.com>
To: Tomi Orava <Tomi.Orava@ncircle.nullnet.fi>
Cc: Mikael Pettersson <mikpe@it.uu.se>, linux-ide@vger.kernel.org
Subject: Re: sata_promise ata exceptions (2.6.20.6)
Date: Sun, 15 Apr 2007 23:55:31 -0700 [thread overview]
Message-ID: <46231DE3.8070404@ipom.com> (raw)
In-Reply-To: <38769.194.237.142.7.1176209348.squirrel@ncircle.nullnet.fi>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
Given that the last one was a hardware issue, I bought a new controller.
Despite my bad luck, given my price-range promise still seemed to be the one
with the most good reports, so I went with that. I was going to go with a
sil, but I couldn't find one..
Anyway, things are MUCH better now... but about once a week, I get:
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (port_status 0x00001000)
ata2.00: cmd c8/00:80:9a:71:d0/00:00:00:00:00/ea tag 0 cdb 0x0 data 65536 in
res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x24 (host bus error)
ata2: soft resetting port
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: configured for UDMA/133
ata2: EH complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
It's the same port_status and Emask/SAct/SErr/action each time... only the
cmd/res and data change (obviously those would change)...
Can anyone tell me what that means?
--
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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-04-16 6:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 10:18 sata_promise ata exceptions (2.6.20.6) 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 [this message]
2007-04-16 7:02 ` Tomi Orava
2007-04-16 7:47 ` Phil Dibowitz
-- 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 21:33 Mikael Pettersson
2007-04-09 22:02 ` Phil Dibowitz
2007-04-09 22:42 ` Greg Freemyer
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=46231DE3.8070404@ipom.com \
--to=phil@ipom.com \
--cc=Tomi.Orava@ncircle.nullnet.fi \
--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).