From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9FCD3C433FE for ; Mon, 13 Sep 2021 23:41:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7D95560FC0 for ; Mon, 13 Sep 2021 23:41:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244164AbhIMXnO (ORCPT ); Mon, 13 Sep 2021 19:43:14 -0400 Received: from mail.i8u.org ([75.148.87.25]:49875 "EHLO chris.i8u.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236079AbhIMXnM (ORCPT ); Mon, 13 Sep 2021 19:43:12 -0400 X-Greylist: delayed 545 seconds by postgrey-1.27 at vger.kernel.org; Mon, 13 Sep 2021 19:43:12 EDT Received: by chris.i8u.org (Postfix, from userid 1000) id DDF6916C958B; Mon, 13 Sep 2021 16:32:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by chris.i8u.org (Postfix) with ESMTP id DD63E16C92D2; Mon, 13 Sep 2021 16:32:39 -0700 (PDT) Date: Mon, 13 Sep 2021 16:32:39 -0700 (PDT) From: Hisashi T Fujinaka To: Heiner Kallweit cc: Jesse Brandeburg , Tony Nguyen , Dave Jones , "linux-pci@vger.kernel.org" , Linux Kernel Mailing List , intel-wired-lan , Bjorn Helgaas , Linus Torvalds , todd.fujinaka@intel.com Subject: Re: [Intel-wired-lan] Linux 5.15-rc1 - 82599ES VPD access isue In-Reply-To: Message-ID: References: <20210913141818.GA27911@codemonkey.org.uk> <20210913201519.GA15726@codemonkey.org.uk> <20210913203234.GA6762@codemonkey.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 13 Sep 2021, Heiner Kallweit wrote: > On 13.09.2021 22:32, Dave Jones wrote: > > + Jesse and Tony as Intel NIC maintainers > >> On Mon, Sep 13, 2021 at 10:22:57PM +0200, Heiner Kallweit wrote: >> >> >> This didn't help I'm afraid :( >> >> It changed the VPD warning, but that's about it... >> >> >> >> [ 184.235496] pci 0000:02:00.0: calling quirk_blacklist_vpd+0x0/0x22 @ 1 >> >> [ 184.235499] pci 0000:02:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) >> >> [ 184.235501] pci 0000:02:00.0: quirk_blacklist_vpd+0x0/0x22 took 0 usecs >> >> >> > With this patch there's no VPD access to this device any longer. So this can't be >> > the root cause. Do you have any other PCI device that has VPD capability? >> > -> Capabilities: [...] Vital Product Data >> >> >> 01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) >> Subsystem: Device 1dcf:030a >> ... >> Capabilities: [e0] Vital Product Data >> Unknown small resource type 06, will not decode more. >> > > When searching I found the same symptom of invalid VPD data for 82599EB. > Do these adapters have non-VPD data in VPD address space? Or is the actual > VPD data at another offset than 0? I know that few Chelsio devices have > such a non-standard VPD structure. > >> >> I'll add that to the quirk list and see if that helps. >> >> Dave >> > Heiner Sorry to reply from my personal account. If I did it from my work account I'd be top-posting because of Outlook and that goes over like a lead balloon. Anyway, can you send us a dump of your eeprom using ethtool -e? You can either send it via a bug on e1000.sourceforge.net or try sending it to todd.fujinaka@intel.com The other thing is I'm wondering is what the subvendor device ID you have is referring to because it's not in the pci database. Some ODMs like getting creative with what they put in the NVM. Todd Fujinaka (todd.fujinaka@intel.com) From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hisashi T Fujinaka Date: Mon, 13 Sep 2021 16:32:39 -0700 (PDT) Subject: [Intel-wired-lan] Linux 5.15-rc1 - 82599ES VPD access isue In-Reply-To: References: <20210913141818.GA27911@codemonkey.org.uk> <20210913201519.GA15726@codemonkey.org.uk> <20210913203234.GA6762@codemonkey.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: On Mon, 13 Sep 2021, Heiner Kallweit wrote: > On 13.09.2021 22:32, Dave Jones wrote: > > + Jesse and Tony as Intel NIC maintainers > >> On Mon, Sep 13, 2021 at 10:22:57PM +0200, Heiner Kallweit wrote: >> >> >> This didn't help I'm afraid :( >> >> It changed the VPD warning, but that's about it... >> >> >> >> [ 184.235496] pci 0000:02:00.0: calling quirk_blacklist_vpd+0x0/0x22 @ 1 >> >> [ 184.235499] pci 0000:02:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) >> >> [ 184.235501] pci 0000:02:00.0: quirk_blacklist_vpd+0x0/0x22 took 0 usecs >> >> >> > With this patch there's no VPD access to this device any longer. So this can't be >> > the root cause. Do you have any other PCI device that has VPD capability? >> > -> Capabilities: [...] Vital Product Data >> >> >> 01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) >> Subsystem: Device 1dcf:030a >> ... >> Capabilities: [e0] Vital Product Data >> Unknown small resource type 06, will not decode more. >> > > When searching I found the same symptom of invalid VPD data for 82599EB. > Do these adapters have non-VPD data in VPD address space? Or is the actual > VPD data at another offset than 0? I know that few Chelsio devices have > such a non-standard VPD structure. > >> >> I'll add that to the quirk list and see if that helps. >> >> Dave >> > Heiner Sorry to reply from my personal account. If I did it from my work account I'd be top-posting because of Outlook and that goes over like a lead balloon. Anyway, can you send us a dump of your eeprom using ethtool -e? You can either send it via a bug on e1000.sourceforge.net or try sending it to todd.fujinaka at intel.com The other thing is I'm wondering is what the subvendor device ID you have is referring to because it's not in the pci database. Some ODMs like getting creative with what they put in the NVM. Todd Fujinaka (todd.fujinaka at intel.com)