Date: Mon, 15 Nov 2004 12:50:18 +0000 (GMT) From: Robert Watson <rwatson@freebsd.org> To: Martin Blapp <mb@imp.ch> Cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT Message-ID: <Pine.NEB.3.96L.1041115124708.66223J-100000@fledge.watson.org> In-Reply-To: <20041115125640.D53544@cvs.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 15 Nov 2004, Martin Blapp wrote: > and boom, it deadlocked and I was not able to get into DDB. Are you able to get into DDB using a serial console? Not getting in via 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). But that would be a useful first step. Are you able to reproduce this problem with INVARIANTS and/or WITNESS compiled in, btw? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041115124708.66223J-100000>