From owner-freebsd-current@FreeBSD.ORG  Tue Mar  8 10:01:34 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0607016A4CE; Tue,  8 Mar 2005 10:01:34 +0000 (GMT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id CE5BC43D53; Tue,  8 Mar 2005 10:01:33 +0000 (GMT)
	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id B20AF5C9CA; Tue,  8 Mar 2005 02:01:31 -0800 (PST)
Date: Tue, 8 Mar 2005 11:01:31 +0100
From: Maxime Henrion <mux@FreeBSD.org>
To: Jeff Roberson <jroberson@chesapeake.net>
Message-ID: <20050308100131.GC31320@elvis.mu.org>
References: <20050308095302.GL94451@obiwan.tataz.chchile.org>
	<20050308045604.B20708@mail.chesapeake.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050308045604.B20708@mail.chesapeake.net>
User-Agent: Mutt/1.4.2.1i
cc: jeff@FreeBSD.org
cc: Jeremie Le Hen <jeremie@le-hen.org>
cc: current@FreeBSD.org
Subject: Re: panic: ufs_dirbad: bad dir
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2005 10:01:34 -0000

Jeff Roberson wrote:
> On Tue, 8 Mar 2005, Jeremie Le Hen wrote:
> 
> > Hi,
> >
> > with a UP -CURRENT from sunday, I stressed my system and I got the
> > following panic.  I know Jeff has just commited something in vfs_bio.c
> > but I'm not sure this is related, so in doubt, I report it before
> > upgrading.  This is hand-written, so I didn't reported numeric value,
> > but I have a crash dump.  Please contact me off-list if you need it.
> 
> Unfortunately, the panic you transcribed is a secondary panic.  I'd like
> to see the primary stack, but it sounds like that isn't available.  I'm
> going to commit some more major fixes in a few days which address unsafe
> code at vnode teardown time.  Hopefully this may have some effect.

Isn't that the first panic?
	panic: bremfree: buffer 0xc9304af0 not on a queue

> > /usr: bad dir ino 413567 at offset 0: mangled entry
> > panic: ufs_dirbad: bad dir
> > KDB: stack-backtrace:
> > panic: bremfree: buffer 0xc9304af0 not on a queue
> > KBD: enter: panic
> > [ thread pid 45 tid 100062 ]
> > Stopped at       kbd_enter+0x30: leave
> > db> trace
> > Tracing pid 45 tid 100062 td 0xc18fb320
> > kbd_enter()
> > panic()
> > bremfree()
> > getblk()
> > breadn()
> > bread()
> > ffs_update()
> > ufs_inactive()
> > VOP_INACTIVE_APV()
> > vput()
> > handle_workitem_remove()
> > process_worklist_item()
> > softdep_process_worklist()
> > sched_sync()
> > fork_exit()
> > fork_trampoline()
> > --- trap0x1, eip = 0, esp = 0xd50d2d7c, ebp = 0 ---
> >
> > My dmesg(8) as well as my kernel configuration files are attached.

Cheers,
Maxime