From owner-freebsd-current Sun Apr 2 6:41:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id E450D37B6AC for ; Sun, 2 Apr 2000 06:41:46 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id D5B742CE69; Sun, 2 Apr 2000 15:41:39 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id B2B3B1C562B; Sun, 2 Apr 2000 15:39:35 +0200 (EET) Date: Sun, 2 Apr 2000 15:39:35 +0200 From: Vallo Kallaste To: Bernd Walter Cc: Greg Lehey , Soren Schmidt , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402153935.A64937@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402015016.C24134@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 01:50:16AM +0200 Organization: =?UTF-8?Q?AS_Matti_B=C3=BCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter wrote: > > Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on > > 7x 200M disks - it does not hang for me since a long time. > > The latest current I tested R5 well is from 19th March on alpha. That's shortly > > before PHKs changes - I don't beleave that it introduced something new. > > The only problem with R5 I know of is parity corruption because of a bug in > > lockrange() for which I've already send you a fix. Even it is a general bug it > > seems only to cause problems together with softupdates. > > Ops - I oversaw that this happened with a recent current. > The best I can say is that it is likely that it happened after the 19th March. I got now crash under 4.0-RELEASE, with syncer and bufdaemon in the same vrlock state, pax in flswait. I was in single-user mode using pax to extract usr archive to newly created raid5 volume. I'm using NFS mount with flags -3i -r16384 -w16384 over 100Mbit full-duplex link, fxp driver on both sides. Note that I'm using stripe unit size 512k now, otherwise same. Here's handcopy of DDB messages: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc1e03ef4 stack pointer = 0x10:0xc0244a84 frame pointer = 0x10:0xc0244aa0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio kernel: type 12 trap, code=0 Stopped at complete_rqe+0x18: movl 0x4(%eax),%edx db> trace complete_rqe at complete_rqe+0x18 biodone at biodone+0x53 ad_interrupt at ad_interrupt+0x2e2 ata_intr at ata_intr+0xca Xresume15() at Xresume15+0x2b --- interrupt, eip = 0xc020e5ae, esp = 0xc0244b54, ebp = 0 --- default_halt() at default_halt+0x2 I hook up serial console to get full traceback next time, but I don't have any knowledge for further analysis. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message