Date: Sun, 10 Jul 2016 05:06:40 +0300 From: Andrey Chernov <ache@freebsd.org> To: Matthew Macy <mmacy@nextbsd.org> Cc: "current@freebsd.org" <current@FreeBSD.org> Subject: Re: Recent -current stable panic at later boot stage Message-ID: <9775fe3b-db09-7b11-779f-fa2ae13ce2b3@freebsd.org> In-Reply-To: <155d26ce8c4.12248bbba219469.8811983805604406181@nextbsd.org> References: <378f847e-3257-19f0-2cf8-cd6319db5e06@freebsd.org> <8c432d68-a3c8-2f39-8429-f1fe920d002b@freebsd.org> <155d26ce8c4.12248bbba219469.8811983805604406181@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10.07.2016 4:30, Matthew Macy wrote: > > > > ---- On Sat, 09 Jul 2016 18:19:57 -0700 Andrey Chernov <ache@freebsd.org> wrote ---- > > BTW, it never happens with 11-ALPHA3 even with world build for 12. > > > > On 09.07.2016 22:06, Andrey Chernov wrote: > > > SCHED_ULE used. I have textdump only. Interesting parts: > > > <118>Starting syslogd. > > > kernel trap 9 with interrupts disabled > > > > > > Fatal trap 9: general protection fault while in kernel mode > > > cpuid = 7; apic id = 07 > > > instruction pointer = 0x20:0xffffffff806b2585 > > > stack pointer = 0x28:0xfffffe022ccce8d0 > > > frame pointer = 0x28:0xfffffe022ccce950 > > > code segment = base 0x0, limit 0xfffff, type 0x1b > > > = DPL 0, pres 1, long 1, def32 0, gran 1 > > > processor eflags = resume, IOPL = 0 > > > current process = 10 (idle: cpu7) > > > > > > It happens at amd64/amd64/cpu_switch.S:ld_ldt: lldt %ax > > > > > > db> bt > > > > > > Tracing pid 10 tid 100009 td 0xfffff80002292000 > > > ld_ldt() at ld_ldt/frame 0xfffffe022ccce8e0 > > > sched_switch() at sched_switch+0x51d/frame 0xfffffe022ccce950 > > > mi_switch() at mi_switch+0x156/frame 0xfffffe022ccce980 > > > sched_idletd() at sched_idletd+0xf9/frame 0xfffffe022cccea70 > > > fork_exit() at fork_exit+0x84/frame 0xfffffe022ccceab0 > > > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe022ccceab0 > > > --- trap 0, rip = 0, rsp = 0, rbp = 0 --- > > Have their been no other stability issues on this machine? At first glance it looks like the ldt got corrupted. Is there no way to inspect that? It seems something wrong happens during incremental kernel update from 11-ALPLA3 to 12, i.e. some old kernel parts affects it. I clean all object and include files and rebuild the kernel from scratch and this panic is gone. Sorry for the noise, I should do it before reporting :(
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9775fe3b-db09-7b11-779f-fa2ae13ce2b3>