Bug #7124
closed
Kernel panic when configuring 6to4 on a interface
100%
Description
Kernel panic when configuring 6to4 on a interface
pfSense on virtualbox: 2.4.0-BETA (amd64) built on Sat Jan 14 10:34:34 CST 2017
Complete crash dumps also uploaded.
db:0:kdb.enter.default> bt Tracing pid 98584 tid 100540 td 0xfffff8002a350000 kdb_enter() at kdb_enter+0x3b/frame 0xffffffff82976970 vpanic() at vpanic+0x19f/frame 0xffffffff829769f0 panic() at panic+0x43/frame 0xffffffff82976a50 dblfault_handler() at dblfault_handler+0xa2/frame 0xffffffff82976a70 Xdblfault() at Xdblfault+0xac/frame 0xffffffff82976a70 --- trap 0x17, rip = 0xffffffff80f765c7, rsp = 0xfffffe004e200fe0, rbp = 0xfffffe004e201060 --- pfr_walktree() at pfr_walktree+0x1a7/frame 0xfffffe004e201060 rn_walktree() at rn_walktree+0x70/frame 0xfffffe004e201090 pfr_dynaddr_update() at pfr_dynaddr_update+0x57/frame 0xfffffe004e2010d0 pfi_kif_update() at pfi_kif_update+0x2b/frame 0xfffffe004e201130 pfi_kif_update() at pfi_kif_update+0x19c/frame 0xfffffe004e201190 pfi_kif_update() at pfi_kif_update+0x19c/frame 0xfffffe004e2011f0 pfi_kif_update() at pfi_kif_update+0x19c/frame 0xfffffe004e201250 ... ... pfi_kif_update() at pfi_kif_update+0x19c/frame 0xfffffe004e204850 pfi_kif_update() at pfi_kif_update+0x19c/frame 0xfffffe004e2048b0 pfi_change_group_event() at pfi_change_group_event+0xb6/frame 0xfffffe004e2048e0 if_addgroup() at if_addgroup+0x984/frame 0xfffffe004e204940 if_clone_createif() at if_clone_createif+0x1bf/frame 0xfffffe004e204990 kern_ioctl() at kern_ioctl+0x2d4/frame 0xfffffe004e204a00 sys_ioctl() at sys_ioctl+0x171/frame 0xfffffe004e204ad0 amd64_syscall() at amd64_syscall+0x4ce/frame 0xfffffe004e204bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe004e204bf0 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x801dfc0aa, rsp = 0x7fffffffa988, rbp = 0x7fffffffa9e0 ---
Updated by Chris Palmer almost 8 years ago
Just want to confirm that this appears to have kept my box from booting. But would restart over and over. No logs to share.
Once I deleted 6to4 from my WAN the box started just fine. Watchguard XTM5 box.
Updated by Renato Botelho almost 8 years ago
- Status changed from New to Confirmed
- Assignee set to Luiz Souza
Updated by Luiz Souza almost 8 years ago
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Fixed.
Relevant commit: https://github.com/pfsense/FreeBSD-src/commit/c050d42a2646d2e582c46cc6f61531150ffb6cb9
Updated by Pi Ba almost 8 years ago
Thanks, i can no longer reproduce the panic.
If 6to4 itself works properly now i cant tell, i have not used it before..
If i configure ipv4 with: 12.13.14.15 i do see it has a v6 ip: 2002:c0d:e0f:: looks okay to me.. And surly better than the crash that happened before ;) .
Anyhow this ticked can be closed imho. Thanks again.
Updated by Chris Palmer almost 8 years ago
Confirmed working here as well. Thank You!
Updated by Chris Palmer almost 8 years ago
Seems right now I cannot monitor the gateway though if I ping from diagnostics the ping returns fine.
Gateway monitor shows unreachable.
2002:c058:6301::1
Not sure if related.
Updated by Chris Palmer almost 8 years ago
Actually just shows "Pending".
Other (2.3) box works.
Updated by Luiz Souza almost 8 years ago
- Status changed from Feedback to Resolved
Yeah, that's a different issue, can you open a new ticket for it ?
Thanks!