From owner-freebsd-current Tue Apr 1 02:16:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA22639 for current-outgoing; Tue, 1 Apr 1997 02:16:46 -0800 (PST) Received: from mailbox.uq.edu.au (zzshocki.slip.cc.uq.edu.au [130.102.221.173]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA22633 for ; Tue, 1 Apr 1997 02:16:39 -0800 (PST) Received: from bloop.craftncomp.com (localhost.craftncomp.com [127.0.0.1]) by mailbox.uq.edu.au (8.8.5/8.6.12) with ESMTP id UAA28966; Tue, 1 Apr 1997 20:09:58 +1000 (EST) Message-Id: <199704011009.UAA28966@mailbox.uq.edu.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: toj@gorilla.net cc: current@freebsd.org, toor@dyson.net Subject: Re: Current is crashing X In-reply-to: Your message of "Tue, 01 Apr 1997 01:18:47 CST." <19970401011847.31693@peeper.jackson.org> From: shocking@mailbox.uq.edu.au Reply-To: shocking@mailbox.uq.edu.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Apr 1997 20:09:56 +1000 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Running current on a p5/100. Kernel built from ctm#2824 seemed to have no > problems. Got ctm#2827 today and since there had been some kernel source > changes, rebuilt the kernel after a successful make on the system. When > I went to start X the box crashes and does an auto reboot. > > CTM having its latency, I looked for anything similar, didn't see any, and > wonder if this is some fluke. Any others see this? Yup. I'm getting a panic with "lockmgr: locking against myself", which is tracked down to /sys/sys/lock.c. It occurs when the X server gets a client, i.e. it happens when firing up startx or having xdm start X, but not when running the X server by itself (/usr/X11R6/bin/XF86_whatever). I can get a traceback, but the offending machine is at work at the moment. This happened between src-cur 2826 & src-cur 2827 (i.e. it did not exist at 2826). Stephen