Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Dec 2018 12:31:41 +0100
From:      =?UTF-8?B?SnVyaWogS292YcSNacSN?= <jurij.kovacic@ocpea.com>
To:        Andriy Gapon <avg@freebsd.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Kernel panic on 11.2-RELEASE-p7
Message-ID:  <CADEDvuApm58djE9Ebuv%2B79q%2BDnG-SrB4deReADECZSgJjTGqXw@mail.gmail.com>
In-Reply-To: <CADEDvuDYphJvWp8o5Anc6TcA7b0A85ypWRxvSpyvLfyQ7y0hTA@mail.gmail.com>
References:  <CADEDvuBa=oEO_4wF-Su3q=tuBNZnn6k3429xwG3eiOUZQyWmsw@mail.gmail.com> <CADEDvuAFUhaxc0YCbPqGrk8-LvwnE2-1tPfCa3B=93AV_hnpDA@mail.gmail.com> <67af7bf5-5fc7-a697-0055-d3518c93b86e@FreeBSD.org> <CADEDvuDYphJvWp8o5Anc6TcA7b0A85ypWRxvSpyvLfyQ7y0hTA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Andriy,

Upon further investigation - I take it the kernel options should probably
be:
...
makeoptions    DEBUG=3D-g
options KDB
options KDB_UNATTENDED
...
?

Thank you!

Kind regards,
Jurij


On Fri, Dec 28, 2018 at 12:07 PM Jurij Kova=C4=8Di=C4=8D <jurij.kovacic@ocp=
ea.com>
wrote:

> 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=3D-g ?
>
>
> Kind regards,
>
> Jurij
>
>
>
> On Fri, Dec 28, 2018 at 11:34 AM Andriy Gapon <avg@freebsd.org> wrote:
>
>> On 28/12/2018 12:07, Jurij Kova=C4=8Di=C4=8D 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 =3D 0; apic id =3D 00
>> > instruction pointer    =3D 0x20:0xffffffff82299013
>> > stack pointer            =3D 0x28:0xfffffe0352893ad0
>> > frame pointer            =3D 0x28:0xfffffe0352893b10
>> > code segment        =3D base 0x0, limit 0xfffff, type 0x1b
>> >             =3D DPL 0, pres 1, long 1, def32 0, gran 1
>> > processor eflags    =3D interrupt enabled, resume, IOPL =3D 0
>> > current process        =3D 9 (dbuf_evict_thread)
>> > trap number        =3D 9
>> > panic: general protection fault
>> > cpuid =3D 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 fo=
r
>> > this? We would appreciate any suggestion ...
>>
>>
>>
>> --
>> Andriy Gapon
>>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADEDvuApm58djE9Ebuv%2B79q%2BDnG-SrB4deReADECZSgJjTGqXw>