From owner-freebsd-current@FreeBSD.ORG Tue Mar 8 09:59:03 2005 Return-Path: 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 4DAAD16A4CE; Tue, 8 Mar 2005 09:59:03 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBB1D43D31; Tue, 8 Mar 2005 09:59:02 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id j289x2d4002059; Tue, 8 Mar 2005 04:59:02 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)j289x2xR002056; Tue, 8 Mar 2005 04:59:02 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Tue, 8 Mar 2005 04:59:01 -0500 (EST) From: Jeff Roberson To: Jeremie Le Hen In-Reply-To: <20050308095302.GL94451@obiwan.tataz.chchile.org> Message-ID: <20050308045604.B20708@mail.chesapeake.net> References: <20050308095302.GL94451@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: jeff@FreeBSD.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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2005 09:59:03 -0000 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. > > /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. > > Regards, > -- > Jeremie Le Hen > jeremie at le-hen dot org >