Sometimes the "pcie_aspm=off" kernel parameter hides this problem. I
would really like to fix the underlying problem so the parameter isn't
needed.
If anybody sees this problem and is willing to help fix it, please open
a bug report at https://bugzilla.kernel.org/, product Drivers/PCI,
mention the
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888523
T
I don't know how to edit posts but I wanted to add:
I plugged a different m.2 NVMe from a different manufacturer into the
"M2A_32G" port to see if the port is the problem. There are no errors. I
can only replicate the problem with the XPG NVMe in port "M2A_32G".
** Attachment added: "Z370 AORUS G
5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020
I pulled all the hardware from my PC and went through each part one by
one. The device that makes these errors appear is the XPG GAMMIX S5 m.2
when plugged into port "M2A_32G". I moved the m.2 device to port
"M2P_32G" and the errors disa
Indeed; I was hoping to check what's under the root port just in case,
but acknowledge that might not be helpful / have too much stuff under,
being a desktop system. Let's see. :)
Per the repeated messages I'd imagine this is a device-related error,
but wanted to check the kernel version log in ca
The errors comes from physical layer so they likely comes from the root
port (00:1d.0) or the device attaches to it. Also, PCIe correctable
errors are handled by hardware, so one can turn off some hardware-
related features, such as apsm (pcie_aspm=off) or msi (pci=nomsi), to
verify whether there a
Hi Pedro,
It's curious that the message is repeatedly showing up at the rate of a few
seconds.
It would initially suggest something might be wrong with the PCI device.
(As Alex mentioned the errors are correctable, so not a serious issue,
but the fact they're being repeatedly logged doesn't soun
When a PCIe AER error is captured, an error message will be output to
console. If it's a correctable error, it is output as a warning.
Otherwise, it is printed as an error. So users could choose different
log level to filter out correctable error messages.
==
PCI(e) is capable of correcting errors whenever possible. From your logs
all of the errors are corrected and therefore nothing to worry about.
If you see incorrectable errors you may observed device failures, or
system failures in some cases.
--
You received this bug notification because you are
Unfortunately I can't share the apport-collect log because I am
uncomfortable with the amount of data it collects about my system. My
threat model doesn't allow for such disclosure of data. I could share
relevant parts of the log if I review it first.
--
You received this bug notification because
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888523
Title:
PCIe Bus Error device 8086:a298 spam
To manage notifications about this bug go to:
https://
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
12 matches
Mail list logo
