Project

General

Profile

Actions

Bug #11676

closed

Kernel Panic with APU2 and Pfsense 2.5.0

Added by Stefan Bühler over 3 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hardware / Drivers
Target version:
-
Start date:
03/15/2021
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
amd64

Description

Hi all
I receive after upgrading to 2.5.0 Kernel Panics on APU2
with PFSense 2.5.0.

Thx in advance
admins


Files

textdump.tar (1).2 (72 KB) textdump.tar (1).2 Stefan Bühler, 03/15/2021 03:23 AM
textdump.tar (1).0 (71 KB) textdump.tar (1).0 Stefan Bühler, 03/15/2021 03:23 AM
textdump.tar (1).1 (71.5 KB) textdump.tar (1).1 Stefan Bühler, 03/15/2021 03:23 AM
info (1).0 (424 Bytes) info (1).0 Stefan Bühler, 03/15/2021 03:23 AM
info (1).1 (455 Bytes) info (1).1 Stefan Bühler, 03/15/2021 03:23 AM
info (1).2 (407 Bytes) info (1).2 Stefan Bühler, 03/15/2021 03:23 AM
Actions #1

Updated by Jim Pingle over 3 years ago

  • Status changed from New to Rejected

Each of those panics has a completely different backtrace, and combined with the errors in the message buffer, I'm inclined to think it's a hardware problem of some sort, or environmental (heat, power, etc) and not a software issue.

Post on the forum for further discussion.

Panic 1:

<6>pid 19708 (php-fpm), jid 0, uid 0: exited on signal 10 (core dumped)
panic: bad pte va 8002ef000 pte 0
cpuid = 1
time = 1615504090
KDB: enter: panic
db:0:kdb.enter.default>  bt
Tracing pid 64824 tid 100232 td 0xfffff8011ecca000
kdb_enter() at kdb_enter+0x37/frame 0xfffffe002eb033d0
vpanic() at vpanic+0x197/frame 0xfffffe002eb03420
panic() at panic+0x43/frame 0xfffffe002eb03480
pmap_remove_pages() at pmap_remove_pages+0xa1d/frame 0xfffffe002eb03580
exec_new_vmspace() at exec_new_vmspace+0x1ce/frame 0xfffffe002eb035f0
exec_elf64_imgact() at exec_elf64_imgact+0xa89/frame 0xfffffe002eb036e0
kern_execve() at kern_execve+0x728/frame 0xfffffe002eb03a40
sys_execve() at sys_execve+0x51/frame 0xfffffe002eb03ac0
amd64_syscall() at amd64_syscall+0x387/frame 0xfffffe002eb03bf0
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe002eb03bf0

Panic 2:

kernel trap 9 with interrupts disabled
panic: vm_fault: fault on nofault entry, addr: 0xfffffe002ea6d000
cpuid = 1
time = 1615578206
KDB: enter: panic
db:0:kdb.enter.default>  bt
Tracing pid 8195 tid 100201 td 0xfffff8008a96e000
kdb_enter() at kdb_enter+0x37/frame 0xfffffe002ea6d6a0
vpanic() at vpanic+0x197/frame 0xfffffe002ea6d6f0
panic() at panic+0x43/frame 0xfffffe002ea6d750
vm_fault() at vm_fault+0x24d2/frame 0xfffffe002ea6d8a0
vm_fault_trap() at vm_fault_trap+0x60/frame 0xfffffe002ea6d8e0
trap_pfault() at trap_pfault+0x19c/frame 0xfffffe002ea6d930
trap() at trap+0x286/frame 0xfffffe002ea6da40
calltrap() at calltrap+0x8/frame 0xfffffe002ea6da40

Panic 3:

<6>pid 53201 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)
<6>pid 44085 (unbound), jid 0, uid 59: exited on signal 11
<6>pid 3865 (php-cgi), jid 0, uid 0: exited on signal 11 (core dumped)

Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address    = 0xfffffe039d08264c
fault code        = supervisor read data, page not present
instruction pointer    = 0x20:0xffffffff8048f9d2
stack pointer            = 0x28:0xfffffe0000450920
frame pointer            = 0x28:0xfffffe0000450ae0
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        = 22 (rand_harvestq)
trap number        = 12
panic: page fault
cpuid = 1
time = 1615681839
KDB: enter: panic
db:0:kdb.enter.default>  bt
Tracing pid 22 tid 100087 td 0xfffff8002d3e2740
kdb_enter() at kdb_enter+0x37/frame 0xfffffe00004505e0
vpanic() at vpanic+0x197/frame 0xfffffe0000450630
panic() at panic+0x43/frame 0xfffffe0000450690
trap_fatal() at trap_fatal+0x391/frame 0xfffffe00004506f0
trap_pfault() at trap_pfault+0x4f
Actions

Also available in: Atom PDF