From owner-freebsd-current@FreeBSD.ORG Thu Apr 17 17:34:33 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1FD010656C3; Thu, 17 Apr 2008 17:34:33 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by mx1.freebsd.org (Postfix) with ESMTP id 691578FC0C; Thu, 17 Apr 2008 17:34:33 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.17] (helo=7.mx.freenet.de) by mout1.freenet.de with esmtpa (Exim 4.69) (envelope-from ) id 1JmY0F-0007tB-KA; Thu, 17 Apr 2008 19:34:31 +0200 Received: from x01ff.x.pppool.de ([89.59.1.255]:26518 helo=peedub.jennejohn.org) by 7.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #12) id 1JmY0F-0005KY-8j; Thu, 17 Apr 2008 19:34:31 +0200 Date: Thu, 17 Apr 2008 19:34:30 +0200 From: Gary Jennejohn To: Robert Watson Message-ID: <20080417193430.63adea19@peedub.jennejohn.org> In-Reply-To: <20080417144424.D71628@fledge.watson.org> References: <20080417144424.D71628@fledge.watson.org> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.10.14; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org, sos@FreeBSD.org Subject: Re: ATA problem in Parallels: warnings -> failures X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2008 17:34:34 -0000 On Thu, 17 Apr 2008 14:46:23 +0100 (BST) Robert Watson wrote: > > Dear Soren, > > Since my most recent kernel update, the intermittent TIMEOUT - READ_DMA > warnings I get on my parallels install appear to have become somewhat less > innocuous: > > ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=38669679 > ad0: FAILURE - already active DMA on this device > ad0: setting up DMA failed > g_vfs_done():ad0s1e[READ(offset=18188230656, length=2048)]error = 5 > cvs update: in directory modules/tx: > cvs [update aborted]: cannot read CVS/Repository: Input/output error > > In the past, this appeared to be a symptom of long and unexplained delays in > Parallel's ATA -> image file operation, but were not harmful as the retried > operation succeeded. However, it seems that this is no longer the case, with > errors exposed to higher levels of the file system. Do you have any > suggestions? > I see this eror on real hardware (PATA DVD hooked to nVidia nForce MCP61 UDMA133 controller) with a kernel generated today: Apr 17 13:11:07 peedub kernel: acd0: TIMEOUT - READ_BIG retrying (1 retry left) Apr 17 13:11:07 peedub kernel: acd0: FAILURE - already active DMA on this device Apr 17 13:11:07 peedub kernel: acd0: setting up DMA failed Apr 17 13:11:07 peedub kernel: g_vfs_done():acd0[READ(offset=4315742208, length=65536)]error = 5 Apr 17 13:11:07 peedub kernel: g_vfs_done():acd0[READ(offset=29360128, length=65536)]error = 5 Apr 17 13:11:07 peedub kernel: g_vfs_done():acd0[READ(offset=33554432, length=65536)]error = 5 Apr 17 13:11:41 peedub kernel: g_vfs_done():acd0[READ(offset=1103101952, length=65536)]error = 5 Apr 17 13:12:08 peedub kernel: g_vfs_done():acd0[READ(offset=2172649472, length=65536)]error = 5 Apr 17 13:12:42 peedub kernel: g_vfs_done():acd0[READ(offset=3242196992, length=65536)]error = 5 Apr 17 13:13:15 peedub kernel: g_vfs_done():acd0[READ(offset=4311744512, length=65536)]error = 5 Apr 17 13:13:15 peedub kernel: g_vfs_done():acd0[READ(offset=563200, length=2048)]error = 5 It almost looks like the driver isn't cleaning up pending DMAs when a hard error occurs. --- Gary Jennejohn