PME: Spurious native interrupt!

jmacko

New Member
Feb 20, 2024
1
0
1
Over and over in my logs I'm seeing the following:
Logs
Apr 15 08:05:34 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:05:35 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:05:37 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:05:41 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:05:41 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:05:41 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:05:52 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:05:52 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Apr 15 08:06:11 prox2 kernel: pcieport 0000:00:02.2: PME: Spurious native interrupt!
Device 02.2
00:02.2 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 2 (rev 01)

I've updated the log to stop the message from being logged and filling up syslog.

Updated /etc/kernel/cmdline and added pcie_aspm=off to disable active state power management. No change.

The servers are HP DL360 Gen9, and the logs are the same on both hosts, so I don't think this is a failed hardware issue.

What's the side effect of this type of bug? Can it be safely ignored?

Thanks!
 
+1
Dec 07 11:30:49 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:51 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:51 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:51 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:52 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:52 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:53 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:53 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:53 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:53 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:53 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:54 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:54 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:54 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:30:55 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:31:04 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:31:04 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:31:18 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
Dec 07 11:31:25 node1 kernel: pcieport 0000:00:01.0: PME: Spurious native interrupt!
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07)
root@node1:~# lspci -vv -t | grep 01.0
+-01.0-[01]----00.0 Intel Corporation 82599 10 Gigabit Network Connection
Anybody know how to fix/hide?

EDIT:
Because I can't see any issue, I hide all messages on the terminal (Monitor connected on the node)

dmesg -n 1
this is not reboot stable, so I put in the command in crontab.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!