From owner-freebsd-current@FreeBSD.ORG Wed Apr 23 14:58:24 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 73C06106566B; Wed, 23 Apr 2008 14:58:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3301B8FC22; Wed, 23 Apr 2008 14:58:24 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id C408646B7F; Wed, 23 Apr 2008 10:58:23 -0400 (EDT) Date: Wed, 23 Apr 2008 15:58:23 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: sos@FreeBSD.org In-Reply-To: <20080417144424.D71628@fledge.watson.org> Message-ID: <20080423155744.D64388@fledge.watson.org> References: <20080417144424.D71628@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: Re: ATA problem in Parallels: warnings -> failures X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 23 Apr 2008 14:58:24 -0000 On Thu, 17 Apr 2008, Robert Watson wrote: > 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? Your recent commits appear now to have resolved this problem. I'm still getting the usual TIMEOUT's for read and write DMA that I always get in Parallels, but no more corrupted UFS, as far as I can tell, anyway. :-) Thanks, Robert N M Watson Computer Laboratory University of Cambridge