From: "Dan Merillat" <dan.merillat@gmail.com>
To: "Mikael Pettersson" <mikpe@it.uu.se>
Cc: gf435@gmx.net, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: sata_promise disk error 2.6.22-rc5 with hrt1 patch
Date: Sat, 7 Jul 2007 02:28:10 -0400 [thread overview]
Message-ID: <a56dfcf00707062328v505bf738kb01e7560f3f3f6ee@mail.gmail.com> (raw)
In-Reply-To: <200706242130.l5OLUgY8004346@harpo.it.uu.se>
On 6/24/07, Mikael Pettersson <mikpe@it.uu.se> wrote:
> (cc: linux-ide added)
>
> The 300 TX4 model is causing transient errors for several people,
> and we don't yet know why. In your case, port_status 0x00001000
> means that "host bus is busy more than 256 clock cycles for every
> ATA I/O transfer" (quoting the docs). Basically it's a timeout.
I'm running vanilla 2.6.22-rc7 here, getting a similar error.
[ 741.010863] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
[ 741.010869] ata2.00: (port_status 0x20080000)
[ 741.010875] ata2.00: cmd c8/00:08:bf:01:0c/00:00:00:00:00/ef tag 0
cdb 0x0 data 4096 in
[ 741.010877] res 50/00:00:c6:01:0c/00:00:00:00:00/ef Emask
0x2 (HSM violation)
[ 741.313131] ata2: soft resetting port
[ 741.463831] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 741.587208] ata2: EH complete
[ 741.640472] sd 1:0:0:0: [sdb] 1465149168 512-byte hardware sectors
(750156 MB)
[ 741.644141] sd 1:0:0:0: [sdb] Write Protect is off
[ 741.644144] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 741.670736] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
Identical card to the one otto posted. How common is this? I
wouldn't notice if it wasn't logged - I don't notice the blip in disk
access.
next prev parent reply other threads:[~2007-07-07 6:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 21:30 Mikael Pettersson
2007-07-07 6:28 ` Dan Merillat [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-24 18:49 otto Meier
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=a56dfcf00707062328v505bf738kb01e7560f3f3f6ee@mail.gmail.com \
--to=dan.merillat@gmail.com \
--cc=gf435@gmx.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®