ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=207594611

[Søren Schmidt]

Daniel Eriksson wrote:
> This is a me-too report:
> 
> After upgrading a 6-CURRENT kernel and world from 2004.09.09.08.00.00 to
> 2004.09.16.13.00.00, I am now getting these messages on a machine that
> previously worked just fine:
> 
> ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=75822564
> ad0: WARNING - READ_DMA no interrupt but good status
> ad12: TIMEOUT - READ_DMA retrying (2 retries left) LBA=107702399
> ad12: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=150299860
> ad2: WARNING - READ_DMA no interrupt but good status
> ad3: TIMEOUT - READ_DMA retrying (2 retries left) LBA=150375742
> ad3: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=68555470
> ad2: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=152916568
> ad2: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=177638432
> ad2: WARNING - READ_DMA no interrupt but good status
> ad14: TIMEOUT - READ_DMA retrying (2 retries left) LBA=326989843
> ad14: WARNING - READ_DMA no interrupt but good status
> ad14: TIMEOUT - READ_DMA retrying (2 retries left) LBA=327711355
> ad14: WARNING - READ_DMA no interrupt but good status
> 
> I only get the messages when I blast the discs with I/O, like when doing
> fsck on all the file systems simultaneously. Also, fsck does not report any
> problems so all operations seem to succeed.
> 
> Other then cvsup'ing the new sources, no other changes were made to the
> machine or the configuration.

Interesting as there isn't any real ATA changes in that period, anyhow 
to be safe could you try to just backstep /sys/dev/ata and see if that 
changes anything ?

-Søren