mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kuppuswamy, Sathyanarayanan"  <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
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: Re: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Date: Mon, 7 Dec 2020 09:44:20 -0800	[thread overview]
Message-ID: <672a0bc2-717a-2545-6a19-8ca7e209c523@linux.intel.com> (raw)
In-Reply-To: <084ea8e2-baae-0e2d-c60d-73fb055bdc1d@molgen.mpg.de>

Hi,

On 12/7/20 5:08 AM, Paul Menzel wrote:
> [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;
As per PCIe spec r5.0, sec 7.9.15.2, valid RP log size is 4 or greater. Please see
the text copied from spec

- - - -
RP PIO Log Size - This field indicates how many DWORDs are allocated for the RP
PIO log registers, comprised by the RP PIO Header Log, the RP PIO ImpSpec Log,
and RP PIO TLP Prefix Log. If the Root Port supports RP Extensions for DPC, the
value of this field must be 4 or greater; otherwise, the value of
this field must be 0. See Section 7.9.15.11 , Section 7.9.15.12 , and Section 7.9.15.13 .
- - - -

In this case, since "(!(cap & PCI_EXP_DPC_CAP_RP_EXT))" condition is false, RP
EXT is supported. If RP EXT is supported, valid log size should be at-least 4.


>      }
> 
> (I guess `cap & PCI_EXP_DPC_RP_PIO_LOG_SIZE` is zero too?)
> 
> Is it a firmware issue or a hardware issue?
I think this could be 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 
> 

-- 
Sathyanarayanan Kuppuswamy
Linux Kernel Developer

  reply	other threads:[~2020-12-07 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 13:08 Paul Menzel
2020-12-07 17:44 ` Kuppuswamy, Sathyanarayanan [this message]
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=672a0bc2-717a-2545-6a19-8ca7e209c523@linux.intel.com \
    --to=sathyanarayanan.kuppuswamy@linux.intel.com \
    --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=pmenzel@molgen.mpg.de \
    /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®