Crashdump 2.5.2-RELEASE

fthomasr

Hello. This unit has been very reliable for years and I recently upgraded from the 2.4.x builds and this has happened I think twice. Thanks for your help in advance.
info.0
textdump.tar.0
info.1.0
textdump.tar.1.0

jimp

The backtrace of both panics is the same but it's not one I recognize. Though it is fairly deep in kernel memory handling and not in a place likely to have a bug.

Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address	= 0x0
fault code		= supervisor write data, page not present
instruction pointer	= 0x20:0xffffffff81202d5d
stack pointer	        = 0x28:0xfffffe001d06f900
frame pointer	        = 0x28:0xfffffe001d06fcb0
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		= 21 (dom0)
trap number		= 12
panic: page fault
cpuid = 1
time = 1627446085
KDB: enter: panic

db:0:kdb.enter.default>  bt
Tracing pid 21 tid 100129 td 0xfffff80007357740
kdb_enter() at kdb_enter+0x37/frame 0xfffffe001d06f5c0
vpanic() at vpanic+0x197/frame 0xfffffe001d06f610
panic() at panic+0x43/frame 0xfffffe001d06f670
trap_fatal() at trap_fatal+0x391/frame 0xfffffe001d06f6d0
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe001d06f720
trap() at trap+0x286/frame 0xfffffe001d06f830
calltrap() at calltrap+0x8/frame 0xfffffe001d06f830
--- trap 0xc, rip = 0xffffffff81202d5d, rsp = 0xfffffe001d06f900, rbp = 0xfffffe001d06fcb0 ---
vm_pageout_worker() at vm_pageout_worker+0xecd/frame 0xfffffe001d06fcb0
vm_pageout() at vm_pageout+0x193/frame 0xfffffe001d06fcf0
fork_exit() at fork_exit+0x7e/frame 0xfffffe001d06fd30
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe001d06fd30
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---

Difficult to say what it might be based on that alone. Any other symptoms before it crashes? Is there something in particular it's doing when the crash happens?

fthomasr

@jimp Hey Jim. No it's only after I log into it randomly to make changes when it pops up and tells me it has crashed. I mean it's still running fine when I log into it. Should I format and reinstall from scratch using 2.5.2 installer since this was an 2.4.x upgrade? Replace the SSD?

Thanks.

jimp

The error doesn't lead me to think it's disk related, so a reinstall or new SSD wouldn't likely make a difference. It could be something else in hardware, but typically hardware-related crashes are more random than this. May still be worth running a memory and CPU test on it if you can.

A fresh install wouldn't hurt anything, so you can do that if you like, but I'm not confident it would be relevant here.

fthomasr

@jimp Well what do you know... I restarted it and ran the built in memtest and it's memory error city. Thanks for the tip! I'll chunk it.