From owner-freebsd-current@FreeBSD.ORG Wed Oct 20 09:01:00 2004 Return-Path: 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 1C0C516A4CE for ; Wed, 20 Oct 2004 09:01:00 +0000 (GMT) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FA0A43D31 for ; Wed, 20 Oct 2004 09:00:58 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) i9K90tgF003425 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 20 Oct 2004 19:00:57 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])i9K90sxP082633; Wed, 20 Oct 2004 19:00:55 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)i9K90s0p082632; Wed, 20 Oct 2004 19:00:54 +1000 (EST) (envelope-from pjeremy) Date: Wed, 20 Oct 2004 19:00:54 +1000 From: Peter Jeremy To: Randy Bush Message-ID: <20041020090054.GA79646@cirb503493.alcatel.com.au> References: <16757.28156.361400.647815@ran.psg.com> <20041019212148.GB93330@xor.obsecurity.org> <16757.35688.795976.719745@ran.psg.com> <20041019215625.GE83510@dan.emsphone.com> <16757.39060.602700.402490@ran.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16757.39060.602700.402490@ran.psg.com> User-Agent: Mutt/1.4.2i cc: FreeBSD Current Subject: Re: multi-user startup failure Pre-seeding PRNG: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2004 09:01:00 -0000 On Tue, 2004-Oct-19 15:43:32 -0700, Randy Bush wrote: >> Can you break into the debugger via Ctrl-Alt-ESC? > >nope If it's convenient sometime, try Ctrl-Alt-ESC and leave it for some time (½-1 hr - eg over lunch or dinner) and see if anything happens. I've seen a situation where an interrupt storm made the system look non-responsive but it was actually just very slow. (Though this was in 4.x and the interrupt watchdog in 5.x should trap this case). -- Peter Jeremy