On 11/23/10 15:34, der Mouse wrote:
Looking at top: [...]
Anything I could look at to find out more?
I'd probably start by breaking into ddb on the console and getting a
stack trace of those processes. I'd guess they probably are stuck
waiting for a lock of one sort or another and this should point you
towards which lock is in question. Alternatively, they could be in
userland, in which case the problem is most likely that they're not
getting scheduled, and you should turn your attention to the scheduler
(most likely its locking, since that's what you've been messing with).
Hmm. Well, my locking code is not running here, so this is more or less
pure stock NetBSD-current.
Breaking in to ddb is easy, though. But I'll have to be careful there,
since ddb is very sensitive to any kind of error happening inside ddb,
which will break everything for good. Getting a stack trace is usually
one of those things, so I only get one shot at a stack trace before I
need to reboot.
But I'll see what I can figure out that way. Thanks.
(Oh, and mouse, your MTA is broken. It don't accept mail from me. ;-) )