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

[Jens Axboe <axboe@suse.de>]

On Fri, Jul 08 2005, Tejun Heo wrote:
> On Fri, Jul 08, 2005 at 10:03:48AM +0200, Jens Axboe wrote:
> > Hi,
> > 
> > Ok, one more error, this time from irq context:
> > 
> > AHCI: ata1: error irq, status=40000001 stat=51 err=04 sstat=00000113
> > serr=00000000
> > ata1: aborting commands due to error.  active_tag -1, sactive 00000001
> > ahci: sactive 1
> > ata1: recovering from error
> > sactive=0
> > ata1: failed to read log page 10h (-110)
> > ata1: resetting...
> > ata1: started resetting...
> > ata1: end resetting, sstatus=00000113
> > 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 2120875
> > Buffer I/O error on device sda2, logical block 2045
> > lost page write due to I/O error on sda2
> > 
> > -- 
> > Jens Axboe
> 
>  Hi, Jens.
> 
>  I also have a weird lockup log.  This log is generated with the
> second take of NCQ patchset I've posted yesterday.  It's Samsung
> HD160JJ on ICH7R AHCI.  Every command with tag#3 is scrambled, so
> recovery operations are performed constantly (log 10h, if that fails
> COMRESET).  After a few hours, the drive failed to become online after
> COMRESET.  Rebooting didn't work.  BIOS couldn't detect/recover it.  I
> had to power-cycle to make it online again.  I'm running similar test
> with much lower error-late (5~6 errors per 3000 requests) to avoid too
> many COMRESET's and, for more than six hours, it's been running okay.
> Error log follows.

very strange, the drive must be really buggered.

>  Jens, can you run your test with the new patchset?

Sure, I will try. But I will be away from this box for the next two
weeks (vacation, then KS/OLS), so I cannot do much about it in the near
future...

-- 
Jens Axboe