Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2377234pxu; Mon, 7 Dec 2020 05:11:31 -0800 (PST) X-Google-Smtp-Source: ABdhPJxdCUB+1Cvqf5TaF08NP/uWlaCgF6xy/scyBscca9Dasn0c7trzUrRzb2sm0g3Gtkb6rs1x X-Received: by 2002:a17:906:7784:: with SMTP id s4mr1178852ejm.93.1607346691370; Mon, 07 Dec 2020 05:11:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607346691; cv=none; d=google.com; s=arc-20160816; b=NMDYvwn7ePD0SintStVkEeUZzif0swysRDtRsUfEVOhqCbRNCd2IinfW04Rydjlyag gwhsv4YX4+Prtqgddllq6PODGPGnm0iYMqTEorzInzk5BFxp6JRjV+lLK8dZdkAPDmuW 9+gJr2dqPRIutBpUdyAs+KWQXHuLLrBQIQuCGdzAg+5ZaIgnS7JJMaxMzyhRcUoK2jj6 1rPdGWBp54Uhobth8aj5VEeJsmC/ICDe0pUnBGcw7g8StZmEK6wMyvVKnGaWt6VQFnsB 3kdl6Y7ks2lk7IPfcqH2tsV0ZqN8ko6oiRanYQWs8D6Fyj4ANaZqRY9k+P5ooZoozSq7 q1eg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :mime-version:user-agent:date:message-id:subject:from:cc:to; bh=fl25vS407hcu2AGptacz0chUhtocXnL26ObNBxhM9d0=; b=EE5Jj0TRcviqthxRH0824SIRkNIdw1MLFEIJMB+cbbPLep9DBO3KlH3t/A225KI49P 1Nrr9OlPnSbnvCPbTP5LiBDKribjOPwk8SqRy5y8s0ic7s/nvsX1Vw3zO6qxEziJfnrq zLzPZT1pAnNrDtInqLn3NeMGdZU+Ze1sS6q6149M9rWFWENsehbVm/36BkNYfwBSESUe X/goiV+ZcYMVTpKzo+R5OQDZAZWdSdT1CiQl/S+MstfHhh7HdLo/KV9TOcOuNOcOcrex CdoFqTEM0Ik6EoZ0MJKfOS/N7YeG/+u5w1HjeGd5lYAtJo30zhUhe0M6YaD7r+LrOxAE KlOg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lw15si6181765ejb.535.2020.12.07.05.11.06; Mon, 07 Dec 2020 05:11:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726339AbgLGNIo (ORCPT + 99 others); Mon, 7 Dec 2020 08:08:44 -0500 Received: from mx3.molgen.mpg.de ([141.14.17.11]:46351 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725772AbgLGNIo (ORCPT ); Mon, 7 Dec 2020 08:08:44 -0500 Received: from [192.168.0.3] (ip5f5af45d.dynamic.kabel-deutschland.de [95.90.244.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id 5328D20647B5E; Mon, 7 Dec 2020 14:08:01 +0100 (CET) To: Kuppuswamy Sathyanarayanan Cc: Bjorn Helgaas , linux-pci@vger.kernel.org, LKML , Mario Limonciello , Mika Westerberg From: Paul Menzel Subject: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid Message-ID: <084ea8e2-baae-0e2d-c60d-73fb055bdc1d@molgen.mpg.de> Date: Mon, 7 Dec 2020 14:08:00 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [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