[issue2072] Fatal trap 12: stopped at lwkt_send_ipiq3

Rumko (via DragonFly issue tracker) sinknull at leaf.dragonflybsd.org
Mon May 16 21:13:05 PDT 2011


Rumko <rumcic at gmail.com> added the comment:

With latest master the trace is a tad different so reposting:
LWKT_WAIT_IPIQ WARNING! 0 wait 0 (-1)
panic: LWKT_WAIT_IPIQ
cpuid = 0
Trace beginning at frame 0xd2e83ca0
panic(ffffffff,0,c0469a5b,d2e83cd4,c0535474) at panic+0x198
panic(c0469a5b,0,0,ffffffff,297) at panic+0x198
lwkt_wait_ipiq(deadc0de,1,c3b9ed60,0,c0535460) at lwkt_wait_ipiq+0x99
callout_stop(c3b9ed60,c01ecb95,d85a8960,d3550aa8,c0535460) at callout_stop+0x108
callout_reset(c3b9ed60,1,c01ecb9b,d3550aa8,fff77842) at callout_reset+0x6f
filt_timerexpire(d3550aa8,0,0,c0535474,d2e431b0) at filt_timerexpire+0x8a
softclock_handler(c0535460,0,0,0,0) at softclock_handler+0x13a
lwkt_exit() at lwkt_exit
Debugger("panic")

CPU0 stopping CPUs: 0x00000002
 stopped
Stopped at      Debugger+0x3f:  movb    $0,in_Debugger.4931
db>

----------
status: unread -> chatting

_____________________________________________________
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue2072>
_____________________________________________________






More information about the Bugs mailing list