Bug 1831899 - 'PME: Spurious native interrupt' when plugging USB 3 device into type C USB 3.1 Gen 2/Thunderbolt port
Summary: 'PME: Spurious native interrupt' when plugging USB 3 device into type C USB 3...
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 32
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-05-05 21:05 UTC by James
Modified: 2021-05-25 16:09 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed: 2021-05-25 16:09:22 UTC
Type: Bug

Attachments (Terms of Use)
dmesg from kernel-5.6.7-300.fc32.x86_64 with the messages. (100.68 KB, text/plain)
2020-05-05 21:05 UTC, James
no flags Details

Description James 2020-05-05 21:05:17 UTC
Created attachment 1685449 [details]
dmesg from kernel-5.6.7-300.fc32.x86_64 with the messages.

1. Please describe the problem:
There's a lot of:

pcieport 0000:00:1c.0: PME: Spurious native interrupt!

in dmesg when I attach a USB 3 device (e.g. a memory stick) to the type C combined USB 3.1 Gen 2/Thunderbolt port on my laptop.

2. What is the Version-Release number of the kernel:

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Unknown if this is a regression.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Attach USB 3 device to Thunderbolt port as described above.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

6. Are you running any modules that not shipped with directly Fedora's kernel?:

Comment 1 Fedora Program Management 2021-04-29 16:24:01 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-05-25 16:09:22 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.