Can not read VPD data of BCM 5720

[Gridsah]

I have a HPE Microserver Gen10 with the latest BIOS and FreeBSD 13.2-p2 installed. I find some 'fails' on /var/log/messages:

...
Aug  3 10:53:19 gen10 kernel: pcib3: failed to allocate initial prefetch window: 0xf0800000-0xf08fffff
...
Aug  3 10:53:19 gen10 kernel: pci0:3:0:0: no valid vpd ident found
Aug  3 10:53:19 gen10 kernel: pci0:3:0:0: failed to read VPD data.
...
Aug  3 10:53:19 gen10 kernel: pci0:3:0:1: no valid vpd ident found
Aug  3 10:53:19 gen10 kernel: pci0:3:0:1: failed to read VPD data.
...

from:

......
Aug  3 10:53:19 gen10 kernel: pcib3: <ACPI PCI-PCI bridge> at device 2.5 on pci0
Aug  3 10:53:19 gen10 kernel: pcib3: failed to allocate initial prefetch window: 0xf0800000-0xf08fffff
Aug  3 10:53:19 gen10 kernel: pci3: <ACPI PCI bus> on pcib3
Aug  3 10:53:19 gen10 kernel: pci0:3:0:0: no valid vpd ident found
Aug  3 10:53:19 gen10 kernel: pci0:3:0:0: failed to read VPD data.
Aug  3 10:53:19 gen10 kernel: bge0: APE FW version: NCSI v1.4.1.0
Aug  3 10:53:19 gen10 kernel: bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
Aug  3 10:53:19 gen10 kernel: miibus0: <MII bus> on bge0
Aug  3 10:53:19 gen10 kernel: brgphy0: <BCM5720C 1000BASE-T media interface> PHY 1 on miibus0
Aug  3 10:53:19 gen10 kernel: bge0: Using defaults for TSO: 65518/35/2048
Aug  3 10:53:19 gen10 kernel: bge0: Ethernet address: b8:83:03:46:05:3c
Aug  3 10:53:19 gen10 kernel: pci0:3:0:1: no valid vpd ident found
Aug  3 10:53:19 gen10 kernel: pci0:3:0:1: failed to read VPD data.
Aug  3 10:53:19 gen10 kernel: bge1: APE FW version: NCSI v1.4.1.0
Aug  3 10:53:19 gen10 kernel: bge1: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
Aug  3 10:53:19 gen10 kernel: miibus1: <MII bus> on bge1
Aug  3 10:53:19 gen10 kernel: brgphy1: <BCM5720C 1000BASE-T media interface> PHY 2 on miibus1
Aug  3 10:53:19 gen10 kernel: bge1: Using defaults for TSO: 65518/35/2048
Aug  3 10:53:19 gen10 kernel: bge1: Ethernet address: b8:83:03:46:05:3d

It is my /etc/rc.conf file below:

root@gen10:~ # vim /etc/rc.conf
hostname="gen10"
# NTP configs
ntpd_enable="YES"
sshd_enable="YES"
powerd_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
zfs_enable="YES"

# network configs
#ifconfig_bge0="DHCP"
ifconfig_bge0="up"
ifconfig_bge1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="up laggproto lacp laggport bge0 laggport bge1 lagghash l3,l4 DHCP"
...

I googled for this problem, and got nothing. But BCM5720 network interface works well.

What is VPD? How can I make this 'fail' no longer appear?

 

[Charlie_]

What is VPD?

https://en.wikipedia.org/wiki/Vital_Product_Data

For the VPD messages, that seems to be a spurious warning:

e.g. https://www.dell.com/support/kbdoc/...ns-vpd-access-failure-during-reboot-of-sles15

 

[VladiBG]

Try to update your LOM firmware to 1.42

https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_ed48a6b463ea47de8c42d19c90&tab=releaseNotes

 

[Gridsah]

https://en.wikipedia.org/wiki/Vital_Product_Data

It looks like I have nothing to do.

 

[Gridsah]

Try to update your LOM firmware to 1.42

https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_ed48a6b463ea47de8c42d19c90&tab=releaseNotes

What does it aim for? This driver is for Windows Server. In my opinion, either updating the BCM5720 driver of FreeBSD or updating something stored on the motherboard may repair the problem.

Should I install a Windows Server, run the update program, and switch back to FreeBSD?

 

[Charlie_]

Is this relevant? PR 272018
MFC not yet.

 

[Gridsah]

Is this relevant? PR 272018
MFC not yet.

It looks similar, but my knowledge does not allow me to determine whether the problem I encountered is the same as described in this link.

 

[VladiBG]

What does it aim for? This driver is for Windows Server. In my opinion, either updating the BCM5720 driver of FreeBSD or updating something stored on the motherboard may repair the problem.

Should I install a Windows Server, run the update program, and switch back to FreeBSD?

You can do this by installing supported OS or using Intelligent provisioning.

 

[Gridsah]

And one more thing, where does 'pcib3: failed to allocate initial prefetch window: 0xf0800000-0xf08fffff' from?

Does the VPD problem lead to this initial prefetch window failure?
Does the initial prefetch window failure lead to this VPD problem?

Which one is the reason?

 

[Charlie_]

pcib3: failed to allocate initial prefetch window: 0xf0800000-0xf08fffff

PR 263038

 

[Gridsah]

PR 263038

Yes, that's it. It is almost the same problem.

I found this report yesterday, but no one replied to it.

 

[Gridsah]

Try to update your LOM firmware to 1.42

https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_ed48a6b463ea47de8c42d19c90&tab=releaseNotes

I had already updated the NIC boot code from 1.39 to 1.42, but nothing changed. The VPD problem is still shown in /var/log/messages.

 

[VladiBG]

Can you create a bootable USB with 14.0-Current and boot to LiveCD and check the dmesg output to see if it's resolved from PR 272018

 

[Gridsah]

OK. I'll let you know the results after the test tonight.

FreeBSD-14.0-CURRENT-amd64-20230727-474708c334a7-264358-disc1.iso

 

[Gridsah]

Can you create a bootable USB with 14.0-Current and boot to LiveCD and check the dmesg output to see if it's resolved from PR 272018

I entered FreeBSD-14.0-CURRENT-amd64-20230720-a52f23f4c49e-264226-disc1.iso live CD, and the VPD problem disappeared. But the initial prefetch window failure is still here.

For the VPD problem in my Freebsd 13.2-p2, it seems I can only switch to Freebsd 14 to fix it.

What about the initial prefetch window failure?

 

[Gridsah]

the VPD problem disappeared. But the initial prefetch window failure is still here.

FreeBSD-14.0-CURRENT-amd64-20230727-474708c334a7-264358-disc1.iso did the same

 

[ralphbsz]

General comment, doesn't just apply to this poster or this thread: Please do not post photos of text output. Cut and paste the text output itself. That makes it much more readable, searchable, and accessible to those with disabilities (such as bad eyesight).

 

[Gridsah]

General comment, doesn't just apply to this poster or this thread: Please do not post photos of text output. Cut and paste the text output itself. That makes it much more readable, searchable, and accessible to those with disabilities (such as bad eyesight).

Although I have already described the content of the picture in text, ok, I will pay attention.