Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Jun 2020 01:30:33 +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-JE4YcNRNoZ@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

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Regular crash: panic,       |carp(4): Active CARP member
                   |trap_pfault, ip_input ||    |crashes: panic,
                   |ip_output using ipSec,      |trap_pfault, ip_input ||
                   |AES-NI & CARP               |ip_output when using ipSec,
                   |                            |AES-NI (on Intel I350)
                URL|                            |https://forum.netgate.com/t
                   |                            |opic/151329/pfsense-active-
                   |                            |carp-member-crashed-aesni_p
                   |                            |rocess-crypto_dispatch/12
             Status|New                         |Open
              Flags|                            |mfc-stable12?,
                   |                            |mfc-stable11?
                 CC|                            |net@FreeBSD.org
           Keywords|panic                       |crash, needs-qa, regression

--- Comment #4 from Kubilay Kocak <koobs@FreeBSD.org> ---
@Reporter Could you please add additional information, including:

- /var/run/dmesg.boot output (as an attachment)
- /etc/rc.conf network configuration (minimal reproducer configuration,
sanitised where necessary, as an attachment)
- Details of reproducibility changes isolating any of the components of the
configuration (ipsec, different interface, not incl lagg(4) etc)
- Any indications of events/traffic/workloads that might be relevent to
triggering the crash

--=20
You are receiving this mail because:
You are on the CC list for the bug.
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-7501-JE4YcNRNoZ>