Re: locking against myself in sched_nextlwp()

[Michael Lorenz <macallan%netbsd.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On May 20, 2008, at 20:48, Andrew Doran wrote:

> On Tue, May 20, 2008 at 06:52:44PM -0400, Michael Lorenz wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hello,
> >
> > 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
> > anywhere?
>
> I filed this today:
>
> kern/38707: scheduler related deadlock during build.sh

Sounds like you hit it too.

> > It usually happens a few minutes into build.sh -j4 distribution.
>
> Did you get LOCKDEBUG output from it?

Yes.

> x/i or gdb "info line *0xfoo" on the address from "last locked"  
> would be useful.

Can't really do that - USB keyboard and no serial ports.
Someone(tm) should fix ukbd polling...

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBSDN0NcpnzkX8Yg2nAQJZJwf/bOuFZR5MBHUuvJrO7hE8vslph0LI8Uhq
/4yWd8ViydihuWp/Ce990QCSfVK7yNcnj/R7g27aZppAUWi8G3pJkXRnFTqzH28q
K3CW2XuG+1fnm4RvgV9amEdYAiaid/HKCIkpQ0GRZTN7qbcGNoTc2dPYTM/9sHSu
doJNdGWxm3fiB3sITvDWecY+dynyAXGUujn0pm2ode0T2NMOJP5QE/MxuUSwrbqX
1Yt7qDqN4EnO9XMFZ8XZ0NgyhpeOlUxc31snmtHDLCNrJb22o4HDQWN/h5E5Iu4i
Y4BCk58vmUVMP2Nti5kNB/LNddSmORGuUpabgoZCP8zCUxJoLdNZ5Q==
=lUuv
-----END PGP SIGNATURE-----