From owner-freebsd-current@FreeBSD.ORG Mon Sep 20 04:44:37 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 2E16516A4CE for ; Mon, 20 Sep 2004 04:44:37 +0000 (GMT) Received: from smtp08.wanadoo.nl (smtp08.wanadoo.nl [194.134.35.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id BADDE43D49 for ; Mon, 20 Sep 2004 04:44:36 +0000 (GMT) (envelope-from j.asher@wanadoo.nl) Received: from localhost (c529d865e.cable.wanadoo.nl [82.157.134.94]) by smtp8.wanadoo.nl (Postfix) with ESMTP id 85BDD5A81C; Mon, 20 Sep 2004 06:44:35 +0200 (CEST) To: "Daniel Eriksson" , current@freebsd.org, =?utf-8?Q?'S=C3=B8ren_Schmidt'?= References: Message-ID: Date: Mon, 20 Sep 2004 06:44:49 +0200 From: "John Asher" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Opera M2/7.54 (FreeBSD, build 751) 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: Mon, 20 Sep 2004 04:44:37 -0000 I am also using the 6-CURRENT kernel i386 (i686) have somethimes at heavy load the same errors. Sep 16 12:41:45 xxx kernel: FreeBSD 6.0-CURRENT #0: Wed Sep 15 15:27:42 CE ST 2004 Sep 16 14:37:45 xxx kernel: ad1: TIMEOUT - READ_DMA retrying (2 retries le ft) LBA=14578175 I completely updated my sourcetree at that day, and recompiled the kernel, since that time this error occurs. Best regards, John Asher. On Thu, 16 Sep 2004 21:17:45 +0200, 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. > > /Daniel Eriksson > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/