I will look into this when I get a chance to bring the home network down so that I can enter the BIOS and look for power-saving features.

In this AMD forum the author states I disable c-states in BIOS and error is gone. One seems to claim it is related to some power-saving feature called C-states: There are a couple of posts that reference this. Reading that makes it seem like there's some missing or misbehaving driver? Unfortunately I haven't found much info on the web, other than that this message means that a 'non maskable interrupt' was signalled from some hardware, and Linux had no handler installed to deal with it, therefore ignored it. Clearly it's not causing any issues for me but I'm just a tinkerer and want to know why. NMI received for unknown reason 2d on CPU 17 occurences in the past 10 months. NMI received for unknown reason 2d on CPU 3. NMI received for unknown reason 3d on CPU 0. NMI received for unknown reason 3d on CPU 1. NMI received for unknown reason 2d on CPU 1. NMI received for unknown reason 2d on CPU 1.Īpr 27 16:45:38 lab kernel: Uhhuh. NMI received for unknown reason 3d on CPU 3.Īpr 18 02:18:55 lab kernel: Uhhuh.

NMI received for unknown reason 3d on CPU 2.Īpr 05 18:11:52 lab kernel: Uhhuh.

NMI received for unknown reason 3d on CPU 5. NMI received for unknown reason 2d on CPU 5.įeb 09 12:56:50 lab kernel: Uhhuh. NMI received for unknown reason 3d on CPU 3. I've never seen this before (nor have I ever head issues) but I checked and it seems to be happening a long time now (though very rarely, this thing runs 24/7 as it has among other things my pfSense gateway to the world): journalctl | grep 'NMI received for unknown'ĭec 20 19:42:49 lab kernel: Uhhuh. Kernel: Dazed and confused, but trying to continue Kernel: Do you have a strange power saving mode enabled? NMI received for unknown reason 2d on CPU 5. Today I left a tmux session running on the host and noticed this message: Message from at Sep 19 17:56:09. I run Proxmox at home on an ASRock 4x4 Box V1000M which has a 4c/8t V1605B Ryzen model in it.

Interrupt storm detected proxmox