From owner-freebsd-current@FreeBSD.ORG Tue Oct 16 19:06:34 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 A32E516A420; Tue, 16 Oct 2007 19:06:34 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id 6486213C45B; Tue, 16 Oct 2007 19:06:34 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.1/8.14.1) id l9GJ6XhG087586; Tue, 16 Oct 2007 14:06:33 -0500 (CDT) (envelope-from dan) Date: Tue, 16 Oct 2007 14:06:33 -0500 From: Dan Nelson To: Kris Kennaway Message-ID: <20071016190633.GA77224@dan.emsphone.com> References: <20070912172752.GA13960@dan.emsphone.com> <200710101615.48760.jhb@freebsd.org> <20071012143800.GA76105@dan.emsphone.com> <470F9211.8010604@FreeBSD.org> <20071016163123.GA22599@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071016163123.GA22599@dan.emsphone.com> X-OS: FreeBSD 7.0-PRERELEASE User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, Ivan Voras Subject: Re: Panic in arpresolve->rt_check? 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, 16 Oct 2007 19:06:34 -0000 In the last episode (Oct 16), Dan Nelson said: > In the last episode (Oct 12), Kris Kennaway said: > > Dan Nelson wrote: > >> In the last episode (Oct 10), John Baldwin said: > >>> On Wednesday 12 September 2007 02:50:37 pm Ivan Voras wrote: > >>>> Dan Nelson wrote: > >>>>> The same panic was also reported for 6.2 via PR 107865 and PR > >>>>> 112490. 112490 included a workaround patch (I haven't tried it; > >>>>> just found it). > >>>> > >>>> The proposed patch in kern/112490 looks trivial but someone who > >>>> knows more about net locking should check it out. Unfortunately it > >>>> lacks context and I don't know the code in question to apply it > >>>> safely on a production machine :( > >>> > >>> I also get panics with what appears to be a double free of > >>> rt_gwroute in rtexpunge(), so I think while this PR may help some > >>> with figuring out the problem, I'm not sure it solves the root bug. > >>> > >>> Hmm, possibly try this patch: > >> > >> This makes the panics more frequent on my machine, actually :) > > > > Since you can reproduce this frequently the best thing might be to > > instrument all the route handling with KTR so that you can do > > post-mortem and try to figure out where the double-free or missing > > reference happened. > > I've added some KTR debugging (why are the macros named CTR* instead of > KTR* ? ) and I think I've got the problem nailed down, but I don't know > anything about networking so I don't know what the solution is. .. and then I notice that yesterday John updated PR 112490 with a patch that looks like it'll fix the problem, just to make me look silly today :) -- Dan Nelson dnelson@allantgroup.com