From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 18:04:45 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 0401D16A4CE for ; Sat, 22 Jan 2005 18:04:45 +0000 (GMT) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id A16BF43D31 for ; Sat, 22 Jan 2005 18:04:44 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 7BE2A173482 for ; Sat, 22 Jan 2005 19:04:43 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id C3536407C; Sat, 22 Jan 2005 19:04:33 +0100 (CET) Date: Sat, 22 Jan 2005 19:04:33 +0100 From: Jeremie Le Hen To: freebsd-current@freebsd.org Message-ID: <20050122180433.GH36660@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: panic: mutex Giant not owned (ffs_vnops.c) 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: Sat, 22 Jan 2005 18:04:45 -0000 Hi, on a very -CURRENT system, I cannot use a vnode-based mdconfig(8) any longer, the following panic (sorry but this is hand-written) occured when I performed this command : %%% # mdconfig -a -t vnode -f /boot/profile/home panic: mutex Giant not owned at ../../../ufs/ffs/ffs_vnops.c:350 KDB: stack backtrace: kdb_backtrace() panic() _mtx_assert() ffs_read() VOP_READ_AP() mdstart_vnode() md_kthread() fork_exit() fork_trampoline() -- trap 0x1, eip = 0, ... db> show alllocks db> %%% I think I can get a kernel dump if needed (doadump() seems to work). All I can say is that I'm pretty sure this was working around Christmas. IIRC, I tried various kernel dates and the earliest one (2004.01.01) is panic()'ing as well, but I'm would not bet too much on it (I had a few unwanted kernel source changes when I tried). Note that I'm sending this report now because I made a `cvs up -C' so I *know* my kernel tree is clean today. Please, don't hesitate to ask me for deeper debugging informations. Regards, -- Jeremie Le Hen jeremie@le-hen.org