[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: locking against myself in sched_nextlwp()
On Tue, May 20, 2008 at 06:52:44PM -0400, Michael Lorenz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> a kernel built from yesterday's sources panics reproducably in
> sched_nextlwp() - the lock is a spinlock, the machine is a dual G4,
> the scheduler is M2. Before I dig deeper - does that ring a bell
I filed this today:
kern/38707: scheduler related deadlock during build.sh
> It usually happens a few minutes into build.sh -j4 distribution.
Did you get LOCKDEBUG output from it? x/i or gdb "info line *0xfoo" on the
address from "last locked" would be useful.
Main Index |
Thread Index |