Date: Fri, 28 Dec 2018 12:34:54 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: =?UTF-8?B?SnVyaWogS292YcSNacSN?= <jurij.kovacic@ocpea.com>, freebsd-stable@freebsd.org Subject: Re: Kernel panic on 11.2-RELEASE-p7 Message-ID: <67af7bf5-5fc7-a697-0055-d3518c93b86e@FreeBSD.org> In-Reply-To: <CADEDvuAFUhaxc0YCbPqGrk8-LvwnE2-1tPfCa3B=93AV_hnpDA@mail.gmail.com> References: <CADEDvuBa=oEO_4wF-Su3q=tuBNZnn6k3429xwG3eiOUZQyWmsw@mail.gmail.com> <CADEDvuAFUhaxc0YCbPqGrk8-LvwnE2-1tPfCa3B=93AV_hnpDA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67af7bf5-5fc7-a697-0055-d3518c93b86e>