Re: frequent panics from current built today

This problem is almost certainly my fault, due to r349393.  Once I
learned of the problem and verified that I was responsible, I reverted
that change with r349405.

I apologize for the multiple inconveniences I have caused.

Doug Moore


> ----- Forwarded message from Pete Wright <pete_at_nomadlogic.org> -----
>
> Date: Tue, 25 Jun 2019 19:09:07 -0700
> From: Pete Wright <pete_at_nomadlogic.org>
> To: FreeBSD Current <freebsd-current_at_freebsd.org>
> Subject: frequent panics from current built today
>
> hello - i've had a system panic multiple times after rebuilding world/kernel
> today.  here's my info:
> FreeBSD topanga 13.0-CURRENT FreeBSD 13.0-CURRENT 2474a68216f(master)
> GENERIC-NODEBUG  amd64
>
> Looking at two of the panic texts I see this:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address   = 0x52
> fault code              = supervisor read data, page not present
> instruction pointer     = 0x20:0xffffffff80f47f54
> stack pointer           = 0x0:0xfffffe0122e4a6d0
> frame pointer           = 0x0:0xfffffe0122e4a7b0
> 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         = 69399 (java)
> trap number             = 12
> panic: page fault
> cpuid = 1
> time = 1561514025
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0122e4a380
> vpanic() at vpanic+0x19d/frame 0xfffffe0122e4a3d0
> panic() at panic+0x43/frame 0xfffffe0122e4a430
> trap_fatal() at trap_fatal+0x39c/frame 0xfffffe0122e4a490
> trap_pfault() at trap_pfault+0x49/frame 0xfffffe0122e4a4f0
> trap() at trap+0x29f/frame 0xfffffe0122e4a600
> calltrap() at calltrap+0x8/frame 0xfffffe0122e4a600
> --- trap 0xc, rip = 0xffffffff80f47f54, rsp = 0xfffffe0122e4a6d0, rbp =
> 0xfffffe0122e4a7b0 ---
> vm_map_lookup() at vm_map_lookup+0x2a4/frame 0xfffffe0122e4a7b0
> vm_fault_hold() at vm_fault_hold+0x72/frame 0xfffffe0122e4a900
> vm_fault() at vm_fault+0x60/frame 0xfffffe0122e4a940
> trap_pfault() at trap_pfault+0x164/frame 0xfffffe0122e4a9a0
> trap() at trap+0x42b/frame 0xfffffe0122e4aab0
> calltrap() at calltrap+0x8/frame 0xfffffe0122e4aab0
> --- trap 0xc, rip = 0x41f695e0, rsp = 0x7fffdfff0738, rbp = 0x7fffdfff07b0 ---
> KDB: enter: panic
>
> __curthread () at /usr/home/pete/git/freebsd/sys/amd64/include/pcpu.h:246
> 246             __asm("movq %%gs:%P1,%0" : "=r" (td) : "n"
> (OFFSETOF_CURTHREAD));
>
>
> I have usable core files and can post any additional debug info needed.  The
> first crash happened when launching chrome, the second (which is what the
> above text is from) happened when I was running a java process in a jail.  Has
> anyone else seen this?
>
> Cheers,
> -pete
>