Kernel panic, stable/12 r341604, swapon -a in SU mode, geli encrypted swap, Chelsio T6225-CR, and ccr(4)

[Navdeep Parhar]

Can you please file a bug at https://bugs.freebsd.org/bugzilla/ and
assign it to me?

Regards,
Navdeep

On 12/6/18 4:02 AM, Trond Endrestøl wrote:
> After booting stable/12 r341604, running a custom kernel including 
> cxgbe(4), cxgbev(4), and ccr(4), and running swapon -a in SU mode:
> 
> GEOM_ELI: Device gpt/swap0.eli created.
> GEOM_ELI: Encryption: AES-XTS 256
> GEOM_ELI:     Crypto: hardware
> 
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 3; apic id = 06
> fault virtual address   = 0x0
> fault code              = supervisor write data, page not present
> instruction pointer     = 0x20:0xffffffff805be1b2
> stack pointer           = 0x28:0xfffffe00a6253770
> frame pointer           = 0x28:0xfffffe00a6253770
> 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         = 65 (g_eli[3] gpt/swap0)
> trap number             = 12
> panic: page fault
> cpuid = 3
> time = 1544087308
> KDB: stack backtrace:
> db_trace_self_wrapper() at 0xffffffff8055d9eb = db_trace_self_wrapper+0x2b/frame 0xfffffe00a6253420
> vpanic() at 0xffffffff808754d3 = vpanic+0x1a3/frame 0xfffffe00a6253480
> panic() at 0xffffffff80875323 = panic+0x43/frame 0xfffffe00a62534e0
> trap_fatal() at 0xffffffff80bd745f = trap_fatal+0x35f/frame 0xfffffe00a6253530
> trap_pfault() at 0xffffffff80bd74b9 = trap_pfault+0x49/frame 0xfffffe00a4b7f590
> trap() at 0xffffffff80bd6ade = trap+0x29e/frame 0xfffffe00a4b7f6a0
> calltrap() at 0xffffffff80bb3935 = calltrap+0x8/frame 0xfffffe00a4b7f6a0
> --- trap 0xc, rip = 0xffffffff805be1b2, rsp = 0xfffffe00a4b7f770, rbp = 0xfffffe00a4b7f770
> t4_wrq_tx_locked() at 0xffffffff805be1b2 = t4_wrq_tx_locked+0x12/frame 0xfffffe00a6253770
> ccr_process() at 0xffffffff805e3fc3 = ccr_process+0x1953/frame 0xfffffe00a4b7f970
> crypto_dispatch() at 0xffffffff80ae3fa4 = crypto_dispatch+0x144/frame 0xfffffe00a4b7f9b0
> g_eli_crypto_run() at 0xffffffff807b5cb3 = g_eli_crypto_run+0x273/frame 0xfffffe00a4b7fa10
> g_eli_worker() at 0xffffffff807aebc8 = g_eli_worker+0x3c8/frame 0xfffffe00a4b7fa70
> fork_exit() at 0xffffffff80834d93 = fork_exit+0x83/frame 0xfffffe00a4b7fab0
> fork_trampoline() at 0xffffffff80bb491e = fork_trampoline+0xe/frame 0xfffffe00a4b7fab0
> --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
> Uptime: 14s
> Automatic reboot in 15 seconds - press a key on the console to abort
> --> Press a key on the console to reboot,
> 
> The Chelsio NIC is a T6225-CR.
> 
> Kernel config is 
> https://ximalas.info/~trond/create-zfs/canmount/ENTERPRISE-amd64-stable-12
> 
> I tried stable/12 r341623 with ccr(4) removed from the kernel, and I 
> had no problems engaging geli encrypted swap in SU mode nor in normal 
> mode.
> 
> Has anyone else tried ccr(4) on recent stable/12?
> Are we discouraged from using ccr(4)?
> I was hoping to take advantage of the crypto accelerator.
>