Re: [Intel-wired-lan] Linux 5.15-rc1 - 82599ES VPD access isue
From: Hisashi T Fujinaka
Date: Mon Sep 13 2021 - 19:41:59 EST
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@xxxxxxxxx
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@xxxxxxxxx)