At 16:50 Uhr +1100 7.1.2003, matthew green wrote:
   >BTW, do you have ddb configured?  you really should.  everyone who
   >runs SMP kernels should probably have DDB and it wouldn't be bad to
   >also turn on the LOCKDEBUG option to check that simplelock's are
   >correctly used ...
   
   After patching sparc/locore.s, the ss10 comes up multi-user, but eventually
   locks up. Breaking into ddb, I get an endless stream of
   
   simple_lock: locking against myself
   lock: 0xf023d4e4, currently at: /usr/src/sys/arch/sparc/sparc/cpu.c:758
   on cpu 0
   last locked: /usr/src/sys/arch/sparc/sparc/cpu.c:667
   last unlocked: /usr/src/sys/arch/sparc/sparc/cpu.c:745


OK, in cpu.c, find pause_mp_cpus() and comment the calls to LOCK_XPMSG()
and UNLOCK_XPMSG().  you'll notice the "XXX" message there...  anyway,
that changes the failure mode...but should let you get further at least
into DDB, if not out of it again.


.mrg.