Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Sep 2004 21:58:17 +0200
From:      =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk>
To:        Daniel Eriksson <daniel_k_eriksson@telia.com>
Cc:        current@freebsd.org
Subject:   Re: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=207594611
Message-ID:  <4149F059.5030708@DeepCore.dk>
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAC8YFoRpoaUeE8xMlUnz6pQEAAAAA@telia.com>
References:  <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA0VcX9IoJqUaXPS8MjT1PdsKAAAAQAAAAC8YFoRpoaUeE8xMlUnz6pQEAAAAA@telia.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Daniel Eriksson wrote:
> This is a me-too report:
>=20
> After upgrading a 6-CURRENT kernel and world from 2004.09.09.08.00.00 t=
o
> 2004.09.16.13.00.00, I am now getting these messages on a machine that
> previously worked just fine:
>=20
> ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D75822564
> ad0: WARNING - READ_DMA no interrupt but good status
> ad12: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D107702399
> ad12: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D150299860
> ad2: WARNING - READ_DMA no interrupt but good status
> ad3: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D150375742
> ad3: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D68555470
> ad2: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D152916568
> ad2: WARNING - READ_DMA no interrupt but good status
> ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D177638432
> ad2: WARNING - READ_DMA no interrupt but good status
> ad14: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D326989843
> ad14: WARNING - READ_DMA no interrupt but good status
> ad14: TIMEOUT - READ_DMA retrying (2 retries left) LBA=3D327711355
> ad14: WARNING - READ_DMA no interrupt but good status
>=20
> I only get the messages when I blast the discs with I/O, like when doin=
g
> fsck on all the file systems simultaneously. Also, fsck does not report=
 any
> problems so all operations seem to succeed.
>=20
> 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=20
to be safe could you try to just backstep /sys/dev/ata and see if that=20
changes anything ?

-S=F8ren



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?4149F059.5030708>