From: Jeff Garzik <jeff@garzik.org>
To: Daniel Schroeder <sec@dschroeder.info>
Cc: linux-ide@vger.kernel.org
Subject: Re: device error via SDB FIS
Date: Sat, 30 Jun 2007 17:46:47 -0400 [thread overview]
Message-ID: <4686CF47.5070409@garzik.org> (raw)
In-Reply-To: <4686CE2A.5070307@dschroeder.info>
Daniel Schroeder wrote:
>
>>> ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
>>> ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
>>> ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data
>>> 20480 out
>>> res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
>>
>> Command 0x61 is FPDMA WRITE (NCQ WRITE).
>>
>> Error 0x04 is 'command aborted'.
>>
>> Not much the driver can do but follow what the device is telling us...
>>
>> If you disable NCQ, presumably this should go away.
> thanks for your explanation, i will monitor this drive and disable ncq
> if it happens again
I should have added: given your report, it sounds like the error
handling code took appropriate action for your error. It should
continue transferring data (though perhaps not in NCQ mode anymore).
HOPEFULLY all you see is a nasty message when the drive complains :)
If that is not the case, if you are seeing data transfer suddenly cease
(or worse, data corruption) please do speak up...
Jeff
prev parent reply other threads:[~2007-06-30 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 17:10 device error via SDB FIS Daniel Schroeder
2007-06-30 17:12 ` Justin Piszcz
2007-06-30 21:12 ` Daniel Schroeder
2007-06-30 21:14 ` Justin Piszcz
2007-06-30 21:22 ` Jeff Garzik
2007-06-30 21:33 ` Justin Piszcz
2007-06-30 21:42 ` Daniel Schroeder
2007-06-30 21:46 ` Jeff Garzik [this message]
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=4686CF47.5070409@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=sec@dschroeder.info \
/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).