From owner-freebsd-bugs Tue Nov 28 10: 0: 9 2000 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BBE5E37B404 for ; Tue, 28 Nov 2000 10:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id eASI03i24567; Tue, 28 Nov 2000 10:00:03 -0800 (PST) (envelope-from gnats) Date: Tue, 28 Nov 2000 10:00:03 -0800 (PST) Message-Id: <200011281800.eASI03i24567@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Carlos Amengual Subject: Re: kern/22086: DMA errors during intensive disk activity on vinum volume Reply-To: Carlos Amengual Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/22086; it has been noted by GNATS. From: Carlos Amengual To: freebsd-gnats-submit@FreeBSD.org, rasmith@aristotle.tamu.edu Cc: Subject: Re: kern/22086: DMA errors during intensive disk activity on vinum volume Date: Tue, 28 Nov 2000 18:52:43 +0100 I found the same problem on a 4.2-RELEASE system: Vinum configuration: drive idea device /dev/ad0s1e drive ideb device /dev/ad2s1f drive idec device /dev/ad4s1f volume raid5a plex org raid5 512k sd length 0 drive idea sd length 0 drive ideb sd length 0 drive idec The error messages: Nov 27 22:24:43 vega /kernel: ata0-master: zero length DMA transfer attempted Nov 27 22:25:06 vega /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Nov 27 22:25:06 vega /kernel: ata0: resetting devices .. done Nov 27 22:25:06 vega /kernel: ata0-master: zero length DMA transfer attempted Nov 27 22:25:06 vega /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Nov 27 22:25:06 vega /kernel: ata0: resetting devices .. done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message