locking against myself in sched_nextlwp()

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

-----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?
It usually happens a few minutes into build.sh -j4 distribution.

have fun
Michael

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

iQEVAwUBSDNWPMpnzkX8Yg2nAQJSMggAtPqfNCZLVayGK6xawnLdkCBTG/3lzxlf
0ZohFuxqA0ByW4xxmEEwJIEBjYJuoreUJaxa0e2CHG6A3xqCAQmIRk01F9ZcUzsY
V15P9Dr/QJaPxHWKbhdf4PlwOWw+D9QWK9y6vmVOCdDdIwE+yQj6k/RwsxMa0JJK
zsAvpZWhhB0s4hDSnl7QBcOW6s9fKCX0gRk6tm9EuCEin8GEOwmCqSm14VnRkIn1
YvDXhZ7rNbzJ8DXe/ftaPMuoqJRrRm3FOeYyEkVJH7vGqmHwPnowEjHb87TgZ4a7
YOGirUVgWzKUeSJe/PMdkFSVmbBmnELsG5e3xQae+2u14nU0ahFCCw==
=Ktm9
-----END PGP SIGNATURE-----