Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Jun 2020 09:46:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 246951] Regular crash: panic, trap_pfault, ip_input || ip_output using ipSec, AES-NI & CARP
Message-ID:  <bug-246951-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246951

            Bug ID: 246951
           Summary: Regular crash: panic, trap_pfault, ip_input ||
                    ip_output using ipSec, AES-NI & CARP
           Product: Base System
           Version: 11.3-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: freebsd-bugzilla@biscuit.ninja

Created attachment 215186
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D215186&action=
=3Dedit
Compilation of crash dump information

Hello,

We're using FreeBSD 11.3 Stable (pfSense). We have encountered numerous ker=
nel
panics during recent months (see attached). They are all trap_pfault and
usually feature ip_input or ip_output.

The pfSense boxes are in a CARP configuration (the crash is always on the
active firewall). We are using IPSec (AES256-GCM, SHA256) and AES-NI. Many =
but
not all of the stack traces include IPSec and AES-NI calls.All interfaces a=
re
using switch independent failover LAGG.

Using FreeBSD 11.2-RELEASE-p3 without producing this problem.=20

There is one other person who appears to have the same problem:
https://forum.netgate.com/topic/151329/pfsense-active-carp-member-crashed-a=
esni_process-crypto_dispatch/12

Hardware is as follows:
* Dell PowerEdge R330
* Intel Xeon E3-1270 v5
* Intel I350 Quad Port 1GbE network cards (x2)

We are just wondering if you can give any pointers as to the potential
cause/resolution?

Thank you

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246951-227>