[Bug 254244] panics after upgrade to stable/13-n244861-b9773574371
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Mar 12 20:03:51 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
Bug ID: 254244
Summary: panics after upgrade to stable/13-n244861-b9773574371
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: bugs at FreeBSD.org
Reporter: zarychtam at plan-b.pwste.edu.pl
Created attachment 223220
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223220&action=edit
Some messages caught by syslog
I have upgraded yesterday a bunch of machines to stable/13-n244861-b9773574371
and experience panics on them. There is no possibility to get cores at the
moment, I will work on this after the weekend. The Syslog has caught something
like a prelude to some of the panics:
Mar 12 13:33:44 opnr kernel: [6004] Fatal trap 12: page fault while in kernel
mode
Mar 12 13:33:44 opnr kernel: [6004] cpuid = 3; apic id = 06
Mar 12 13:33:44 opnr kernel: [6004] fault virtual address = 0x18
Mar 12 13:33:44 opnr kernel: [6004] fault code = supervisor read data,
page not present
Mar 12 13:33:44 opnr kernel: [6004] instruction pointer =
0x20:0xffffffff80c77c28
Mar 12 13:33:44 opnr kernel: [6004] stack pointer =
0x28:0xfffffe00c723f340
Mar 12 13:33:44 opnr kernel: [6004] frame pointer =
0x28:0xfffffe00c723f3b0
Mar 12 13:33:44 opnr kernel: [6004] code segment = base 0x0,
limit 0xfffff, type 0x1b
Mar 12 13:33:44 opnr kernel: [6004] = DPL 0, pres 1, long
1, def32 0, gran 1
Mar 12 13:33:44 opnr kernel: [6004] processor eflags = interrupt enabled,
resume, IOPL = 0
Mar 12 13:33:44 opnr kernel: [6004] current process = 0
(if_io_tqg_3)
More traces in the file attached.
Both affected machines have Atom C2758 CPU. I have been testing 13.0-STABLE on
them for a month with no issues so far. The last working build was
stable/13-n244798-05083436a6e from Sun Mar 7.
Access to the machines is limited, swap is configured on the ZFS and netdumps
not possible due to network configuration (vlan(4)s, over LACP lagg(4)).
I will try to configure the USB drive as a device to save crash dumps if such a
scenario will be possible.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list