Deadlock problems with 'kill PID' on CURRENT

[Robert Watson]

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 at fledge.watson.org      Principal Research Scientist, McAfee Research