[Bug 262894] Kernel Panic (page fault) with 13.1-BETA2 in g_eli & httpd

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 28 Mar 2022 17:15:46 UTC

            Bug ID: 262894
           Summary: Kernel Panic (page fault) with 13.1-BETA2 in g_eli &
           Product: Base System
           Version: 13.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: mathias.kraut@gmx.de

Created attachment 232788
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232788&action=edit
crash dumps

updated from FreeBSD 12 to 13.1. 
Running in a HyperV virtual machine on a Xeon D 1518. 32GB ECC Memory. Passing
a HBA to the VM (LSI).

13.1 B2 crashing ~1x a day especially on moderate load. 
12 running stable for years.

HW, VM host and tunables unchanged. 

I wonder a bit because many seem to have panics in FreeBSD 13 and I also have
one in httpd and two in geli within three days. See the /data/crash  dumps

Thanks for your help


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0xfffff80e00000004
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80f1c50d
stack pointer           = 0x28:0xfffffe0144d3cc00
frame pointer           = 0x28:0xfffffe0144d3cca0
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         = 2653 (g_eli[2] gptid/e2d4)
trap number             = 12
panic: page fault
cpuid = 2
time = 1648393340
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0144d3c9c0
vpanic() at vpanic+0x17f/frame 0xfffffe0144d3ca10
panic() at panic+0x43/frame 0xfffffe0144d3ca70
trap_fatal() at trap_fatal+0x385/frame 0xfffffe0144d3cad0
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe0144d3cb30
calltrap() at calltrap+0x8/frame 0xfffffe0144d3cb30
--- trap 0xc, rip = 0xffffffff80f1c50d, rsp = 0xfffffe0144d3cc00, rbp =
0xfffffe0144d3cca0 ---
aesni_crypt_xts() at aesni_crypt_xts+0x17d/frame 0xfffffe0144d3cca0
aesni_decrypt_xts() at aesni_decrypt_xts+0xe/frame 0xfffffe0144d3ccc0
aesni_cipher_crypt() at aesni_cipher_crypt+0x2f1/frame 0xfffffe0144d3cd70
aesni_process() at aesni_process+0x159/frame 0xfffffe0144d3cdc0
crypto_dispatch() at crypto_dispatch+0x118/frame 0xfffffe0144d3cdf0
g_eli_crypto_run() at g_eli_crypto_run+0x178/frame 0xfffffe0144d3ce90
g_eli_worker() at g_eli_worker+0x328/frame 0xfffffe0144d3cef0
fork_exit() at fork_exit+0x7e/frame 0xfffffe0144d3cf30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0144d3cf30
--- trap 0x80af5f94, rip = 0, rsp = 0, rbp = 0 ---
KDB: enter: panic

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