Subject: re: couldn't ping cpus
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: matthew green <mrg@eterna.com.au>
List: port-sparc
Date: 01/20/2003 10:45:46
Here his what I have on console:
xcall(cpu0, f00078dc): couldn't ping cpus: cpu1
simple_lock: locking against myself (this is probably the cause of the lookup
without lockdebug)
lock: 0xf01bbb88, currently at: sys_generic.c:996 on cpu0
last locked: kern_sync.c:659
last unlocked: kern_sync.c:637
logwakeup+0x28
printf+0xa4
xcall+0x328
sched_wakeup+0x1e0
wakeup+0x84
lwp_exit2+0x64
exit2+0x64
switchexit+0x3c
cpu_exit+0x120
exit1+0x128
sys_exit+0x2c
this looks like the xcall() calls printf() which wakes up the scheduler
because of the log device bug that pk fixed a couple of days ago? please
update and see if it still fails?
.mrg.