Date: Sat, 04 May 2013 10:24:03 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: Peter Wemm <peter@wemm.org> Cc: Glen Barber <gjb@freebsd.org>, freebsd-current@freebsd.org, "Robert N. M. Watson" <rwatson@freebsd.org> Subject: Re: panic: in_pcblookup_local (?) Message-ID: <E1UYXlD-0001UR-N0@clue.co.za> In-Reply-To: <CAGE5yCq3adNey0U1HDZxFY1dmeAu1H0QjeOoi5kYQdTzowKnmg@mail.gmail.com> References: <CAGE5yCq3adNey0U1HDZxFY1dmeAu1H0QjeOoi5kYQdTzowKnmg@mail.gmail.com> <201305021209.41221.jhb@freebsd.org> <52B3AEE5-D24A-4ED3-BB11-E7E27BFB447F@freebsd.org> <E1UXxhT-000MPI-Ju@clue.co.za> <201305021432.34456.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote: > >> > offending revision. > >> > >> I've started a binary search. I'll let you know what that turns up. > > > > Thanks, and sorry for getting my Ian's mixed up. :-/ > > > > -- > > John Baldwin > > There's been two separate machines, at least twice each on this exact > panic / trace. Always with doing a 'svn update'. > > Rolling back to April 5th 249172 solves it. (There's nothing > particular about that rev, except it was top-of-tree when the last > update was done). > > I see a number locking changes in the area. Note that this is UDP, > most likely a dns lookup. I'll work to confirm this here. I was a little slow in bisecting because I spent 2 days trying to figure out what revision caused PF to rapidly expire its entire state table which prevented testing this condition. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1UYXlD-0001UR-N0>