From owner-freebsd-stable  Sun Feb 18 12: 8:11 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67])
	by hub.freebsd.org (Postfix) with ESMTP id EDC1637B67D
	for <stable@FreeBSD.ORG>; Sun, 18 Feb 2001 12:08:08 -0800 (PST)
Received: (from dillon@localhost)
	by earth.backplane.com (8.11.2/8.9.3) id f1IK87k31550;
	Sun, 18 Feb 2001 12:08:07 -0800 (PST)
	(envelope-from dillon)
Date: Sun, 18 Feb 2001 12:08:07 -0800 (PST)
From: Matt Dillon <dillon@earth.backplane.com>
Message-Id: <200102182008.f1IK87k31550@earth.backplane.com>
To: Mike Meyer <mwm@mired.org>
Cc: stable@FreeBSD.ORG
Subject: Re: Suggestions for diagnosing lockups
References: <14991.58225.783986.487533@guru.mired.org>
	<200102181936.f1IJanm31380@earth.backplane.com> <14992.9931.334001.521780@guru.mired.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:
:Matt Dillon <dillon@earth.backplane.com> types:
:>     I also recommend using 4.2-Stable rather then 4.2-Release.  4.2-Release
:>     has a number of bugs and security holes relative to stable.
:
:I upgraded to -Stable before sending the question, hoping that would
:solve the problem. I recall there being some strange problems with the
:ahc drivers in current about the time that 4.2-RELEASE, and thought
:this might be related.
:
:	<mike

    I dunno. I think we won't know until you manage to get the broken
    into DDB.  From there you should be able to do a 'trace' and a 'ps'
    to hopefully see where things have locked up.  If you have setup a 
    dump device & swap, you should also be able to 'panic' the kernel from DDB
    and get a core dump.

						-Matt



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