From owner-freebsd-current Mon Mar 12 15:38:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 5E18437B728 for ; Mon, 12 Mar 2001 15:38:26 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2CNbjA93572; Mon, 12 Mar 2001 15:37:46 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 12 Mar 2001 15:37:29 -0800 (PST) From: John Baldwin To: Dag-Erling Smorgrav Subject: Re: panic trying to play Civillization (with trace, etc.) Cc: current@FreeBSD.org, Mikhail Teterin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Mar-01 Dag-Erling Smorgrav wrote: > 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: It's stupidness due to proctree and allproc locks being backed by lockmgr I think. I'm waiting on looking at this one until proctree and allproc are converted to sx locks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message