Date: Fri, 6 Dec 2019 18:39:41 +0200 From: Christos Chatzaras <chris@cretaforce.gr> To: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: kernel panic Message-ID: <6014CAB6-4827-4D6D-B5DD-A9E901047F69@cretaforce.gr>
next in thread | raw e-mail | index | archive | help
Today and yesterday I had a server crash. The server runs FreeBSD 12.1 = without the last "FreeBSD-SA-19:25.mcepsc" patch. Today I got this: Dec 6 18:27:18 server36.example.com kernel: Fatal trap 12: page fault = while in kernel mode Dec 6 18:27:18 server36.example.com kernel: cpuid =3D 3; apic id =3D 03 Dec 6 18:27:18 server36.example.com kernel: fault virtual address#011=3D = 0xffffffff82fb8f38 Dec 6 18:27:18 server36.example.com kernel: fault code#011#011=3D = supervisor read data, page not present Dec 6 18:27:18 server36.example.com kernel: instruction pointer#011=3D = 0x20:0xffffffff810954b6 Dec 6 18:27:18 server36.example.com kernel: stack pointer#011 =3D = 0x0:0xfffffe00c3c9f600 Dec 6 18:27:18 server36.example.com kernel: frame pointer#011 =3D = 0x0:0xfffffe00c3c9f6b0 Dec 6 18:27:18 server36.example.com kernel: code segment#011#011=3D = base 0x0, limit 0xfffff, type 0x1b Dec 6 18:27:18 server36.example.com kernel: #011#011#011=3D DPL 0, pres = 1, long 1, def32 0, gran 1 Dec 6 18:27:18 server36.example.com kernel: processor eflags#011=3D = interrupt enabled, resume, IOPL =3D 0 Dec 6 18:27:18 server36.example.com kernel: current process#011#011=3D = 86140 (nginx) Dec 6 18:27:18 server36.example.com kernel: trap number#011#011=3D 12 Dec 6 18:27:18 server36.example.com kernel: panic: page fault Dec 6 18:27:18 server36.example.com kernel: cpuid =3D 3 Dec 6 18:27:18 server36.example.com kernel: time =3D 1575649514 Dec 6 18:27:18 server36.example.com kernel: KDB: stack backtrace: Dec 6 18:27:18 server36.example.com kernel: #0 0xffffffff80c1d207 at = kdb_backtrace+0x67 Dec 6 18:27:18 server36.example.com kernel: #1 0xffffffff80bd053d at = vpanic+0x19d Dec 6 18:27:18 server36.example.com kernel: #2 0xffffffff80bd0393 at = panic+0x43 Dec 6 18:27:18 server36.example.com kernel: #3 0xffffffff810a7d2c at = trap_fatal+0x39c Dec 6 18:27:18 server36.example.com kernel: #4 0xffffffff810a7d79 at = trap_pfault+0x49 Dec 6 18:27:18 server36.example.com kernel: #5 0xffffffff810a736f at = trap+0x29f Dec 6 18:27:18 server36.example.com kernel: #6 0xffffffff8108132c at = calltrap+0x8 Dec 6 18:27:18 server36.example.com kernel: #7 0xffffffff80f0c340 at = vm_fault_hold+0x1b90 Dec 6 18:27:18 server36.example.com kernel: #8 0xffffffff80f0a760 at = vm_fault+0x60 Dec 6 18:27:18 server36.example.com kernel: #9 0xffffffff810a7e94 at = trap_pfault+0x164 Dec 6 18:27:18 server36.example.com kernel: #10 0xffffffff810a74fb at = trap+0x42b Dec 6 18:27:18 server36.example.com kernel: #11 0xffffffff8108132c at = calltrap+0x8 Do you think it's hardware related?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6014CAB6-4827-4D6D-B5DD-A9E901047F69>