current panic igmp related ?

From: Poul-Henning Kamp <phk_at_phk.freebsd.dk>
Date: Tue, 07 Dec 2004 12:47:35 +0100
Timecounters tick every 1.000 msec
panic: mtx_lock() of spin mutex (null) _at_ ../../../netinet/igmp.c:431
cpuid = 0
KDB: enter: panic
[thread pid 37 tid 100013 ]
Stopped at      kdb_enter+0x2c: leave   
db> trace
Tracing pid 37 tid 100013 td 0xc3485480
kdb_enter(c06d85e0,100,c3485480,1af,c06e0fec) at kdb_enter+0x2c
panic(c06d7ac5,0,c06e0fec,1af,c0713fc4) at panic+0x17f
_mtx_lock_flags(c0738740,0,c06e0fec,1af,e4c97cc8) at _mtx_lock_flags+0x82
igmp_slowtimo(e,0,e4c97cf4,c050683a,0) at igmp_slowtimo+0x19
pfslowtimo(0,27,0,2,2) at pfslowtimo+0x66
softclock(0,0,0,c34d07e0,0) at softclock+0x10a
ithread_loop(c34cf100,e4c97d48,c34cf100,c04e9200,0) at ithread_loop+0x18e
fork_exit(c04e9200,c34cf100,e4c97d48) at fork_exit+0x7e
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe4c97d7c, ebp = 0 ---
db> 

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
Received on Tue Dec 07 2004 - 10:47:38 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:24 UTC