From: Bjorn Helgaas <bjorn.helgaas@gmail.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: bugzilla.pci@gmail.com, linux-pci@vger.kernel.org
Subject: Re: [Bug 203303] New: PCIe Bus Error
Date: Sun, 14 Apr 2019 17:24:08 -0500 [thread overview]
Message-ID: <CABhMZUWEvx62b-w5Wxf3xbjn9rFpZRMMWNvF3iBStgVnemJ5Aw@mail.gmail.com> (raw)
In-Reply-To: <bug-203303-193951@https.bugzilla.kernel.org/>
> pcieport 0000:00:01.7: AER: Corrected error received: 0000:00:01.0
> pcieport 0000:00:01.7: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
> pcieport 0000:00:01.7: device [1022:15d3] error status/mask=00000040/00006000
> pcieport 0000:00:01.7: [ 6] BadTLP
Can you please attach a complete dmesg log and complete "sudo lspci
-vv" output for the whole system? Is this reproducible? Is it a
regression?
Hardware should recover from PCIe correctable errors without software
intervention. They are reported only for logging purposes. Does your
system work correctly in spite of logging this error? Is it possible
the ath10k card is not seated correctly, has dirty contacts, etc?
parent reply other threads:[~2019-04-14 22:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-203303-193951@https.bugzilla.kernel.org/>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABhMZUWEvx62b-w5Wxf3xbjn9rFpZRMMWNvF3iBStgVnemJ5Aw@mail.gmail.com \
--to=bjorn.helgaas@gmail.com \
--cc=bjorn@helgaas.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=bugzilla.pci@gmail.com \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.