I went with the Intel NUC 12 Pro Kit - NUC12WSHi5. And yes, no issues so far - Proxmox is running smoothly with this machine. Same memory sticks and SSD drives which I used in the PN51-E1..
Last edited:
Random system freeze on PN51-E1
- Thread starter cpc0307
- Start date
Thank you for your reply, I think I will go with that NUC as well then. I like the "running smoothly" part!
Hey guys, I have the same issue with my asus PN51-E1. I do own a PN50 and it works flawlessly. I don't believe it's a software issue as I have tried different OS mainly linux based on both my PN50 and PN51-E1. But no luck with my PN51-E1 it run will for some times and then crashes. Has anybody tried to reach out to Asus support? I'm seeing similar issues in other forums as well.
I tried that, didn't work.
Sent my unit back to the ASUS repair center, and tell them the device suffres from unexpected freezes when running Linux.
After a month of waiting, the result is inconclusive.
ASUS said that they can't replica the issue, and it passes all the tests under Windows environment.
WIth my system i have also freeze problems.
I mitigated them by using the watchdog. Since my system is a headless server, with the watchdog it does reboot automatically.
On the Asus website I found a new BIOS version. Just installed it. Hopefully it helps.
After the update the cpuidle driver was shown. Before it was saying there is none available.
My best uptime with this issue is 11days and 10h.
So far the system is running for 26 days, 18:54:52 after the bios update. Hopefully this will solve the freezes.
getting close to the top. Some of the higher uptimes where reached before with load on the system like video encoding. For the actual run there was no heavy load on the system. I'm getting hope that this issue is really fixed.
update: I considered this bug fixed. my server is running and running. There are no special cmd line params for the kernel in place.
I mitigated them by using the watchdog. Since my system is a headless server, with the watchdog it does reboot automatically.
On the Asus website I found a new BIOS version. Just installed it. Hopefully it helps.
After the update the cpuidle driver was shown. Before it was saying there is none available.
Bash:
sudo cpupower -c all idle-info
CPUidle-Treiber: acpi_idle
CPUidle-Regler: menu
CPU 0 wird analysiert:
Anzahl der Ruhezustände: 4
Verfügbare Ruhezustände: POLL C1 C2 C3
POLL:
Merker/Beschreibung: CPUIDLE CORE POLL IDLE
Latenz: 0
Aufruf: 854
Dauer: 27846
C1:
Merker/Beschreibung: ACPI FFH MWAIT 0x0
Latenz: 1
Aufruf: 8509
Dauer: 606498
C2:
Merker/Beschreibung: ACPI IOPORT 0x414
Latenz: 18
Aufruf: 5723
Dauer: 2252344
C3:
Merker/Beschreibung: ACPI IOPORT 0x415
Latenz: 350
Aufruf: 8769
Dauer: 115199355My best uptime with this issue is 11days and 10h.
So far the system is running for 26 days, 18:54:52 after the bios update. Hopefully this will solve the freezes.
getting close to the top. Some of the higher uptimes where reached before with load on the system like video encoding. For the actual run there was no heavy load on the system. I'm getting hope that this issue is really fixed.
Bash:
uprecords
# Uptime | System Boot up
----------------------------+---------------------------------------------------
-> 1 26 days, 18:54:52 | Linux 6.1.0-17-amd64 Sun Jan 14 22:36:35 2024
2 11 days, 10:22:37 | Linux 6.1.0-11-amd64 Fri Sep 1 08:15:35 2023
3 8 days, 09:26:35 | Linux 6.1.0-9-amd64 Tue Jul 4 05:03:58 2023
4 8 days, 00:01:40 | Linux 6.1.0-15-amd64 Tue Dec 12 21:05:17 2023
5 7 days, 12:01:14 | Linux 6.1.0-0.deb11.7-am Wed May 24 16:48:46 2023
6 6 days, 11:44:54 | Linux 6.1.0-11-amd64 Mon Aug 21 19:39:15 2023
7 5 days, 23:01:41 | Linux 6.1.0-13-amd64 Thu Nov 2 07:55:32 2023
8 5 days, 20:08:50 | Linux 6.1.0-10-amd64 Wed Jul 12 15:25:14 2023
9 5 days, 00:01:40 | Linux 6.1.0-12-amd64 Wed Sep 27 08:03:26 2023
10 4 days, 16:01:40 | Linux 6.1.0-10-amd64 Thu Aug 10 15:30:08 2023
----------------------------+---------------------------------------------------
NewRec 15 days, 08:32:14 | since Fri Jan 26 08:59:13 2024
up 266 days, 12:40:20 | since Sat May 13 06:53:21 2023
down 6 days, 22:57:46 | since Sat May 13 06:53:21 2023
%up 97.456 | since Sat May 13 06:53:21 2023update: I considered this bug fixed. my server is running and running. There are no special cmd line params for the kernel in place.
Last edited:
Wow, this looks promising
Will try switching back to proxmox this weekend.
--- Update 02/19/2024 ---
Also managed to get an 11-day uptime without encountering any random system freeze.
Looks like the BIOS update really did something to improve the situation.
Last edited:
@cpc0307 Is it still running?
Did just remembered this thread the other day, and figured I will test the same, after a year or something with the PN51-E1 on the shelf collecting dust. Did a new install (and updated to the newest bios) and it have been running for the last 24h, and no freeze yet :-D
Did just remembered this thread the other day, and figured I will test the same, after a year or something with the PN51-E1 on the shelf collecting dust. Did a new install (and updated to the newest bios) and it have been running for the last 24h, and no freeze yet :-D
Yes, I got it running after the BIOS update in January, and it has been running without any freezes.
That was until I decided to swap it for an Minisforum MS-01 in mid-July.
Hi there,
We also have a PN51-E1 and had similar problems last year until it stopped around July / August in a version version.
But unfortunately I do not remember which versions and timeframes. Must dig a little bit around.
Now since around End of August it started again.. first crash some time after upgrading to 9.x then 2 weeks working without issues.
Currently we do have daily freezes in the morning (backups are running at 21:00 - which should be the biggest load).
Currently using: Linux 6.14.11-3-pve
PVE-Manager: 9.0.10
Just updated BIOS to 0510 but don't think this is a solution.
We also have a PN51-E1 and had similar problems last year until it stopped around July / August in a version version.
But unfortunately I do not remember which versions and timeframes. Must dig a little bit around.
Now since around End of August it started again.. first crash some time after upgrading to 9.x then 2 weeks working without issues.
Currently we do have daily freezes in the morning (backups are running at 21:00 - which should be the biggest load).
Currently using: Linux 6.14.11-3-pve
PVE-Manager: 9.0.10
Just updated BIOS to 0510 but don't think this is a solution.
More details:
PN51-E1 with a 5700U
Ethernet RTL8125
BTW at the update I had the warning about the "Package amd64-microcode is not available"
Why I added non-free-firmware to the sources and installed the update/package now
changed to:
update log:
PN51-E1 with a 5700U
Ethernet RTL8125
BTW at the update I had the warning about the "Package amd64-microcode is not available"
Why I added non-free-firmware to the sources and installed the update/package now
Code:
# grep microcode /proc/cpuinfo | uniq
microcode : 0x8608103
# dmesg | grep microcode
[ 0.301490] Zenbleed: please update your microcode for the most optimal fix
[ 1.056040] microcode: Current revision: 0x08608103
Code:
apt install amd64-microcode
The following packages were automatically installed and are no longer required:
libpython3.11 proxmox-kernel-6.8.12-6-pve-signed python3-jaraco.classes python3-pastedeploy-tpl python3-soupsieve python3-waitress
proxmox-kernel-6.14.8-2-pve-signed proxmox-kernel-6.8.12-9-pve-signed python3-paste python3-pytz python3-tempita python3-webtest
proxmox-kernel-6.8.12-11-pve-signed python3-bs4 python3-pastedeploy python3-singledispatch python3-tz
Use 'apt autoremove' to remove them.
Installing:
amd64-microcode
Summary:
Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0
Download size: 278 kB
Space needed: 715 kB / 249 GB available
Get:1 http://ftp.ch.debian.org/debian trixie/non-free-firmware amd64 amd64-microcode amd64 3.20250311.1 [278 kB]
Fetched 278 kB in 0s (8,492 kB/s)
Selecting previously unselected package amd64-microcode.
(Reading database ... 116782 files and directories currently installed.)
Preparing to unpack .../amd64-microcode_3.20250311.1_amd64.deb ...
Unpacking amd64-microcode (3.20250311.1) ...
Setting up amd64-microcode (3.20250311.1) ...
amd64-microcode: microcode will be updated at next boot
Processing triggers for initramfs-tools (0.148.3) ...
update-initramfs: Generating /boot/initrd.img-6.14.11-4-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B1CD-EA4B
Copying kernel and creating boot-entry for 6.14.11-3-pve
Copying kernel and creating boot-entry for 6.14.11-4-pve
Copying kernel and creating boot-entry for 6.8.12-14-pvechanged to:
Code:
#grep microcode /proc/cpuinfo | uniq
microcode : 0x8608108
# dmesg | grep microcode
[ 1.046730] microcode: Current revision: 0x08608108
[ 1.046745] microcode: Updated early from: 0x08608103update log:
Code:
2025-10-15 proxmox-kernel-6.14.11-4-pve-signed:amd64, pve-manager:amd64 (9.0.10, 9.0.11)
2025-10-06 proxmox-kernel-6.14.11-3-pve-signed:amd64, proxmox-kernel-6.14:amd64 (6.14.8-2, 6.14.11-3), pve-manager:amd64 (9.0.6, 9.0.10)
2025-08-28 proxmox-kernel-6.14.8-2-pve-signed:amd64, proxmox-ve:amd64 (8.4.0, 9.0.0), proxmox-kernel-helper:amd64 (8.1.4, 9.0.4)
2025-08-27 proxmox-kernel-6.8.12-14-pve-signed:amd64, pve-manager:amd64 (8.4.1, 8.4.12)
2025-07-07 proxmox-kernel-6.8.12-11-pve-signed:amd64