paulmorabi Posted June 9, 2021 Share Posted June 9, 2021 Hi, I recently moved across a Linux Debian VM to my Unraid that was previously running on Proxmox. Usually, after a few days (7+) of uptime, I begin to get errors on the terminal like this: Quote Message from syslogd@vm at Jun 9 10:24:23 ... kernel:[671107.221270] Uhhuh. NMI received for unknown reason 21 on CPU 3. Message from syslogd@vm at Jun 9 10:24:23 ... kernel:[671107.221271] Do you have a strange power saving mode enabled? Message from syslogd@vm at Jun 9 10:24:23 ... kernel:[671107.221271] Dazed and confused, but trying to continue These occur maybe 1-2 times per day until I shut down the VM, restart and then everything goes well for several days before beginning again. I don't notice anything else resulting from these errors. I've searched through the forums and have done the following to try and avoid these without success: CPU cores 0 and 1 are not assigned to any VM. Remaining cores are assigned to different VMs but no VM's are assigned the same core. Am not passing through any other hardware to the VM and system is stable and working otherwise. No issues with memtest. I'm running latest Unraid on a Ryzen 3600XT with 32GB Ram and a Gigabyte X570 Aorus Pro motherboard. Should I be worried about these and is there anything I can do further to avoid them? Quote Link to comment
daemonix Posted July 27, 2021 Share Posted July 27, 2021 Did you get anywhere with this? I just got something similar on an Epyc Milan unraid system.... kernel:[1220181.434892] Uhhuh. NMI received for unknown reason 31 on CPU 104. kernel:[1220181.434893] Do you have a strange power saving mode enabled? kernel:[1220181.434893] Dazed and confused, but trying to continue kernel:[1220250.396968] Uhhuh. NMI received for unknown reason 21 on CPU 12. kernel:[1220250.396969] Do you have a strange power saving mode enabled? kernel:[1220250.396970] Dazed and confused, but trying to continue Quote Link to comment
paulmorabi Posted October 1, 2021 Author Share Posted October 1, 2021 Sorry for the late reply, I didn’t get a notification. Sadly, I didn’t get anywhere with this. I tried pinning and assigning CPU cores to VM’s and that has possibly reduced the instances of this occurring but it still happens every 1-2 days. It seems to be harmless or have no long lasting effect but am also curious what is behind this and the cause of it. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.