From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mario Limonciello <mario.limonciello@dell.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Date: Mon, 7 Dec 2020 14:08:00 +0100 [thread overview]
Message-ID: <084ea8e2-baae-0e2d-c60d-73fb055bdc1d@molgen.mpg.de> (raw)
[Bringing the issue up on the list in case the Linux Bugzilla is not
monitored/used.]
Dear Linux folks,
On Intel Tiger Lake Dell laptop, Linux logs the error below [1].
[ 0.507307] pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
[ 0.508835] pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
$ lspci -nn -s 00:07
00:07.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP
Thunderbolt PCI Express Root Port #0 [8086:9a23] (rev 01)
00:07.2 PCI bridge [0604]: Intel Corporation Tiger Lake-LP
Thunderbolt PCI Express Root Port #2 [8086:9a27] (rev 01)
Commit 2700561817 (PCI/DPC: Cache DPC capabilities in
pci_init_capabilities()) [1] probably introduced it in Linux 5.7.
What does this error actually mean?
pdev->dpc_rp_log_size = (cap & PCI_EXP_DPC_RP_PIO_LOG_SIZE) >> 8;
if (pdev->dpc_rp_log_size < 4 || pdev->dpc_rp_log_size > 9) {
pci_err(pdev, "RP PIO log size %u is invalid\n",
pdev->dpc_rp_log_size);
pdev->dpc_rp_log_size = 0;
}
(I guess `cap & PCI_EXP_DPC_RP_PIO_LOG_SIZE` is zero too?)
Is it a firmware issue or a hardware issue?
Kind regards,
Paul
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=209943
"pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid"
[2]:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=27005618178ef9e9bf9c42fd91101771c92e9308
next reply other threads:[~2020-12-07 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 13:08 Paul Menzel [this message]
2020-12-07 17:44 ` Kuppuswamy, Sathyanarayanan
2020-12-07 23:13 ` Bjorn Helgaas
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=084ea8e2-baae-0e2d-c60d-73fb055bdc1d@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=mika.westerberg@linux.intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®