Re: translated ATA stat/err 0x51/0c to ... PDC20376 (FastTrak 376) related cold freezes

[Tejun Heo <htejun@gmail.com>]

[cc'ing Jeff & linux-ide, quoting whole body]

Jeff, here's a EH test case for sata_promise, just in case you missed 
this thread.

Tejun Heo wrote:
> Soeren Sonnenburg wrote:
> > On Sun, 2006-08-27 at 18:37 +0900, Tejun Heo wrote:
> > > Soeren Sonnenburg wrote:
> > > > Dear all,
> > > >
> > > > I just upgraded to using 2 sata disks (both seagate drives
> > > > ST3400832AS and ST3750640AS) on this asus a7v8x on-board promise 
> > > > fastrak
> > > > 376 (PDC20376) controller. However, as soon as I do a lot of io (cp 
> > > > some
> > > > G of files) I get swamped in
> > > > ata1: translated ATA stat/err 0x51/0c to SCSI SK/ASC/ASCQ 0xb/00/00
> > > > ata1: status=0x51 { DriveReady SeekComplete Error }
> > > > ata1: error=0x0c { DriveStatusError }
> > > > ata2: translated ATA stat/err 0x51/0c to SCSI SK/ASC/ASCQ 0xb/00/00
> > > > ata2: status=0x51 { DriveReady SeekComplete Error }
> > > > ata2: error=0x0c { DriveStatusError }
> > > > ...
> > > Is the system usable after these messages?
> >
> > Yes, however I got cold freezes from (time to time) after a while...
>
> I see.  your drive is reporting error for some reason and libata is 
> failing to recover.
>
> > > > messages. For that it is enough to do it on a single drive or copy from
> > > > drive to drive. This is on kernel 2.6.17.4, but I remember (when I was
> > > > still using a single drive) this very same output to happen on 2.6.15.
> > > >
> > > > Can anyone translate these dubious error messages to me ?
> > > >
> > > > Here are more details about the system:
> > > >
> > > > - the sata_promise driver version 1.04 is used
> > > Can you give a shot at 2.6.18-rc4?
> >
> > I will, though I don't see much changes in that driver...
>
> Ah.. right.  sata_promise isn't converted to new EH yet.  There's no 
> reason to try -rc4.  Please stand by.
>
> Thanks.

--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/