Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 May 1995 21:45:44 -0500 (CDT)
From:      Mike Pritchard <pritc003@maroon.tc.umn.edu>
To:        bugs@FreeBSD.org
Subject:   -current kernel panics in rtfree
Message-ID:  <199505130245.VAA00225@mpp.com>

next in thread | raw e-mail | index | archive | help
I don't have time to examine the crash dump I've got now, but
I've seen a couple of crashes with a -current kernel from about 2
hours ago.  The chain of events seems to be:

1)  I make a slip connection (delete some routes, start the connection,
    setup my routing for my dynamic IP number from my provider),
2)  do some stuff over the slip link (get mail, etc)
3)  terminate the slip link (delete some of the previous routes I just
    setup, and reset them to route the way they were originally)

The default route is involved above, which makes me suspect some code that
went in recently in this area.  I've never seen a problem with a kernel
from a couple of weeks ago.

Shortly after terminating the slip link the machine panics with:

panic: rtfree

During one of the panics I also saw:

May 12 21:23:22 mpp /kernel.mpp: rtfree: 0xf06b2d00 not freed (neg refs)

shortly before the actual panic.

The stack trace from both crashes shows that we are in the
softclock() routine processing the callout table.  Here is the
stack from the dump I have right now:

Reading symbol data from /usr/var/crash/kernel.0...
(no debugging symbols found)...done.
IdlePTD 202000
panic: rtfree
current pcb at 1d63b0
(kgdb) bt
#0  0xf0199394 in boot ()
#1  0xf0117dc5 in panic ()
#2  0xf010125d in db_panic ()
#3  0xf0101146 in db_command (-266589452, -266589868, -267382174)
#4  0xf01012c5 in db_command_loop ()
#5  0xf0103c48 in db_trap ()
#6  0xf01965ea in kdb_trap (3, 0, -272630676)
#7  0xf019d9e4 in trap ()
#8  0xf0196e91 in exception:calltrap ()
#9  0xf0117dbf in panic ()
#10 0xf013f39f in rtfree (-261400576)
#11 0xf013f434 in rtfree (-261365248)
#12 0xf01441f5 in in_pcbdetach ()
#13 0xf014e16e in tcp_close ()
#14 0xf014e49e in tcp_timers (-261365504, 3)
#15 0xf014ea35 in tcp_usrreq (-261372416, 19, 0, 3, 0)
#16 0xf014e3cd in tcp_slowtimo ()
#17 0xf011fb0f in pfslowtimo (0)
#18 0xf010bbf0 in softclock ()
#19 0xf01981e7 in exception:doreti_swi ()
#20 0xf012d9e0 in chmod ()
#21 0xf019e3c5 in syscall ()
(kgdb) quit


Another disturbing thing that happened during the above crash was that my 
clock was also reset to be exactly 4 months in the past from May 12
to Jan 12, the time was correct.
-- 
Mike Pritchard
pritc003@maroon.tc.umn.edu
"Go that way.  Really fast.  If something gets in your way, turn"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505130245.VAA00225>