[Bug 234042] panics on 12.0-RELEASE: swi4: clock(0), instruction pointer 0x0
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Dec 15 20:12:57 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234042
Bug ID: 234042
Summary: panics on 12.0-RELEASE: swi4: clock(0), instruction
pointer 0x0
Product: Base System
Version: 12.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: mandrews at bit0.com
Created attachment 200136
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200136&action=edit
dmesg.boot
Since updating from 11.2 to 12.0-RELEASE, two of our systems have given this
same panic a total of three times in the last 24 hours. Usually the
instruction pointer is 0, but not always:
---
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x0
fault code = supervisor read instruction, page not present
instruction pointer = 0x20:0x0
stack pointer = 0x28:0xfffffe0000470a78
frame pointer = 0x28:0xfffffe0000470b20
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 = 12 (swi4: clock (0))
trap number = 12
panic: page fault
cpuid = 1
time = 1544894686
KDB: stack backtrace:
#0 0xffffffff80be7977 at kdb_backtrace+0x67
#1 0xffffffff80b9b563 at vpanic+0x1a3
#2 0xffffffff80b9b3b3 at panic+0x43
#3 0xffffffff8107496f at trap_fatal+0x35f
#4 0xffffffff810749c9 at trap_pfault+0x49
#5 0xffffffff81073fee at trap+0x29e
#6 0xffffffff8104f1d5 at calltrap+0x8
#7 0xffffffff80bb5a39 at softclock+0x79
#8 0xffffffff80b5ee17 at ithread_loop+0x1a7
#9 0xffffffff80b5bf33 at fork_exit+0x83
#10 0xffffffff810501be at fork_trampoline+0xe
Uptime: 1d18h48m53s
---
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x158
fault code = supervisor read instruction, page not present
instruction pointer = 0x20:0x158
stack pointer = 0x28:0xfffffe0000470a78
frame pointer = 0x28:0xfffffe0000470b20
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 = 12 (swi4: clock (0))
trap number = 12
panic: page fault
cpuid = 0
time = 1544781943
KDB: stack backtrace:
#0 0xffffffff80be7977 at kdb_backtrace+0x67
#1 0xffffffff80b9b563 at vpanic+0x1a3
#2 0xffffffff80b9b3b3 at panic+0x43
#3 0xffffffff8107496f at trap_fatal+0x35f
#4 0xffffffff810749c9 at trap_pfault+0x49
#5 0xffffffff81073fee at trap+0x29e
#6 0xffffffff8104f1d5 at calltrap+0x8
#7 0xffffffff80bb5a39 at softclock+0x79
#8 0xffffffff80b5ee17 at ithread_loop+0x1a7
#9 0xffffffff80b5bf33 at fork_exit+0x83
#10 0xffffffff810501be at fork_trampoline+0xe
Uptime: 11h29m48s
---
Fatal trap 12: page fault while in kernel mode
cpuid = 6; apic id = 14
fault virtual address = 0x0
fault code = supervisor read instruction, page not present
instruction pointer = 0x20:0x0
stack pointer = 0x0:0xfffffe0000470a78
frame pointer = 0x0:0xfffffe0000470b20
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 = 12 (swi4: clock (0))
trap number = 12
panic: page fault
cpuid = 6
time = 1544887543
KDB: stack backtrace:
#0 0xffffffff80be7977 at kdb_backtrace+0x67
#1 0xffffffff80b9b563 at vpanic+0x1a3
#2 0xffffffff80b9b3b3 at panic+0x43
#3 0xffffffff8107496f at trap_fatal+0x35f
#4 0xffffffff810749c9 at trap_pfault+0x49
#5 0xffffffff81073fee at trap+0x29e
#6 0xffffffff8104f1d5 at calltrap+0x8
#7 0xffffffff80bb5a39 at softclock+0x79
#8 0xffffffff80b5ee17 at ithread_loop+0x1a7
#9 0xffffffff80b5bf33 at fork_exit+0x83
#10 0xffffffff810501be at fork_trampoline+0xe
Uptime: 1d5h17m30s
---
Both systems are identical (a bit old, though) Supermicro 5016T-MTFB.
dmesg.boot from one of them is attached.
I don't have dumps of these, for some reason -- I'm looking into why so I can
capture the next one.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list