[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

bug report question



Hello,

I'd like to submit a bug, but I'm not quite sure which package it should be. I could not find anything similar in the bugtracker.

The problem occurs every 10-20 times. After the system has been suspended and then resumed, the following message is written to kern.log and syslog:

2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040221] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264297+02:00 host kernel: [527584.040225] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264298+02:00 host kernel: [527584.040229] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264298+02:00 host kernel: [527584.040233] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264299+02:00 host kernel: [527584.040237] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264299+02:00 host kernel: [527584.040241] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264300+02:00 host kernel: [527584.040244] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264301+02:00 host kernel: [527584.040248] pcieport 0000:00:01.3: PME: Spurious native interrupt! 2023-09-07T09:43:21.264301+02:00 host kernel: [527584.040252] pcieport 0000:00:01.3: PME: Spurious native interrupt!

There are so many of them that within 10 minutes the log files are several GiB in size, filling the root filesystem and rendering the OS unusable.

I accept that the message may indicate a valid problem, but having so many log messages is not OK either. Currently, when this happens, I am forced to manually delete the log file and reboot.

Best regards,
Peter


Reply to: