[Bug 246951] carp(4): Active CARP member crashes: panic, trap_pfault, ip_input || ip_output when using ipSec, AES-NI (on Intel I350)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Jun 25 15:57:44 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246951

igor-fbsdbugs at grinchenko.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |igor-fbsdbugs at grinchenko.or
                   |                            |g

--- Comment #11 from igor-fbsdbugs at grinchenko.org ---
unfortunately dtrace is not available on pfsense. is there another way to get
the refcounts?

I can confirm, however, that it does take a few days for this crash to happen.
usually within 4-8 days, but never immediately.

I have a handful of crash backtraces from previous crashes.
I will paste the first 3 few lines from each. let me know if you need the
entire dumps:

Tracing pid 12 tid 100285 td 0xfffff8000ccf6620
ip_input() at ip_input+0x60e/frame 0xfffffe0451afee70
netisr_dispatch_src() at netisr_dispatch_src+0xa8/frame 0xfffffe0451afeec0
ether_demux() at ether_demux+0x173/frame 0xfffffe0451afeef0


Tracing pid 12 tid 100263 td 0xfffff8000c88f620
ip_output() at ip_output+0x1418/frame 0xfffffe0451a15a60
ipsec_process_done() at ipsec_process_done+0x1c8/frame 0xfffffe0451a15ab0
esp_output_cb() at esp_output_cb+0xeb/frame 0xfffffe0451a15b10


db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100283 td 0xfffff8000c67b000
ip_output() at ip_output+0x1418/frame 0xfffffe0451af4a60
ipsec_process_done() at ipsec_process_done+0x1c8/frame 0xfffffe0451af4ab0
esp_output_cb() at esp_output_cb+0xeb/frame 0xfffffe0451af4b10


Tracing pid 12 tid 100270 td 0xfffff8000c8cf000
ip_input() at ip_input+0x60e/frame 0xfffffe0451a38e70
netisr_dispatch_src() at netisr_dispatch_src+0xa8/frame 0xfffffe0451a38ec0
ether_demux() at ether_demux+0x173/frame 0xfffffe0451a38ef0


Tracing pid 12 tid 100267 td 0xfffff8000c3f3620
ip_input() at ip_input+0x60e/frame 0xfffffe0451a29e70
netisr_dispatch_src() at netisr_dispatch_src+0xa8/frame 0xfffffe0451a29ec0
ether_demux() at ether_demux+0x173/frame 0xfffffe0451a29ef0


Tracing pid 18 tid 100138 td 0xfffff800085d1620
ip_output() at ip_output+0x1418/frame 0xfffffe044f4181c0
ipsec_process_done() at ipsec_process_done+0x1c8/frame 0xfffffe044f418210
esp_output_cb() at esp_output_cb+0xeb/frame 0xfffffe044f418270


Tracing pid 12 tid 100264 td 0xfffff8000c15f000
in_broadcast() at in_broadcast+0x43/frame 0xfffffe0451a1ac40
ip_output() at ip_output+0x7be/frame 0xfffffe0451a1ad70
ip_forward() at ip_forward+0x2b5/frame 0xfffffe0451a1ae10

our pfsense host is relatively busy pushing about 300mbit of traffic through,
with about half of it to the ipsec tunnel.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the freebsd-net mailing list