Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Dec 2004 02:31:19 +0000 (GMT)
From:      Robert Watson <rwatson@freebsd.org>
To:        Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc:        mlaier@freebsd.org
Subject:   protocol timer running before protocol is fully initialized (again) (was re: panic:  mtx_lock() of spin mutex ...)
Message-ID:  <Pine.NEB.3.96L.1041209023008.44319C-100000@fledge.watson.org>
In-Reply-To: <20041209002303.GC4674@troutmask.apl.washington.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

On Wed, 8 Dec 2004, Steve Kargl wrote:

> panic: mtx_lock() of spin mutex (null) @ sys/netinet/frag6.c:682
> cpuid = 0
> kdb_backtrace+0x37
> panic+0x1d1
> _mtx_lock_flags+0x72
> frag6_slowtimo+0x26
> pfslowtimo+0x5a
> softclock+0x1c0
> ithread_loop+0x179
> fork_exit+0xe9
> fork_trampoline+0xe
> 
> This is FreeBSD/amd64 from today's sources of about 30 minutes ago.

>From the instant interpretation unit: it looks like this is another
example of a protocl's timeout firing before the protocol is properly
initialized, as the mutex appears to be zero'd due to being in BSS.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Principal Research Scientist, McAfee Research




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041209023008.44319C-100000>