From owner-freebsd-bugs Tue Nov 28 11:16:45 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0B24A37B400 for ; Tue, 28 Nov 2000 11:16:41 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA00377; Tue, 28 Nov 2000 20:17:37 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200011281917.UAA00377@freebsd.dk> Subject: Re: kern/22086: DMA errors during intensive disk activity on vinum volume In-Reply-To: <200011281800.eASI03i24567@freefall.freebsd.org> from Carlos Amengual at "Nov 28, 2000 10:00:03 am" To: webmaster@healthnet-sl.es (Carlos Amengual) Date: Tue, 28 Nov 2000 20:17:36 +0100 (CET) Cc: freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Carlos Amengual wrote: > 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 This is an old problem with vinum, somehow vinum manage to trash the ad_request struct between where the ata drives makes it in ad_strategy and when it actually gets used later.. I thought this was fixed at least in -current long ago, but apparently this was either not backported to -stable or the fix was not good enough. I'm sure Greg will tell you its an ATA problem though :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message