From owner-freebsd-stable Tue Sep 19 20:43:40 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 5DFE137B43F; Tue, 19 Sep 2000 20:43:36 -0700 (PDT) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA05361; Tue, 19 Sep 2000 23:43:10 -0400 (EDT) Date: Tue, 19 Sep 2000 23:43:10 -0400 (EDT) From: Daniel Eischen To: Andy@silverbrook.com.au Cc: Brad Knowles , stable@FreeBSD.ORG, "Brandon D. Valentine" , gibbs@FreeBSD.ORG Subject: Re: MFC of ahc driver updates (long-ish) In-Reply-To: <200009200330.OAA24867@bebop.lan.silverbrook.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000 Andy@silverbrook.com.au wrote: > I've run tests with the disks striped & mirrored, and it appears to be > a problem with vinum's RAID 5. I can't crash it in a non-RAID 5 > config. The symptons appear similar to kern/21148 and I've got two > crash dumps now that point fingers at RAID 5 request buffer corruption > (at completion time ... I've never lost data, just time :) Just another datapoint, I've got a SuperMicro DL3 board with builtin 7892. With 4.1-release, things work, but under load, I can get the system to hang or go into an endless aborting SCB/resetting SCSI bus loop that forces a power cycle. With 4.1-stable, it doesn't even boot. I get continuous "ahc0: detected spurious interrupt" messages that prevent the system from booting. Brandon, I'll take those patches if you've still got them lying around. If not, I'll try to make them myself or try to get the latest -current aic7xxx driver to work. Thanks, -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message