Date: Mon, 15 Nov 2004 08:57:42 -0800 From: Peter Wemm <peter@wemm.org> To: freebsd-current@freebsd.org Cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT Message-ID: <200411150857.42423.peter@wemm.org> In-Reply-To: <Pine.NEB.3.96L.1041115133457.80435A-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1041115133457.80435A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 15 November 2004 05:35 am, Robert Watson wrote: > On Mon, 15 Nov 2004, Martin Blapp wrote: > > > syscons is typically a sign that some thread holding Giant is > > > spinning, or that Giant has been leaked. Alternatively, some > > > other lock is leaked, and a thread with Giant waits on that lock. > > > You may be able to get into DDB using the serial console as it > > > doesn't require Giant (or you might not). > > > > I was not able to get into DDB over serial console. Sorry for not > > saying this exactly. Hardlock. > > Any chance that any of the boxes has an NMI button? I had this problem too BTW, but it didn't prevent DDB. Once named or rndc got stuck, trying to kill them was Really Bad(TM). Both use libpthread. The programs were stuck in "runnable" state according to CTRL-T (siginfo). No, I haven't looked closer. That system was built about when the last round of libpthread turmoil was happening. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200411150857.42423.peter>