Date: Thu, 2 May 2013 12:25:08 +0100 From: "Robert N. M. Watson" <rwatson@freebsd.org> To: Glen Barber <gjb@FreeBSD.org> Cc: Ian FREISLICH <ianf@clue.co.za>, freebsd-current@freebsd.org Subject: Re: panic: in_pcblookup_local (?) Message-ID: <52B3AEE5-D24A-4ED3-BB11-E7E27BFB447F@freebsd.org> In-Reply-To: <20130502104219.GA1586@glenbarber.us> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52B3AEE5-D24A-4ED3-BB11-E7E27BFB447F>