Date: Tue, 09 Jun 2020 15:15:00 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 246951] carp(4): Active CARP member crashes: panic, trap_pfault, ip_input || ip_output when using ipSec, AES-NI (on Intel I350) Message-ID: <bug-246951-7501-XyJ1cCY5oi@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246951-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-246951-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246951 --- Comment #10 from Mark Johnston <markj@FreeBSD.org> --- (In reply to freebsd-bugzilla from comment #9) So from the panic sites it looks like a linked ifaddr structure has been fr= eed. (Or zeroed, but I cannot see any code which does that.) One possible cause that we can try to rule out is a refcount overflow. You said that the upti= me between panics is at least several days - is that consistently the case? In other words, have you ever seen back-to-back crashes in a short timeframe? I'm not sure if pfsense enables DTrace, but if so we can try to probe ifa_ref(), which is helpfully not inlined. Please try this command (you mi= ght need to kldload dtraceall first): # dtrace -n 'fbt::ifa_ref:entry {@[args[0]->ifa_refcnt] =3D count();} tick-= 300s {exit(0);}' It will sleep for 300s and dump a table of reference counts. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246951-7501-XyJ1cCY5oi>