From owner-freebsd-current@FreeBSD.ORG  Thu May  2 11:25:11 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id DD09FDCB;
 Thu,  2 May 2013 11:25:11 +0000 (UTC)
 (envelope-from rwatson@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.56])
 by mx1.freebsd.org (Postfix) with ESMTP id BADA614E1;
 Thu,  2 May 2013 11:25:11 +0000 (UTC)
Received: from c0237.aw.cl.cam.ac.uk (c0237.aw.cl.cam.ac.uk [128.232.100.237])
 by cyrus.watson.org (Postfix) with ESMTPSA id 80DF746B8D;
 Thu,  2 May 2013 07:25:10 -0400 (EDT)
Subject: Re: panic: in_pcblookup_local (?)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Robert N. M. Watson" <rwatson@freebsd.org>
In-Reply-To: <20130502104219.GA1586@glenbarber.us>
Date: Thu, 2 May 2013 12:25:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <52B3AEE5-D24A-4ED3-BB11-E7E27BFB447F@freebsd.org>
References: <E1UW0K5-000P7H-36@clue.co.za>
 <20130501180321.GA44525@glenbarber.us>
 <49916D2B-496A-40EA-971F-62951FF6B584@freebsd.org>
 <201305011430.37106.jhb@freebsd.org> <20130502005704.GB1623@glenbarber.us>
 <C154B059-A634-4162-A984-B1972F786F7C@freebsd.org>
 <20130502104219.GA1586@glenbarber.us>
To: Glen Barber <gjb@FreeBSD.org>
X-Mailer: Apple Mail (2.1283)
Cc: Ian FREISLICH <ianf@clue.co.za>, freebsd-current@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: Thu, 02 May 2013 11:25:11 -0000


On 2 May 2013, at 11:42, Glen Barber wrote:

> Hmm.  Perhaps it would be worthwhile for me to rebuild the current
> kernel with DDB support.  It looks like the machine has panicked a few
> times over the last two weeks or so, but based on the timestamps of =
the
> crash dumps and nagios complaints, happened during the middle of the
> night when I would not have really noticed, or otherwise would have =
just
> blamed my ISP.
>=20
> Two of the panics are ath(4) related.  One looks similar to the one
> referenced in this thread, similarly triggered by a CFEngine process.
>=20
> In that case, the backtrace looks like:
>=20
> #4 0xffffffff808cdbb3 at calltrap+0x8
> #5 0xffffffff807371d8 at in_pcb_lport+0x128
> #6 0xffffffff8073745a at in_pcbbind_setup+0x16a
> #7 0xffffffff80737d8e at in_pcbconnect_setup+0x71e
> #8 0xffffffff80737df9 at in_pcbconnect_mbuf+0x59
> #9 0xffffffff807bf29f at udp_connect+0x11f
> #10 0xffffffff80680615 at kern_connectat+0x275
>=20
> Regarding DDB though, it would be rather difficult to access the =
machine
> if it drops to a DDB debugger session, since the machine acts as my
> firewall.

Thanks -- will take a look at the attached.

FWIW, though, I'm worried by the number of panics you are seeing, =
especially given that they involve multiple subsystems, and in =
particular, John's observation about a potentially corrupted pointer. =
This makes me wonder whether (a) you are experiencing hardware faults -- =
it would be worth running some memory/cpu/etc tests and (b) if we might =
be seeing a software memory corruption bug of some sort.

Robert=