¿Do you have a strange power saving mode enabled? PROXMOX MSG

V

VDNKH

Renowned Member
Aug 8, 2016
44
2
73
28
Hello very good afternoon community

A day ago my DELL T40 server with proxmox 7.3-3 started showing this message on screen and syslog:

Mar 12 03:58:59 MXBLCH kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0.
Mar 12 03:58:59 MXBLCH kernel: Do you have a strange power saving mode enabled?
Mar 12 03:58:59 MXBLCH kernel: Dazed and confused, but trying to continue
Mar 12 03:58:59 MXBLCH kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0.
Mar 12 03:58:59 MXBLCH kernel: Do you have a strange power saving mode enabled?
Mar 12 03:58:59 MXBLCH kernel: Dazed and confused, but trying to continue
Mar 12 03:58:59 MXBLCH kernel: Uhhuh. NMI received for unknown reason 2c on CPU 0.
Mar 12 03:58:59 MXBLCH kernel: Do you have a strange power saving mode enabled?
Mar 12 03:58:59 MXBLCH kernel: Dazed and confused, but trying to continue
Mar 12 03:58:59 MXBLCH kernel: Uhhuh. NMI received for unknown reason 3c on CPU 0.
Mar 12 03:58:59 MXBLCH kernel: Do you have a strange power saving mode enabled?
Mar 12 03:58:59 MXBLCH kernel: Dazed and confused, but trying to continue

It appears a lot, and after about 3 hours the server freezes, and the virtual machines are not accessible. The only way to get them back is to restart the server..

But the virtualizer does respond to PING, the virtual machines don't...

Do you know what could be happening? C-states are disabled in the BIOS
 
Now the server even rebooted by itself, could it be one of the Hardware components?
 
Greetings friends, no one responded, but here I leave what the problem was:

It was one of the RAM DIMMs. So what we did was physically replace it and that's it.
 
  • Like
Reactions: leesteken
VDNKH said:
Greetings friends, no one responded, but here I leave what the problem was:

It was one of the RAM DIMMs. So what we did was physically replace it and that's it.
Click to expand...
I have a the same issue but I've tried everything (replacing RAM sticks, reseating CPUs, replacing PSU, etc.) but nothing seems to solve the issue :-(
 
This can also occur within Virtual Machines during a long snapshot task or backup. While I was snapshotting my media server with local SSD's, I noticed the snapshot process took several minutes per SSD group (5TB and 4.5TB respectively) and the virtual machine's kernel was interrupting my SSH session with messages from the syslog:
kernel:[ 1836.283767] Uhhuh. NMI received for unknown reason 20 on CPU 2.
Message from syslogd@media at Feb 9 10:43:24 ...
kernel:[ 1836.283767] Do you have a strange power saving mode enabled?

Even though this was fast storage and XFS, these snapshots can take time and produce interesting results.
 
You must log in or register to reply here.
Top Bottom