Bug 258528 - [fib_algo][routing] crash after switch algo
Summary: [fib_algo][routing] crash after switch algo
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 13.0-STABLE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-net (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-16 09:28 UTC by Konrad
Modified: 2022-06-28 16:16 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Konrad 2021-09-16 09:28:25 UTC
Hardware: Dell R630, Chelsio T62100-SO-CR
Network: lagg, vlans
Jail: vnet, vlans, bird (received full feed)
Kernel:

root@Storm:~ # uname -a
FreeBSD Storm 13.0-STABLE FreeBSD 13.0-STABLE #14 stable/13-139144a7a-dirty: Wed Sep  8 02:18:17 CEST 2021     root@Storm:/usr/obj/usr/src/amd64.amd64/sys/ROUTER  amd64

I switched many times between DXR and DPDK_LPM4 without problem but today something goes wrong:

panic: vm_fault_lookup: fault on nofault entry, addr: 0xfffffe015d4a7000
cpuid = 13
time = 1631744099
KDB: stack backtrace:
#0 0xffffffff80cbbc95 at kdb_backtrace+0x65
#1 0xffffffff80c6dde7 at vpanic+0x187
#2 0xffffffff80c6dc53 at panic+0x43
#3 0xffffffff80f99432 at vm_fault+0x1432
#4 0xffffffff80f97f21 at vm_fault_trap+0xb1
#5 0xffffffff810fb780 at trap_pfault+0x1f0
#6 0xffffffff810fac5a at trap+0x26a
#7 0xffffffff810d2608 at calltrap+0x8
#8 0xffffffff80e0b4dd at fib4_lookup+0x3d
#9 0xffffffff80e18d5e at ip_findroute+0x1e
#10 0xffffffff80e186b7 at ip_tryforward+0x247
#11 0xffffffff80e1af02 at ip_input+0x352
#12 0xffffffff80da503a at netisr_dispatch_src+0xca
#13 0xffffffff80d89078 at ether_demux+0x138
#14 0xffffffff80d8a41e at ether_nh_input+0x34e
#15 0xffffffff80da503a at netisr_dispatch_src+0xca
#16 0xffffffff80d894c9 at ether_input+0x69
#17 0xffffffff80d89061 at ether_demux+0x121
Uptime: 7d21h52m39s
Dumping 5427 out of 32631 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%

I switched from DXR to DPDK_LPM4
Comment 1 Alexander V. Chernikov freebsd_committer freebsd_triage 2022-05-30 12:21:28 UTC
Sorry for the belated reply. Were there any other similar crashes after this one?
Comment 2 Konrad 2022-06-28 16:16:43 UTC
I haven't experienced it more times. 
Only one time did something go wrong