From owner-freebsd-current@FreeBSD.ORG  Sat May  4 12:03:00 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id C89A9D3C;
 Sat,  4 May 2013 12:03:00 +0000 (UTC) (envelope-from ianf@clue.co.za)
Received: from zcs04.jnb1.cloudseed.co.za (zcs04.jnb1.cloudseed.co.za
 [41.154.0.161]) by mx1.freebsd.org (Postfix) with ESMTP id 617171697;
 Sat,  4 May 2013 12:03:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTP id A57D22A830C4;
 Sat,  4 May 2013 10:24:07 +0200 (SAST)
X-Virus-Scanned: amavisd-new at zcs04.jnb1.cloudseed.co.za
Received: from zcs04.jnb1.cloudseed.co.za ([127.0.0.1])
 by localhost (zcs04.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id sSNUYJL8ph84; Sat,  4 May 2013 10:24:07 +0200 (SAST)
Received: from clue.co.za (unknown [41.154.88.19])
 by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id CA4AB2A830C3;
 Sat,  4 May 2013 10:24:06 +0200 (SAST)
Received: from localhost ([127.0.0.1] helo=zen.clue.co.za)
 by clue.co.za with esmtp (Exim 4.80.1 (FreeBSD))
 (envelope-from <ianf@clue.co.za>)
 id 1UYXlD-0001UR-N0; Sat, 04 May 2013 10:24:03 +0200
To: Peter Wemm <peter@wemm.org>
From: Ian FREISLICH <ianf@clue.co.za>
Subject: Re: panic: in_pcblookup_local (?)
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>
X-Attribution: BOFH
Date: Sat, 04 May 2013 10:24:03 +0200
Message-Id: <E1UYXlD-0001UR-N0@clue.co.za>
Cc: Glen Barber <gjb@freebsd.org>, freebsd-current@freebsd.org,
 "Robert N. M. Watson" <rwatson@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 12:03:00 -0000

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