https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233341
--- Comment #3 from Joe Barbish <qja...@a1poweruser.com> ---
I don't disagree that the traffic looks like a device announcing itself using
the Simple Service Discovery Protocol. Thanks for identifying what it is. The
problem is it never ends. The log file is flooded until it fills up and then
rotates. This is not happening on amd64 system and if I use ipfw on the host
and vnet jail this also does't happen. That is the problem.
Cut the following out of the vmcore dump. Hope its what you want.
in6_purgeaddr: err=65, destination address delete failed
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x2f9528c8
fault code = supervisor read, page not present
instruction pointer = 0x20:0x18c0f2c0
stack pointer = 0x28:0x16614b6c
frame pointer = 0x28:0x16614b74
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 0 (thread taskq)
trap number = 12
panic: page fault
cpuid = 0
time = 1542749869
KDB: stack backtrace:
#0 0x11080cf at kdb_backtrace+0x4f
#1 0x10bb097 at vpanic+0x147
#2 0x10baf4b at panic+0x1b
#3 0x16910a5 at trap_fatal+0x395
#4 0x16910e3 at trap_pfault+0x33
#5 0x169072f at trap+0x3cf
#6 0xffc0315d at PTDpde+0x4165
#7 0x11b9a06 at if_clone_destroyif+0x1a6
#8 0x11ba17c at if_clone_detach+0xbc
#9 0x18c0f441 at vnet_pflog_uninit+0x21
#10 0x11dfaeb at vnet_destroy+0x10b
#11 0x1083da4 at prison_deref+0x284
#12 0x1119c59 at taskqueue_run_locked+0x189
#13 0x111ae07 at taskqueue_thread_loop+0x97
#14 0x107c731 at fork_exit+0x71
#15 0xffc033ba at PTDpde+0x43c2
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
