More info on crash report?
-
Hello,
I recently (2016 December 5, ~11:20 a.m. EST) submitted a crash report from 24.239.28.10. It appears that my installation of pfSense crashed over the weekend. Is there anyone who could take a look at the crash report and let me know if I should submit a bug report for this issue, or if there is something else going on?
Thank you!
James Dietrich
-
I have to say, it looks like hardware. Random processes are crashing with signal 11 which is never a good sign, usually RAM/CPU/Heat to blame.
<6>pid 71204 (awk), uid 0: exited on signal 11 (core dumped) <6>pid 70866 (cat), uid 0: exited on signal 11 (core dumped) <5>xl0: link state changed to DOWN <5>xl0: link state changed to UP <5>xl0: link state changed to DOWN <5>xl0: link state changed to UP Fatal trap 1: privileged instruction fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff80bc27e9 stack pointer = 0x28:0xfffffe003cdb5940 frame pointer = 0x28:0xfffffe003cdb5ad0 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 = 72133 (rrdtool)db:0:kdb.enter.default> show pcpu cpuid = 0 dynamic pcpu = 0x531500 curthread = 0xfffff800037744b0: pid 72133 "rrdtool" curpcb = 0xfffffe003cdb5cc0 fpcurthread = none idlethread = 0xfffff800032f5000: tid 100003 "idle: cpu0" curpmap = 0xfffff80003d899f8 tssp = 0xffffffff82113490 commontssp = 0xffffffff82113490 rsp0 = 0xfffffe003cdb5cc0 gs32p = 0xffffffff82114ee8 ldt = 0xffffffff82114f28 tss = 0xffffffff82114f18 db:0:kdb.enter.default> bt Tracing pid 72133 tid 100062 td 0xfffff800037744b0 vn_seek() at vn_seek+0x2a9/frame 0xfffffe003cdb5ad0 amd64_syscall() at amd64_syscall+0x40f/frame 0xfffffe003cdb5bf0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe003cdb5bf0 --- syscall (499, FreeBSD ELF64, sys_openat), rip = 0x80061542a, rsp = 0x7fffffffd968, rbp = 0x7fffffffda40 ---That call is very deep in the kernel, highly unlikely to be a bug of any kind. It is a filesystem operation, so there's a chance it's the disk and/or controller.
This is also odd:
g_dev_taste: make_dev_p() failed (gp->name=reiserfs//, error=22)Could it be that this drive used to contain a Linux installation but it was not fully cleaned up?
I'd put a new drive in there and consider this one suspicious. At the very least, backup the config and dd wipe the entire drive with zeros and then reinstall.
-
Thank you for taking the time to look at my crash report and write a thoughtful reply.
Last night it crashed again, and today I ended up putting in a different motherboard/CPU/RAM. So far everything looks good; hopefully it stays that way.
James
