Re: [PATCH Linux 2.6.12 00/09] NCQ: generic NCQ completion/error-handling

[Jens Axboe <axboe@suse.de>]

On Fri, Jul 01 2005, Jens Axboe wrote:
> >  I converted most of debug messages I've used during development into
> > warning messages when posting the patchset and forgot about it, so
> > I've never posted the debug patch.  Sorry about that.  Here's a small
> > patch which adds some more messages though.  The following patch also
> > adds printk'ing FIS on each command issue in ahci.c:ahci_qc_issue(),
> > if you think it would fill your log excessively, feel free to turn it
> > off.  It wouldn't probably matter anyway.
> 
> I will have to kill the issue part of the patch, that would generate
> insane amounts of printk traffic :-)
> 
> I'll boot the kernel and report what happens.

It triggered last night, but the old kernel was booted. This was the
log:

ahci ata1: stat=d0, issuing COMRESET
ata1: recovering from error
ata1: status=0x01 { Error }
ata1: error=0x80 { Sector }
SCSI error : <0 0 0 0> return code = 0x8000002
sda: Current: sense key=0x3
    ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 66255899
Buffer I/O error on device sda2, logical block 8018923
lost page write due to I/O error on sda2
ata1: status=0x01 { Error }
ata1: error=0x80 { Sector }
SCSI error : <0 0 0 0> return code = 0x8000002
sda: Current: sense key=0x3
    ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 66239043
Buffer I/O error on device sda2, logical block 8016816
lost page write due to I/O error on sda2
ata1: recovering from error
ata1: status=0x01 { Error }
ata1: error=0x80 { Sector }
SCSI error : <0 0 0 0> return code = 0x8000002
sda: Current: sense key=0x3
    ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 66239051
Buffer I/O error on device sda2, logical block 8016817
lost page write due to I/O error on sda2
ata1: status=0x01 { Error }
ata1: error=0x80 { Sector }
SCSI error : <0 0 0 0> return code = 0x8000002
sda: Current: sense key=0x3
    ASC=0x11 ASCQ=0x4
end_request: I/O error, dev sda, sector 35137043

Which just continues. I'll boot the right kernel now. I removed the
reset dependency on the read_log_page() issue, I'm suspecting we still
need that to kick start the drive after an error.

-- 
Jens Axboe