https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291552
Bug ID: 291552
Summary: vlan on wireless with ipv6 kernel panic
Product: Base System
Version: 15.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: wireless
Assignee: [email protected]
Reporter: [email protected]
Created attachment 266065
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=266065&action=edit
dmesg captured after the recovery reboot
The kernel panics when a vlan interface on a wlan has ipv6 enabled. The bug
dates back to at least 13.5-RELEASE and occurs with both an Intel and an
Atheros chipset. It was reproduced on two machines.
Steps to reproduce:
ifconfig wlan0 create wlandev iwm0
ifconfig wlan0.50 create vlan 50 vlandev wlan0 inet6 -ifdisabled up
I've verified this on three setups:
1. An HP mini-PC with an Intel AC8265, under release versions of FreeBSD 15.0,
14.3 and 13.5.
2. The same machine, having installed a Qualcomm Atheros QCNFA222, under 13.5,
substituting ath0 for iwm0.
3. A Thinkpad with an Intel AC 8260, under FreeBSD 15.0 and 13.5.
All of these were booted directly from the live USB images to rule out any
local changes causing the issue. I've verified that taking similar steps on an
ethernet interface does not cause a crash.
I've captured a core dump if that would be useful. I've also attached the full
dmesg dump from the machine after it had rebooted back into a usable state,
crash output as follows:
251 Fatal trap 9: general protection fault while in kernel mode
252 cpuid = 1; apic id = 11
253 instruction pointer = 0x20:0xffffffff80d0c16f
254 stack pointer = 0x28:0xfffffe00f90aaab8
255 frame pointer = 0x28:0xfffffe00f90aac70
256 code segment = base 0x0, limit 0xfffff, type 0x1b
257 = DPL 0, pres 1, long 1, def32 0, gran 1
258 processor eflags = interrupt enabled, resume, IOPL = 0
259 current process = 2 (clock (0))
260 rdi: fffff800426d1800 rsi: fffff800421db600 rdx: fffffe00f90aaaf4
261 rcx: 0000000000000000 r8: 0000000000000000 r9: 0000000000000000
262 rax: d04baeb3dc0baeb7 rbx: 0000000000000000 rbp: fffffe00f90aac70
263 r10: 00000000eac7e14d r11: fffff800039112e0 r12: 0000000000000000
264 r13: fffff800421db688 r14: 0000000000000000 r15: 0000000000000048
265 trap number = 9
266 panic: general protection fault
267 cpuid = 1
268 time = 1765233382
269 KDB: stack backtrace:
270 #0 0xffffffff80bbe1ed at kdb_backtrace+0x5d
271 #1 0xffffffff80b71576 at vpanic+0x136
272 #2 0xffffffff80b71433 at panic+0x43
273 #3 0xffffffff81079b98 at trap_fatal+0x68
274 #4 0xffffffff8104ff18 at calltrap+0x8
275 #5 0xffffffff80da1ede at nd6_ns_output+0x4ee
276 #6 0xffffffff80da331b at nd6_dad_timer+0x1cb
277 #7 0xffffffff80b8e60d at softclock_call_cc+0x16d
278 #8 0xffffffff80b8fca5 at softclock_thread+0xe5
279 #9 0xffffffff80b2786b at fork_exit+0x7b
Trying to put a vlan on a wireless interface is probably a silly thing to do,
I'm just being lazy about finding an ethernet cable.
--
You are receiving this mail because:
You are the assignee for the bug.
