From owner-freebsd-current@FreeBSD.ORG Thu Sep 16 19:58:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA4C016A4CE for ; Thu, 16 Sep 2004 19:58:21 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4578443D45 for ; Thu, 16 Sep 2004 19:58:21 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i8GJwJxA024187; Thu, 16 Sep 2004 21:58:19 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <4149F059.5030708@DeepCore.dk> Date: Thu, 16 Sep 2004 21:58:17 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eriksson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable cc: current@freebsd.org Subject: Re: ad0: TIMEOUT - READ_DMA retrying (2 retries left) LBA=207594611 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 19:58:22 -0000 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