Kernel panic on 11.2-RELEASE-p7

[Jurij Kovačič]

Dear list,

This morning the server mentioned in my previous e-mail (Freebsd
11.2-RELEASE-p7 with GENERIC kernel, ZFS root) experienced another kernel
panic:

Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer    = 0x20:0xffffffff82299013
stack pointer            = 0x28:0xfffffe0352893ad0
frame pointer            = 0x28:0xfffffe0352893b10
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        = 9 (dbuf_evict_thread)
trap number        = 9
panic: general protection fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff80b3d577 at kdb_backtrace+0x67
#1 0xffffffff80af6b17 at vpanic+0x177
#2 0xffffffff80af6993 at panic+0x43
#3 0xffffffff80f77fdf at trap_fatal+0x35f
#4 0xffffffff80f7759e at trap+0x5e
#5 0xffffffff80f5808c at calltrap+0x8
#6 0xffffffff8229c049 at dbuf_evict_one+0xe9
#7 0xffffffff82297a15 at dbuf_evict_thread+0x1a5
#8 0xffffffff80aba093 at fork_exit+0x83
#9 0xffffffff80f58fae at fork_trampoline+0xe

I have used the "crashinfo" utility to (again) generate the text file which
is available at this URL: http://www.ocpea.com/dump/core-2.txt
<http://www.ocpea.com/dump/core.txt>

Does anyone have any idea how we can go about discovering the cause for
this? We would appreciate any suggestion ...

Kind regards,
Jurij Kovacic


On Tue, Dec 25, 2018 at 7:57 AM Jurij Kovačič <jurij.kovacic at ocpea.com>
wrote:

> Dear list,
>
> I hope I am posting this to the correct list - if not, I apologize (and
> please advise where to post this instead).
>
> Today I experienced a kernel panic on a (physical) server, running Freebsd
> 11.2-RELEASE-p7 with GENERIC kernel, ZFS root:
>
> Fatal trap 9: general protection fault while in kernel mode
> cpuid = 0; apic id = 00
> instruction pointer    = 0x20:0xffffffff82299013
> stack pointer            = 0x28:0xfffffe0352893ad0
> frame pointer            = 0x28:0xfffffe0352893b10
> 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        = 9 (dbuf_evict_thread)
> trap number        = 9
> panic: general protection fault
> cpuid = 0
> KDB: stack backtrace:
> #0 0xffffffff80b3d577 at kdb_backtrace+0x67
> #1 0xffffffff80af6b17 at vpanic+0x177
> #2 0xffffffff80af6993 at panic+0x43
> #3 0xffffffff80f77fdf at trap_fatal+0x35f
> #4 0xffffffff80f7759e at trap+0x5e
> #5 0xffffffff80f5808c at calltrap+0x8
> #6 0xffffffff8229c049 at dbuf_evict_one+0xe9
> #7 0xffffffff82297a15 at dbuf_evict_thread+0x1a5
> #8 0xffffffff80aba093 at fork_exit+0x83
> #9 0xffffffff80f58fae at fork_trampoline+0xe
>
> I have used "crashinfo" utility to generate the text file which is
> available at this URL: http://www.ocpea.com/dump/core.txt
>
> At the time of the crash, the server was probably under more intensive I/O
> load (scheduled backup with rsync).
>
> This is a production server, so naturally, all advice is deeply
> appreciated. :)
>
> Kind regards,
> Jurij
>