kern/127724: rtfree: 0xc5a8f870 has 1 refs

[Jason Mader]

>Number:         127724
>Category:       kern
>Synopsis:       rtfree: 0xc5a8f870 has 1 refs
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 29 17:50:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Jason Mader
>Release:        7.0-RELEASE-p4
>Organization:
The George Washington University
>Environment:
FreeBSD tri-mx.seas.gwu.edu 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #0: Thu Sep 25 17:33:34 EDT 2008     jason at tri-mx.seas.gwu.edu:/usr/obj/usr/src/sys/PROSERV  i386


>Description:
/var/log/messages:
Sep 29 10:41:59 tri-mx kernel: rtfree: 0xc57d0438 has 1 refs
Sep 29 12:16:49 tri-mx kernel: rtfree: 0xc5a8f870 has 1 refs

I've read about this problem, and thought it had been patched by now.  My setup doesn't seem to be the same as most others reporting the rtfree warning.  On interface em0 I have a lot of IP aliases:

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
	options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
	ether 00:15:17:74:b5:e4
	inet 161.253.154.22 netmask 0xffffffc0 broadcast 161.253.154.63
	inet 161.253.154.18 netmask 0xffffffff broadcast 161.253.154.18
	inet 161.253.154.19 netmask 0xffffffff broadcast 161.253.154.19
	inet 161.253.154.20 netmask 0xffffffff broadcast 161.253.154.20
	inet 161.253.154.21 netmask 0xffffffff broadcast 161.253.154.21
	media: Ethernet autoselect (1000baseTX <full-duplex>)
	status: active

And there are different gateways to local networks, e.g., 

default            161.253.154.62     UGS         0  2093825    em0
161.253.154.242    161.253.154.61     UGHD3       0       68    em0   3538
161.253.155.65     161.253.154.60     UGHD3       0      101    em0   3600

I hope that's useful.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: