From owner-freebsd-stable@FreeBSD.ORG  Thu Nov 17 08:54:55 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CB52D16A41F
	for <freebsd-stable@freebsd.org>; Thu, 17 Nov 2005 08:54:55 +0000 (GMT)
	(envelope-from PeterJeremy@optushome.com.au)
Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au
	[211.29.132.198])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E7D843D45
	for <freebsd-stable@freebsd.org>; Thu, 17 Nov 2005 08:54:54 +0000 (GMT)
	(envelope-from PeterJeremy@optushome.com.au)
Received: from cirb503493.alcatel.com.au
	(c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236])
	by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id
	jAH8sqJb014590
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 17 Nov 2005 19:54:53 +1100
Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])
	by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id
	jAH8sqHh095144; Thu, 17 Nov 2005 19:54:52 +1100 (EST)
	(envelope-from pjeremy@cirb503493.alcatel.com.au)
Received: (from pjeremy@localhost)
	by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jAH8sqI4095143; 
	Thu, 17 Nov 2005 19:54:52 +1100 (EST) (envelope-from pjeremy)
Date: Thu, 17 Nov 2005 19:54:51 +1100
From: Peter Jeremy <PeterJeremy@optushome.com.au>
To: Rob <spamrefuse@yahoo.com>
Message-ID: <20051117085451.GN39882@cirb503493.alcatel.com.au>
References: <20051117080003.1088.qmail@web36214.mail.mud.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051117080003.1088.qmail@web36214.mail.mud.yahoo.com>
User-Agent: Mutt/1.4.2.1i
X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc
Cc: freebsd-stable@freebsd.org
Subject: Re: Swapfile problem in 6?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Nov 2005 08:54:55 -0000

On Thu, 2005-Nov-17 00:00:03 -0800, Rob wrote:
> The only way I know of how to trigger the deadlock, is to compile
> a new kernel and the 'linking kernel' stage will lock-up the PC.
> With a regular kernel, this takes 2.5 hours until deadlock, but with
> a fully equipped debug kernel it takes about 8 hours....

When the first deadlock occurs, you have a fully populated set of kernel
objects (though possibly some of them are in the buffer case rather than
on disk).  You should be able to quickly reproduce the panic by running:
# cd /usr/obj/usr/src/sys/<<KERNEL>>
# make

(Adjust the directory to suit your config name and MAKEOBJDIRPREFIX).

Alternatively, check out the following lines in /usr/src/Makefile.inc1
#       -DNO_KERNELCONFIG do not run config in ${MAKE} buildkernel
#       -DNO_KERNELCLEAN do not run ${MAKE} clean in ${MAKE} buildkernel
#       -DNO_KERNELDEPEND do not run ${MAKE} depend in ${MAKE} buildkernel

-- 
Peter Jeremy