panic: starting DAD on non-tentative address 0xfffff800034a5800,

[Alexander V. Chernikov]

03.06.2020, 11:46, "Bjoern A. Zeeb" <bzeeb-lists at lists.zabbadoz.net>:
> Hi,
>
> got this with HEAD from a few days ago, just in case it rings a bell
> with someone.
I'm curious what are the conditions. Was it the first "up" for the interface?
It looks like we're not locking anything in nd6_dad_timer, so potentially if one configures IPv6 address, waits for most of the dad timer, then do down/up, this can potentially happen.

> Otherwise I’ll go investigate when it happens again; I’ll try to
> setup netdump to get more information.
>
> panic: starting DAD on non-tentative address 0xfffff800034a5800
> cpuid = 1
> time = 1500939739
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
> 0xfffffe003b65a690
> vpanic() at vpanic+0x182/frame 0xfffffe003b65a6e0
> panic() at panic+0x43/frame 0xfffffe003b65a740
> nd6_dad_start() at nd6_dad_start+0x3bb/frame 0xfffffe003b65a7e0
> in6_if_up() at in6_if_up+0x62/frame 0xfffffe003b65a820
> if_up() at if_up+0x69/frame 0xfffffe003b65a850
> ifhwioctl() at ifhwioctl+0xbf8/frame 0xfffffe003b65a8d0
> ifioctl() at ifioctl+0x3ac/frame 0xfffffe003b65a9a0
> kern_ioctl() at kern_ioctl+0x27b/frame 0xfffffe003b65aa00
> sys_ioctl() at sys_ioctl+0x127/frame 0xfffffe003b65aad0
> amd64_syscall() at amd64_syscall+0x140/frame 0xfffffe003b65abf0
> fast_syscall_common() at fast_syscall_common+0x101/frame
> 0xfffffe003b65abf0
> --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80047cd8a, rsp =
> 0x7fffffffe258, rbp = 0x7fffffffe2b0 ---
> KDB: enter: panic
> [ thread pid 12247 tid 100088 ]
> Stopped at kdb_enter+0x37: movq $0,0x10c9ad6(%rip)
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"