Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Nov 2007 10:15:57 -0800
From:      "Kip Macy" <kip.macy@gmail.com>
To:        "Per olof Ljungmark" <peo@intersonic.se>
Cc:        freebsd-current@freebsd.org, Stefan Lambrev <stefan.lambrev@moneybookers.com>
Subject:   Re: rtfree: 0xc741ee88 has 1 refs
Message-ID:  <b1fa29170711061015l67d999ceqfcdf1d668d18ad6b@mail.gmail.com>
In-Reply-To: <4730AA30.7090607@intersonic.se>
References:  <472B1E89.5080006@moneybookers.com> <47303578.8060703@moneybookers.com> <4730AA30.7090607@intersonic.se>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/6/07, Per olof Ljungmark <peo@intersonic.se> wrote:
> Stefan Lambrev wrote:
> > Hi,
> >
> > Sorry to reply to myself, but I found that the problem exist only if the
> > GW is carp interface, e.g. 10.1.1.1 sits on carp0 on default GW.
> > I'm still testing how to reproduce this in my test lab and will fill a PR.
> >
> > Stefan Lambrev wrote:
> >> Hi,
> >>
> >> I see rtfree: 0xc741ee88 has 1 refs with freebsd releng_7 (i386) from
> >> today.
> >>
> >> I think it's easy reproducible. What I have is:
> >>
> >> releng_7 (10.1.1.2) -> default GW (10.1.1.1)
> >> on default GW I have route to 10.10.1.1/24 -> 10.1.1.3
> >>
> >> so everytime when 10.1.1.2 try to contact someone from 10.10.1.1/24 I
> >> see:
> >> rtfree: 0xc741ee88 has 1 refs
> >>
> >> if I add direct route on 10.1.1.2 to 10.10.1.1/24 through 10.1.1.3 the
> >> message will go away.
> >>
> >> Should I ignore this msg for now, or should I expect kernel panic
> >> soon? :)
>
> Just FYI, I see this on a few boxes including the 7-BETA2 I'm writing
> this on. None of them has a carp interface though. What I find
> interesting here is that none of them are able to run a SMP kernel
> without crashing (no panic, they're just frozen completely).
>
> Perhaps it is a coincidence, I don't know, but I am very interested in
> your findings and have testbeds if you need.
>

The warning is mostly harmless. It means that rtfree is being called
where RTFREE_LOCKED should be used. Adding a kdb_backtrace() should
track it down for you.

 -Kip



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