[Bug 286302] avahi-daemon Fatal trap 12: page fault while in kernel mode
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 286302] net/avahi: avahi-daemon causes Fatal trap 12: page fault while in kernel mode"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 286302] net/avahi: avahi-daemon causes Fatal trap 12: page fault while in kernel mode"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 286302] net/avahi: avahi-daemon causes Fatal trap 12: page fault while in kernel mode"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 23 Apr 2025 07:51:29 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286302 Bug ID: 286302 Summary: avahi-daemon Fatal trap 12: page fault while in kernel mode Product: Base System Version: 14.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: lists@freshlybrewed.coffee I've seen the below fault and panic several times on an amd64 host running many vnet jails and some bhyve vms. Panic is triggered on restarting a jailed avahi-daemon, or on restarting the jail containing it. I'm using iocage for jail management. It's not reliably reproduceable, i.e. it doesn't happen everytime I restart the jail or avahi-daemon Fatal trap 12: page fault while in kernel mode cpuid = 14; apic id = 34 fault virtual address = 0x28 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80d596fe stack pointer = 0x28:0xfffffe01cf26db50 frame pointer = 0x28:0xfffffe01cf26dbb0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 21985 (avahi-daemon) rdi: fffff802e9838100 rsi: 0000000000000000 rdx: 0000000000000001 rcx: 0000000000000001 r8: 0000000000000000 r9: 0000000000000000 rax: 0000000000000000 rbx: fffff80830c35000 rbp: fffffe01cf26dbb0 r10: 0000000824abf43a r11: fffff80830c35520 r12: fffff802e9838100 r13: 0000000000000000 r14: 0000000000000000 r15: fffff8078e4dd800 trap number = 12 panic: page fault cpuid = 14 time = 1745393475 KDB: stack backtrace: #0 0xffffffff80b8b88d at kdb_backtrace+0x5d #1 0xffffffff80b3dc11 at vpanic+0x131 #2 0xffffffff80b3dad3 at panic+0x43 #3 0xffffffff81025a0b at trap_fatal+0x40b #4 0xffffffff81025a56 at trap_pfault+0x46 #5 0xffffffff80ffc388 at calltrap+0x8 #6 0xffffffff80d481cf at in6_leavegroup_locked+0x8f #7 0xffffffff80d48952 at ip6_freemoptions+0x142 #8 0xffffffff80cf9b29 at in_pcbfree+0x329 #9 0xffffffff80be2b39 at sorele_locked+0x89 #10 0xffffffff80be375a at soclose+0x14a #11 0xffffffff80adb8f1 at _fdrop+0x11 #12 0xffffffff80adeb5a at closef+0x24a #13 0xffffffff80ae2bd8 at closefp_impl+0x58 #14 0xffffffff810262be at amd64_syscall+0x10e #15 0xffffffff80ffcc9b at fast_syscall_common+0xf8 -- You are receiving this mail because: You are the assignee for the bug.