Re: protocol timer running before protocol is fully initialized (again) (was re: panic: mtx_lock() of spin mutex ...)

From: Ruslan Ermilov <ru_at_FreeBSD.org>
Date: Thu, 9 Dec 2004 22:33:34 +0200
Hi Max,

On Thu, Dec 09, 2004 at 12:34:08PM +0100, Max Laier wrote:
[...]
> in ip_input() - that's not good! Can you send me the trace? I was under the 
> impression that net send and esp. reveice is off during this part of the 
> initialization. Crashing ip_input() would question that assumption.
> 
I don't have a serial attached to this notebook (all my
serial cables are at work), so this is hand-copied from
the screen:

Timecounters tick every 1.000 msec
panic: mtx_lock() of spin mutex (null) _at_ /usr/src/sys/netinet/ip_input.c:1096
KDB: enter: panic
[thread pid 27 tid 100001 ]
Stopped at	kdb_enter+0x32: leal	0(%esi),%esi
db> where
Tracing pid 27 tid 100001 td 0xc1219180
kdb_enter(...) at kdb_enter+0x32
panic(...) at panic+0x14d
_mtx_lock_flags(...) at _mtx_lock_flags+0x114
ip_slowtimo(...) at ip_slowtimo+0x2f
pfslowtimo(...) at pfslowtimo+0x82
softclock(...) at softclock+0x12f
ithread_loop(...) at ithread_loop+0x210
fork_exit(...) at fork_exit+0xa9
fork_trampoline(...) at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xcdbbbd7c, ebp = 0 ---

PID 27 is "[CPU 0] swi4: clock sio


Cheers,
-- 
Ruslan Ermilov
ru_at_FreeBSD.org
FreeBSD committer

Received on Thu Dec 09 2004 - 19:33:38 UTC

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