"PME: Spurious native interrupt!" Kernel Meldungen

smasty

New Member
Mar 21, 2019
3
3
3
Hallo zusammen,

nachdem ich nun den ersten PVE-Knoten von 6.0.9 auf 6.1.5 (und damit Kernel 5.3.13) angehoben habe, wird mein Syslog mit folgenden Meldungen kontinuierlich befüllt:

[...]
Jan 6 10:00:01 kernel: [ 8076.840412] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:04 kernel: [ 8078.958690] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:06 kernel: [ 8080.971962] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:06 kernel: [ 8080.988809] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:09 kernel: [ 8084.103786] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:09 kernel: [ 8084.103963] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:11 kernel: [ 8086.457771] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:16 kernel: [ 8091.345566] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:16 kernel: [ 8091.353984] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:26 kernel: [ 8101.770559] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:27 kernel: [ 8102.724566] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:27 kernel: [ 8102.869279] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:28 kernel: [ 8103.431608] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:31 kernel: [ 8106.841754] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:31 kernel: [ 8106.856727] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:33 kernel: [ 8108.399521] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:38 kernel: [ 8113.399608] pcieport 0000:00:03.0: PME: Spurious native interrupt!
Jan 6 10:00:39 kernel: [ 8114.350334] pcieport 0000:00:03.0: PME: Spurious native interrupt!
[...]
Wie man an den zeitlichen Abständen sieht, kommen da schon viele Log Messages zusammen...

Es geht dabei wohl um folgendes PCI-Device:

# lspci -vv -t|grep 03.0
| +-03.0-[83]--
+-03.0-[04-05]--+-00.0 Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection
Die Meldungen erscheinen allerdings erst im Log, nachdem ich wieder eine VM zurückmigriert habe bzw. dort eine VM läuft.

Ich vermute, dass sich das mit dem/den nächsten Kernel Updates erledigen wird, hat hier jemand ähnliches im Log?
 

rdfeij

New Member
Jan 8, 2020
3
0
1
40
Same problem here. Since update yesterday from version 5.4.x to 6.1-5
We have the same Intel 10Gbit interfaces.
We had over 64GB of logging in kern.log filling up OS disk
 

rdfeij

New Member
Jan 8, 2020
3
0
1
40
Same problem here. Since update yesterday from version 5.4.x to 6.1-5
We have the same Intel 10Gbit interfaces.
We had over 64GB of logging in kern.log filling up OS disk
This morning our 3th node crashed again (out of diskspace)
After deleting:
/var/log/syslog
/var/log/messages
/var/log/kern.log
and a reboot it is working again.

The spurious interrupt records are filling up logging very fast.
For now solved by creating a cronjob emptying these files every hour.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!