From owner-freebsd-current@FreeBSD.ORG Tue Nov 6 19:51:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1465E16A41A for ; Tue, 6 Nov 2007 19:51:27 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id D19F213C4B5 for ; Tue, 6 Nov 2007 19:51:26 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <4730C5B9.1030709@intersonic.se> Date: Tue, 06 Nov 2007 20:51:21 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.6 (X11/20071103) MIME-Version: 1.0 To: Kip Macy References: <472B1E89.5080006@moneybookers.com> <47303578.8060703@moneybookers.com> <4730AA30.7090607@intersonic.se> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Stefan Lambrev Subject: Re: rtfree: 0xc741ee88 has 1 refs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Nov 2007 19:51:27 -0000 Kip Macy wrote: >>>> >>>> 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. "Mostly", meaning that in some cases it actually does harm? I cannot help noting the fact I decribed above but as I have not investigated it it may as well be just a coincidence. I hope I can set aside some time to investigate it further. --per