From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Samuel Masham <samuel.masham@gmail.com>
Cc: Mauro Tassinari <mtassinari@cmanet.it>, linux-kernel@vger.kernel.org
Subject: Re: libata/sata errors on ich[?]/maxtor
Date: Fri, 17 Mar 2006 11:34:54 +0000 [thread overview]
Message-ID: <1142595294.28614.3.camel@localhost.localdomain> (raw)
In-Reply-To: <93564eb70603162037g1856b7eey@mail.gmail.com>
On Gwe, 2006-03-17 at 13:37 +0900, Samuel Masham wrote:
> As you can see from the printk's here this error continues and the for
> every access (write?) to the drive you just have to wait for a
> timeout.
Eventually the drive will be offlined.
> ata1: command 0x35 timeout, stat 0xd1 host_stat 0x61
> ata1: translated ATA stat/err 0xd1/00 to SCSI SK/ASC/ASCQ 0xb/47/00
> ata1: status=0xd1 { Busy }
> SCSI disk error : host 0 channel 0 id 1 lun 0 return code = 8000002
> Current sd08:12: sense key Aborted Command
> Additional sense indicates Scsi parity error
It thinks there is a communication (eg cable problem), at least that is
how it has mapped the error report. Not something I'd expect to see in
the SATA case on several machines so it could be some kind of setup
error or timing incompatibility in the driver.
What is attached to that controller (SATA and PATA items)
next prev parent reply other threads:[~2006-03-17 11:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 23:02 libata/sata errors on ich[?]/maxtor Mauro Tassinari
2006-03-17 4:37 ` Samuel Masham
2006-03-17 6:01 ` Samuel Masham
2006-03-17 9:55 ` R: " mtassinari
2006-03-17 11:34 ` Alan Cox [this message]
2006-03-17 14:35 ` Samuel Masham
2006-03-17 15:10 ` R: " Mauro Tassinari
2006-03-22 9:59 ` Samuel Masham
2006-03-22 11:27 ` R: " mtassinari
2006-03-25 23:13 ` Ian Young
-- strict thread matches above, loose matches on Subject: below --
2006-03-18 16:17 Ian Young
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=1142595294.28614.3.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mtassinari@cmanet.it \
--cc=samuel.masham@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