From: Brad Campbell <brad@wasp.net.au>
To: linux-ide@vger.kernel.org
Subject: Re: sata media errors not propagated? (was Re: sata_via issue)
Date: Tue, 17 Aug 2004 20:40:47 +0400 [thread overview]
Message-ID: <4122350F.3040700@wasp.net.au> (raw)
In-Reply-To: <1092741447.1581.33.camel@localhost>
Kevin Shanahan wrote:
I have done about 15 re-compiles now with increasing numbers of printk's added and have got this far.
scsi -> libata to ata_queued_cmd
>
> Buffer I/O error on device sdb2, logical block 7281
> ata2: command 0x25 timeout, stat 0x59 host_stat 0x1
> scsi1: ERROR on channel 0, id 0, lun 0, CDB: 0x28 00 00 03 29 f0 00 00 ec 00
> Current sdb: sense = 70 3
> ASC=11 ASCQ= 4
> Raw sense data:0x70 0x00 0x03 0x00 0x00 0x00 0x00 0x06 0x00 0x00 0x00 0x00 0x11 0x04
> end_request: I/O error, dev sdb, sector 207344
Here the libata layer passes the error back to scsi and everyone is happy. (uses ata_scsi_qc_complete)
>
> Then always ends with the following:
About here, scsi passes a command down to libata, ata_queued_cmd which causes the next 3 messages.
libata never errors out here and completes the request so it all falls in a heap.
I'm going out to dinner, I'll see if I can trace it further later tonight.
> ATA: abnormal status 0x59 on port 0xB807
> ATA: abnormal status 0x59 on port 0xB807
> ATA: abnormal status 0x59 on port 0xB807
Not much help, but closing in.
Regards,
Brad
next prev parent reply other threads:[~2004-08-17 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 11:17 sata media errors not propagated? (was Re: sata_via issue) Kevin Shanahan
2004-08-17 12:38 ` Brad Campbell
2004-08-17 16:40 ` Brad Campbell [this message]
2004-08-17 18:57 ` Brad Campbell
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=4122350F.3040700@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-ide@vger.kernel.org \
/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).