From owner-freebsd-current  Tue Nov  5  6:56:12 2002
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 BBFC737B401
	for <current@FreeBSD.ORG>; Tue,  5 Nov 2002 06:56:11 -0800 (PST)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3408E43E3B
	for <current@FreeBSD.ORG>; Tue,  5 Nov 2002 06:56:07 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA09355;
	Tue, 5 Nov 2002 09:56:06 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id gA5Eta435802;
	Tue, 5 Nov 2002 09:55:36 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15815.56296.463941.374808@grasshopper.cs.duke.edu>
Date: Tue, 5 Nov 2002 09:55:36 -0500 (EST)
To: "Joel M. Baldwin" <qumqats@outel.org>
Cc: current@FreeBSD.ORG
Subject: Re: Why is my -current system Hard Locking?
In-Reply-To: <149469335.1036439809@[192.168.1.20]>
References: <149469335.1036439809@[192.168.1.20]>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


Joel M. Baldwin writes:

<...>
 > don't think this is related to the X FP problem ( although I am
 > running X11 ).  There have been many times when I'd walk in the
<...>
 > options         DDB                     #Enable the kernel debugger
<...>

Its likley you are panic'ing in X, and the system is waiting at the
ddb prompt.  But you can't see it or do anything, since X has control
of the graphics and kbd, so it looks like the machine is frozen.

Try adding options DDB_UNATTENDED  to your config.  Or just do
sysctl  debug.debugger_on_panic=0

Both of these have the same effect: they will prevent ddb from stopping
the panic.  Make sure you have a dump device setup to capture a
crashdump.

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message