with what drives installed?
I have tried with 2x samsung nvme drives and one regular ssd. Same drives worked great on 2 other proxmox installations on i5 and i3 with ~0.05% io delay when idle.
with what drives installed?
the 23 microcode will most likely not solve your issues permanently.Hi, just wanted to add my experience.
N5105 based system, OVMS/Home Assistant install crashing every 6-8 hours. SeaBIOS/Pfsense install not crashing.
Update to the 6.2 Kernel and Microcode 0x24000023 has me at 3 days so far. No other changes.
what are you referring to with your question?@beisser also with powersave cpu governor? Really don't want to upgrade as mine is stable
ahh, now i understand.Does version 23 of the microcode run stable with CPU governor powersave?
im on powersave with 24Ah sorry, mean 24. Which are you using now (with 24)?
update of the kernel depends on hwre you want to go.It is great to see that "my" thread seemed to have helped some people.
I had 70 days of uptime before a power outage and now I am back to 3-15 days before a reboot of pfSense.
I am currently on
- Proxmox 7.3-6
- Kernel: Linux pve 5.15.85-1-pve #1 SMP PVE 5.15.85-1 (2023-02-01T00:00Z) x86_64 GNU/Linux
- no idea on the microcode
How do I check/update the microcode and update the kernel?
apt install pve-kernel-6.1
apt install pve-kernel-6.2
dmesg | grep "microcode updated early to"
apt install intel-microcode
update of the kernel depends on hwre you want to go.
the 5.15 kernel is automatically updated as far as i know.
if you want to use 6.1 or 6.2 kernels you will need toorCode:apt install pve-kernel-6.1
Code:apt install pve-kernel-6.2
as for checking which microcode you have you can useif it returns something its the version of the installed microcode.Code:dmesg | grep "microcode updated early to"
if it doesnt return anything its most likely that you havent installed the microcode.
in that case you can, which will get you to the version 23 microcode (you may need to enable non-free repositories for that).Code:apt install intel-microcode
after that you will need to follow the instructions earlier in this thread on how to overwrite the 23 microcode with the 24 microcode.
is used the instructions in this post: https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/post-536880
root@pve:~# cat /proc/cpuinfo|grep 'microcode\|model name'
model name : Intel(R) Celeron(R) N5105 @ 2.00GHz
microcode : 0x1d
model name : Intel(R) Celeron(R) N5105 @ 2.00GHz
microcode : 0x1d
model name : Intel(R) Celeron(R) N5105 @ 2.00GHz
microcode : 0x1d
model name : Intel(R) Celeron(R) N5105 @ 2.00GHz
microcode : 0x1d
i can only speak from my point of view.Is there any disadvantage of going to 6.2 kernel vs 6.1?
As for microcode, the command did not return anything:
Code:root@pve:~# cat /proc/cpuinfo|grep 'microcode\|model name' model name : Intel(R) Celeron(R) N5105 @ 2.00GHz microcode : 0x1d model name : Intel(R) Celeron(R) N5105 @ 2.00GHz microcode : 0x1d model name : Intel(R) Celeron(R) N5105 @ 2.00GHz microcode : 0x1d model name : Intel(R) Celeron(R) N5105 @ 2.00GHz microcode : 0x1d
Sounds good,i can only speak from my point of view.
i was running 6.1.2 on my n5105 box since it came out and then immediately switched to 6.2.2 (havent rebooted since for even newer kernel) and havent noticed any negative effects, but i am not using features such as gpu passthrough or anything, so others may think differently.
yesSounds good,
I assume I will need a reboot for the new microcode?
4 x Intel(R) Celeron(R) N5105 @ 2.00GHz (1 Socket)
Linux 6.2.6-1-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.6-1 (2023-03-14T17:08Z)
GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on pcie_aspm.policy=performance split_lock_detect=off"
32GB RAM
NVMe system disk + 2 SATA SSD Crucial M500
model name : Intel(R) Celeron(R) N5105 @ 2.00GHz
stepping : 0
microcode : 0x24000024
root@pve1:~# cpupower idle-info
CPUidle driver: intel_idle
CPUidle governor: menu
analyzing CPU 0:
Number of idle states: 4
Available idle states: POLL C1_ACPI C2_ACPI C3_ACPI
POLL:
Flags/Description: CPUIDLE CORE POLL IDLE
Latency: 0
Usage: 1798437
Duration: 183454194
C1_ACPI:
Flags/Description: ACPI FFH MWAIT 0x0
Latency: 1
Usage: 254458076
Duration: 70202037938
C2_ACPI:
Flags/Description: ACPI FFH MWAIT 0x31
Latency: 253
Usage: 94577494
Duration: 115673679409
C3_ACPI:
Flags/Description: ACPI FFH MWAIT 0x60
Latency: 1048
Usage: 21449179
Duration: 51663352077
root@pve2:~# cpupower idle-info
CPUidle driver: intel_idle
CPUidle governor: menu
analyzing CPU 0:
Number of idle states: 8
Available idle states: POLL C1 C1E C6 C7s C8 C9 C10
POLL:
Flags/Description: CPUIDLE CORE POLL IDLE
Latency: 0
Usage: 3127267
Duration: 60532016
C1:
Flags/Description: MWAIT 0x00
Latency: 2
Usage: 71236569
Duration: 3713080218
C1E:
Flags/Description: MWAIT 0x01
Latency: 10
Usage: 95569525
Duration: 19317061195
C6:
Flags/Description: MWAIT 0x20
Latency: 150
Usage: 0
Duration: 0
C7s:
Flags/Description: MWAIT 0x31
Latency: 150
Usage: 342048643
Duration: 333922774597
C8:
Flags/Description: MWAIT 0x40
Latency: 5963
Usage: 2425164
Duration: 7676647957
C9:
Flags/Description: MWAIT 0x50
Latency: 5963
Usage: 3335931
Duration: 13552333719
C10:
Flags/Description: MWAIT 0x60
Latency: 6291
Usage: 16030930
Duration: 68046199898
cpupower idle-set -D 11
i turned everything back on after the 24 microcode. seems to work just fine with all c-states enabled.How did y'all handle BIOS settings after updating the kernel and the microcode. Some settings were recommended earlier in the thread, but not sure they did the trick. I e.g. disabled the power saving modes (C-State?). Would you do a BIOS settings reset?
Hello,How did y'all handle BIOS settings after updating the kernel and the microcode. Some settings were recommended earlier in the thread, but not sure they did the trick. I e.g. disabled the power saving modes (C-State?). Would you do a BIOS settings reset?