Kernel panic on 11.2-RELEASE-p7

Jurij Kovačič jurij.kovacic at ocpea.com
Fri Dec 28 11:08:00 UTC 2018


Hi Andriy,

Thank you for your reply.

Is what you are suggesting I build and install GENERIC kernel WITH debug
symbols?

I presume I just update the sources to 11.2 release and build and install
the GENERIC kernel with added

makeoptions	DEBUG=-g ?


Kind regards,

Jurij



On Fri, Dec 28, 2018 at 11:34 AM Andriy Gapon <avg at freebsd.org> wrote:

> On 28/12/2018 12:07, Jurij Kovačič via freebsd-stable wrote:
> > 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>
>
> This is useless because you do not have debug symbols for the kernel.
>
> > Does anyone have any idea how we can go about discovering the cause for
> > this? We would appreciate any suggestion ...
>
>
>
> --
> Andriy Gapon
>


More information about the freebsd-stable mailing list