Date: Wed, 28 Feb 2018 09:52:20 +0545 From: "Kristof Provost" <kristof@sigsegv.be> To: "Joe Jones" <joe@stream-technologies.com> Cc: freebsd-pf@freebsd.org Subject: Re: Kernel Panic Message-ID: <22A6028C-9BBA-4117-8734-D976EA5A1367@sigsegv.be> In-Reply-To: <19aedb50-34c0-417d-fc1e-e8d519655684@stream-technologies.com> References: <5A842FC6.7020806@stream-technologies.com> <FCB6BE6F-5346-42EC-ACB2-9CD99A1A16F0@sigsegv.be> <5A8443BF.8040208@stream-technologies.com> <5289570D-24E1-4292-B4D2-D2F67D7D2D4F@sigsegv.be> <5A93EDC9.7020407@stream-technologies.com> <9F39A687-FB34-4984-B969-5264DF38544E@sigsegv.be> <19aedb50-34c0-417d-fc1e-e8d519655684@stream-technologies.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 Feb 2018, at 20:40, Joe Jones wrote: > we have a kernel panic after compiling with witness and invariant > > Feb 27 13:49:33 sovapn1 kernel: lock order reversal: > Feb 27 13:49:33 sovapn1 kernel: 1st 0xfffffe000fed78b8 pf_idhash > (pf_idhash) @ /usr/src/sys/netpfil/pf/pf.c:1078 > Feb 27 13:49:33 sovapn1 kernel: 2nd 0xfffff8001e0474a8 pfsync (pfsync) > @ /usr/src/sys/netpfil/pf/if_pfsync.c:1667 That’s a lock order reversal. It’s not good, but it should at worst result in a deadlock. Did the system stop after this? It also looks like a different problem from the panic you initially reported. Regards, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22A6028C-9BBA-4117-8734-D976EA5A1367>