Actions
Bug #9579
closed
Upgrade from 2.4.4_2 > 2.4.4_3 failed upon reboot
Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/09/2019
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4-p3
Affected Architecture:
amd64
Description
Recently upgraded my stable 2.4.4_2 instance (on physical hardware not VM) to 2.4.4_3 which didn't work. Rebuilt from 2.4.4_1 then upgraded to 2.4.4_3, using config recovery, and first login into the dashboard produced error reports.
Both textdump & info.0 attached.
Files
Updated by Jim Pingle about 6 years ago
- Status changed from New to Not a Bug
Looks more like a hardware issue to me.
db:0:kdb.enter.default> show pcpu cpuid = 2 dynamic pcpu = 0xfffffe0170ff5380 curthread = 0xfffff800084e8620: pid 768 "logger" curpcb = 0xfffffe00f9de3b80 fpcurthread = 0xfffff800084e8620: pid 768 "logger" idlethread = 0xfffff8000483f000: tid 100005 "idle: cpu2" curpmap = 0xfffff80008f9c138 tssp = 0xffffffff82bb68e0 commontssp = 0xffffffff82bb68e0 rsp0 = 0xfffffe00f9de3b80 gs32p = 0xffffffff82bbd138 ldt = 0xffffffff82bbd178 tss = 0xffffffff82bbd168 db:0:kdb.enter.default> bt Tracing pid 768 tid 100428 td 0xfffff800084e8620 copyout() at copyout+0x3e/frame 0xfffffe00f9de3800 uiomove_faultflag() at uiomove_faultflag+0x10c/frame 0xfffffe00f9de3840 pipe_read() at pipe_read+0x214/frame 0xfffffe00f9de38a0 dofileread() at dofileread+0xba/frame 0xfffffe00f9de38e0 kern_readv() at kern_readv+0x68/frame 0xfffffe00f9de3930 sys_read() at sys_read+0x86/frame 0xfffffe00f9de3980 amd64_syscall() at amd64_syscall+0xa38/frame 0xfffffe00f9de3ab0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00f9de3ab0 --- syscall (3, FreeBSD ELF64, sys_read), rip = 0x800970d4a, rsp = 0x7fffffffe728, rbp = 0x7fffffffe740 ---
<118>Launching the init system...Updating CPU Microcode...
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0x800e29000
fault code = supervisor write data, page not present
instruction pointer = 0x20:0xffffffff81189dde
stack pointer = 0x28:0xfffffe00f9de3800
frame pointer = 0x28:0xfffffe00f9de3800
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 = 768 (logger)
Post on the forum for assistance. There may be something you can do (update BIOS or similar), but that's too deep in hardware operations for it to be pfSense.
Updated by Dean McBride about 6 years ago
Jim Pingle wrote:
Looks more like a hardware issue to me.
Didn't do the same thing on p1 or p2 with the only difference being a console upgrade to p3. Will post over there
Actions