I spoke too soon, I'm now seeing multiple reboots per day on the pfsense VM with Unraid.
The error seems to be more consistent now;
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x30
fault code = supervisor write data, page not present
instruction pointer = 0x20:0xffffffff80da98bd
stack pointer = 0x28:0xfffffe0025972b00
frame pointer = 0x28:0xfffffe0025972b60
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = resume, IOPL = 0
current process = 11 (idle: cpu0)
trap number = 12
timeout stopping cpus
panic: page fault
cpuid = 0
time = 1659451328
KDB: enter: panic
Any chance you could go into more detail about everything you did?
- How/which C-states you disabled and any other bios changes? (What did that do to your power usage/heat?)
- How to disable powerd in pfsense? Any other pfsense mods?
- What version of QEMU, Linux kernel etc, you are running (I'm on Unraid not Proxmox).
Thanks,
C-states defaulted to "Disabled" on both the CW-N6000 and CW-N11 devices. I originally enabled them to get the lowest power usage possible but that may have been responsible for the aforementioned issues. Since I need reliability more than I need to save 4-5W, I reverted to the original setting of "Disabled".
To disable C-states, go into BIOS:
Advanced > Power & Performance > CPU - Power Management Control > C States [Disabled]
Save and reset.
That results in about a 4-5W penalty on idle power usage. I think I went from 8.9W to 13.4 during idle when I was playing around with the kill-a-watt. I can plug in the power meter later if you want exact numbers which will vary depending how many NICs you have connected, how much memory is installed, what storage devices(s), etc.
The only other change I made was to Disable Intel ME (also done in BIOS).
To disable PowerD in pfsense:
System > Advanced > Miscellaneous
In the "Power Savings" section, make sure the PowerD Enabled box is unchecked (you don't need powerd trying to manage CPU states if you're running it as a guest and have C-states disabled).
I'm running pfsense on Proxmox. Here are the relevant Proxmox package versions:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-4
pve-kernel-helper: 7.2-4
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-qemu-kvm: 6.2.0-11
qemu-server: 7.2-3