From owner-freebsd-current Mon Mar 12 14:16:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 1F9AC37B719 for ; Mon, 12 Mar 2001 14:16:50 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA43517; Mon, 12 Mar 2001 23:16:46 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Mikhail Teterin Cc: current@freebsd.org Subject: Re: panic trying to play Civillization (with trace, etc.) References: <200103120526.AAA09072@mail.virtual-estates.net> From: Dag-Erling Smorgrav Date: 12 Mar 2001 23:16:45 +0100 In-Reply-To: Mikhail Teterin's message of "Mon, 12 Mar 2001 00:26:41 -0500 (EST)" Message-ID: Lines: 36 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin writes: > > If you can, please reproduce the panic on a kernel compiled with the > > INVARIANTS, INVARIANT_SUPPORT and WITNESS options. > Well, with this options on, the machine does not crash, but the > program segfaults on startup: The trace you're showing looks like it's from a shell script that starts civctp. I need to see the trace from the civctp binary itself. > lock order reversal > 1st lockmgr interlock last acquired @ ../../kern/kern_lock.c:239 > 2nd 0xcefa0520 process lock @ ../../kern/kern_sig.c:183 > 3rd 0xc1029f80 lockmgr interlock @ ../../kern/kern_lock.c:560 Haven't seen this one before... If it's reproducible, could you do the following: 1) recompile your kernel with WITNESS_DDB 2) hook up a serial console and boot with '-h' in /boot.config 3) provoke the reversal, then get the output from 'trace', 'show mutex' and 'show witness' at the DDB prompt 4) type 'continue' to exit DDB and continue running normally. > lock order reversal > 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625 > 2nd 0xc0419680 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:939 > 3rd 0xcefb986c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:948 This is a known (and probably benign) bug. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message