Re: panic in sbdrop_locked
- From: Gleb Smirnoff <glebius@xxxxxxxxxxx>
- Date: Mon, 30 Jan 2006 13:05:17 +0300
On Sat, Jan 28, 2006 at 01:45:07AM +0100, Meno Abels wrote:
M> i have two boxes running currently freebsd-6.0-p3 i386 and they are
M> panic around every 24 hour once a time. I just update to -p4 so i will
M> see if it working better. I also didn't have the debug kernel ready so
M> i can only provide this very weak infos:
M> (kgdb) bt
M> #0 0xc06e5b2c in doadump ()
M> #1 0xc06e60c0 in boot ()
M> #2 0xc06e6409 in panic ()
M> #3 0xc0731406 in sbdrop_locked ()
M> #4 0xc07b373e in tcp_input ()
M> #5 0xc07a93fe in ip_input ()
M> #6 0xc077a2b9 in netisr_processqueue ()
M> #7 0xc077a51f in swi_net ()
M> #8 0xc06cbfe8 in ithread_loop ()
M> #9 0xc06caebf in fork_exit ()
M> #10 0xc090fe1c in fork_trampoline ()
M>
M> Is there any procedure to track this problem down other than have a
M> debug kernel prepared what i done now-:) And have a very close look to
M> the backtrace. I saw it
M> happens sometimes in the development branches.
Yes, the same backtrace with debugging kernel will be much more
informative. Please followup when you got one.
--
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- References:
- panic in sbdrop_locked
- From: Meno Abels
- panic in sbdrop_locked
- Prev by Date: Re: /usr/src/lib/libc/net/res_debug.c: compile problem fixed
- Next by Date: Re: re0: 2 link states coalesced.
- Previous by thread: panic in sbdrop_locked
- Next by thread: multiple natd + ipfw, with 2 internal ip's
- Index(es):