https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262894

--- Comment #4 from Krautmaster <mathias.kr...@gmx.de> ---
@Mark Johnston 
I can report that the same machine back with 12.2 runs fine again, any load, no
crash so far (like it did before the 13.1 update). Wonder what may have caused
the httpd and geli page fault, maybe the same root cause.

See the other crash in the row of three in the attachment of this ticket

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x10
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80ac5384
stack pointer           = 0x28:0xfffffe015bedbc80
frame pointer           = 0x28:0xfffffe015bedbcc0
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         = 37468 (httpd)
trap number             = 12
panic: page fault
cpuid = 0
time = 1648160238
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe015bedba40
vpanic() at vpanic+0x17f/frame 0xfffffe015bedba90
panic() at panic+0x43/frame 0xfffffe015bedbaf0
trap_fatal() at trap_fatal+0x385/frame 0xfffffe015bedbb50
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe015bedbbb0
calltrap() at calltrap+0x8/frame 0xfffffe015bedbbb0
--- trap 0xc, rip = 0xffffffff80ac5384, rsp = 0xfffffe015bedbc80, rbp =
0xfffffe015bedbcc0 ---
kqueue_drain() at kqueue_drain+0x134/frame 0xfffffe015bedbcc0
kqueue_close() at kqueue_close+0x42/frame 0xfffffe015bedbd10
_fdrop() at _fdrop+0x11/frame 0xfffffe015bedbd30
closef() at closef+0x24b/frame 0xfffffe015bedbdc0
closefp() at closefp+0x80/frame 0xfffffe015bedbe00
amd64_syscall() at amd64_syscall+0x10c/frame 0xfffffe015bedbf30
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe015bedbf30
--- syscall (6, FreeBSD ELF64, sys_close), rip = 0x8007f591a, rsp =
0x7fffffffe808, rbp = 0x7fffffffe820 ---
KDB: enter: panic

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to