Re: DRDY errors again

Re: DRDY errors again

[Jeff Garzik]

J.A. Magallón wrote:
> scsi4 : ata_piix
> scsi5 : ata_piix
> ata3: SATA max UDMA/133 cmd 0xc000 ctl 0xc400 bmdma 0xd000 irq 18
> ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xcc00 bmdma 0xd008 irq 18

> ata4.00: ATA-8: ST3500820AS, SD25, max UDMA/133
> ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> ata4.00: configured for UDMA/133

> ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata4.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
>          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata4.00: status: { DRDY }

Can you bisect to see when this problem starts?  I'm pretty sure it's 
software, either interrupt-related or the libata driver itself.

See http://ata.wiki.kernel.org/index.php/Libata_error_messages for a 
full explanation of that error message.

Most notable:  "DRDY" == device ready == device says everything is OK, 
from it's perspective.  "timeout" usually means an interrupt wasn't 
delivered from your ATA controller, when we were expecting one.

	Jeff

Re: DRDY errors again

[J.A. Magallón]

On Tue, 08 Apr 2008 11:59:51 -0400, Jeff Garzik <jeff@garzik.org> wrote:

> J.A. Magallón wrote:
> > scsi4 : ata_piix
> > scsi5 : ata_piix
> > ata3: SATA max UDMA/133 cmd 0xc000 ctl 0xc400 bmdma 0xd000 irq 18
> > ata4: SATA max UDMA/133 cmd 0xc800 ctl 0xcc00 bmdma 0xd008 irq 18
> 
> > ata4.00: ATA-8: ST3500820AS, SD25, max UDMA/133
> > ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
> > ata4.00: configured for UDMA/133
> 
> > ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> > ata4.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
> >          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> > ata4.00: status: { DRDY }
> 

I'm still trying to dig this...

After googling sometime I saw several reports like mine (it looks like a too
common problem). In those repots, kernel messages were a bit different from
mine. For example, from http://marc.info/?l=linux-kernel&m=119498755206823&w=2:

ata1.00: status: { DRDY }
ata1: soft resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: configured for UDMA/133
ata1: EH complete

Why I don't have any "SATA link up..." message ?

And at device init, some logs read like:

ata1.00: ATA-8: WDC WD2500BEVS-22UST0, 01.01A01, max UDMA/133
ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133

Mine is like:

ata3.00: ATA-8: WDC WD3200AVJS-63WDA0, 12.01B02, max UDMA/133
ata3.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)  <===== 0, not 31 ??
ata3.00: configured for UDMA/133
ata4.00: ATA-8: ST3500820AS, SD25, max UDMA/133
ata4.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)  <===== 0, not 31 ??
ata4.00: configured for UDMA/133

Just to see if I have some strange behaviour...

-- 
J.A. Magallon <jamagallon()ono!com>     \               Software is like sex:
                                         \         It's better when it's free
Mandriva Linux release 2008.1 (Cooker) for i586
Linux 2.6.23-jam05 (gcc 4.2.2 20071128 (4.2.2-2mdv2008.1)) SMP PREEMPT