Overview & identity
1572 resolves to I40E_DEV_ID_SFP_XL710 and is in the physical-function table. X710, XL710 and OEM naming must be reconciled with subsystem IDs and actual adapter inventory.
- Curated identifiers
pci 8086:1572
A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.
Driver & binding
i40e is the candidate established by this table. The driver guide discusses the 700-series NVM/FW relationship and SFP/QSFP devices; a host firmware package does not identify the adapter NVM.
i40e— kernel driver/module candidate
Firmware
Device/revision dependent
Adapter NVM/FW is part of this family’s deployment context. No exact host-loaded filename is established here; use the actual adapter/OEM identity and the observed firmware-version.
Read-only diagnostics
Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.
Check the PCI function and bound driver
lspci -nnk -s BDFReplace BDF with the domain:bus:device.function address. Look for [8086:1572] and Kernel driver in use. i40e in Kernel modules is only a candidate, not proof of binding.
Identify the network interface driver
ethtool -i INTERFACEReplace INTERFACE with the real interface name. Driver and bus-info connect this interface to its device. A displayed firmware-version is adapter information; it does not prove a file was loaded. Candidate: i40e.
Compare supported modes with the current link
ethtool INTERFACESupported/advertised link modes describe capability or negotiation offers. Speed, Duplex and Link detected describe the current link, not measured throughput. An unsupported query is a limitation of the interface/driver.
Separate PCIe transport from Ethernet speed
sudo lspci -vv -s BDFElevated access may be needed. Root can expose the full PCI configuration. If PCIe capabilities exist, compare LnkCap with LnkSta: maximum and negotiated PCIe speed/width are different from Ethernet speed. Legacy PCI or virtual functions may omit these fields.
Limitations & related issues
A physical-function match does not imply a guest uses i40e; virtual functions have separate identities and drivers. This source review is not a tested driver/NVM compatibility matrix.
These guides are linked for relevant observations, not as known defects of every device in this family.
- Ethernet has no carrier or repeatedly loses link · First documented next step
- Network transmit queue watchdog or hardware hang · First documented next step
Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab
References
Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.
- Upstream Linux: drivers/net/ethernet/intel/i40e/i40e_devids.h
Reviewed upstream source
I40E_DEV_ID_SFP_XL710; line 10 - Upstream Linux: drivers/net/ethernet/intel/i40e/i40e_main.c
Reviewed upstream source
PCI_VDEVICE(INTEL, I40E_DEV_ID_SFP_XL710); line 66 - Upstream Linux: Documentation/networking/device_drivers/ethernet/intel/i40e.rst
Project or distribution documentation
latest NVM/FW; line 39