https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285813
Andrey V. Elsukov <a...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |a...@freebsd.org
--- Comment #12 from Andrey V. Elsukov <a...@freebsd.org> ---
(In reply to Mark Johnston from comment #6)
I saw similar panic and it was related with ifconfig destroy+create for
interface reconfiguration. But last time when it was happened, panic has been
occurred after ~15 minutes after reconfiguration was done.
It is 13.0:
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 04
fault virtual address = 0x100000390
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80cd32cb
stack pointer = 0x28:0xfffffe00df5d79e0
frame pointer = 0x28:0xfffffe00df5d7a50
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 = 12 (swi4: clock (0))
trap number = 12
panic: page fault
cpuid = 2
time = 1743588228
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00df5d76a0
vpanic() at vpanic+0x182/frame 0xfffffe00df5d76f0
panic() at panic+0x43/frame 0xfffffe00df5d7750
trap_fatal() at trap_fatal+0x387/frame 0xfffffe00df5d77b0
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00df5d7800
trap() at trap+0x271/frame 0xfffffe00df5d7910
calltrap() at calltrap+0x8/frame 0xfffffe00df5d7910
--- trap 0xc, rip = 0xffffffff80cd32cb, rsp = 0xfffffe00df5d79e0, rbp =
0xfffffe00df5d7a50 ---
arptimer() at arptimer+0x6b/frame 0xfffffe00df5d7a50
softclock_call_cc() at softclock_call_cc+0x139/frame 0xfffffe00df5d7b00
softclock() at softclock+0x79/frame 0xfffffe00df5d7b20
ithread_loop() at ithread_loop+0x24d/frame 0xfffffe00df5d7bb0
fork_exit() at fork_exit+0x7e/frame 0xfffffe00df5d7bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00df5d7bf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
Uptime: 15d14h40m59s
--
You are receiving this mail because:
You are the assignee for the bug.
