Intel Networking Adapter/Device Linux Firmware
===========================================================================
Intel v27.6 Network FW Update Release for Linux
Release date = 06/24/2022
Package Version: net-9.0-6.0-1.3266.0-6
===========================================================================
CONTENTS
________
1.0 Change history
2.0 Web information and support phone Number
3.0 Notices and trademarks
4.0 Disclaimer
1.0 Change history
___________________
This release includes the following updates:
============================================
New features:
- Windows 10,11 support for X710-T2L/T4L and XXV710
- Support RHEL8.6/9.0, SLES 15SP4
Bug fixes:
- IPS: 00685894 - I210 Option Rom Request
Description:
Lenovo required support for specific 4-part ID, additional HII fields
in "NIC Configuration" menu for I210 AT, remove "Device Level
Configuration" and "iSCSI Configuration" fields
Fix:
Added and removed corresponding fields.
- IPS: 00729600 - XXV710 Link issues
Description:
While DC power cycle, the port maybe lose the link
Fix:
When the FW starts to run, retry to configure the Retimer in case of
error.
- IPS: 00725539 - x722 link down issue after NVM image update
Description:
After NVM image update to 800039xx, none of the 4 x722 ports connecting
a PHY OCP card can't link up even if an AC power cycle is applied
Fix:
The work-around is to forcibly change assigned port numbers to match the
PHY card configuration
1) The following X710/XXV710 images are at NVM 9.0 level with 1.3266.0 PREBOOT.
- System x and ThinkSystem X710-DA2 NVM
- ThinkSystem X710-T4 NVM
- ThinkSystem X710-DA4 NVM
- ThinkSystem X710-T2L PCIe NVM
- ThinkSystem X710-T2L OCP NVM
- ThinkSystem X710-T4L PCIe NVM
- ThinkSystem X710-T4L OCP NVM
- ThinkSystem X710-T2L Internal Lock OCP NVM
- ThinkSystem XXV710-DA2 NVM
- Intel I710-T4L 1G 4-Port RJ45 OCP NVM
- Intel I710-T4L 1G 4-Port RJ45 PCIe NVM
The following X710 images are at NVM 8.70 level with 1.3218.0 PREBOOT.
- X710-DA2 ML2 NVM
The other X710/XXV710 are at NVM 8.60 level with 1.3141.0 PREBOOT.
2) All X722 NVM images are at NVM 6.0 level with 1.3266.0 PREBOOT.
All these NVM images are with LLDP Agent disabled.
3) X550 NVM images are at NVM 3.60 level with 1.3141.0 PREBOOT.
4) PREBOOT 1.3218.0 update for I340, I350 adapters.
PREBOOT 1.3141.0 update for X520, X540 adapters.
PREBOOT 1.3282.0 update for I210 adapters.
5) NVMUPDATE tool updated to 1.39.5.5 to support new config version.
6) With the X710-T2L OCP 3.0 adapter, note that:
a. If you install and run this adapter in Lenovo's AMD-based SR635 or SR655 system, in RHEL7 or RHEL8 OS.
b. And if you plan to run Intel BOOTUTIL tool in the OS with Intel iqvlinux driver.
c. Then first, during system boot, you need to go into System BIOS and set IOMMU to disabled. Or restart the system and
go to System BIOS and set IOMMU to disabled.
d. Then Intel BOOTUTIL in Linux, with iqvlinux, should be functional and you can read OROM content for both ports.
e. If you have IOMMU enabled in the System BIOS, then you can only read the OROM content for the second port and first
port. The firt port would be displayed for Flash Firmware as "Flash Unknown".
NOTE that this is ONLY with AMD-based SR635/SR655 systems, and also ONLY with RHEL7 and RHEL8.
7) With v27.1 release, add support for new SKUs:
- ThinkSystem Intel X710-T2L 10GBASE-T 2-Port PCIe Ethernet Adapter
- ThinkSystem Intel X710-T4L 10GBASE-T 4-Port PCIe Ethernet Adapter
- ThinkSystem Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter
- ThinkSystem Intel X710-T2L 10GBASE-T 2-port Internal Lock OCP Ethernet Adapter
- ThinkSystem Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
8) With v27.3 release:
- FW/NVM updates for X722, X710, XXV710, I710 and X550 based products.
Add support for new SKUs:
- Intel I710-T4L 1G 4-Port RJ45 OCP Ethernet Adapter
- Intel I710-T4L 1G 4-Port RJ45 PCIe Ethernet Adapter
- Intel(R) Ethernet I210-T1 LOM
Note on Firmware Recovery Mode:
When a device is in Firmware Recovery mode it will not pass traffic or allow any configuration; you can only
attempt to recover the device's firmware. A device will enter Firmware Recovery mode if it detects a problem
that requires the firmware to be reprogrammed.
Resolving Firmware Recovery Mode Issues:
If your device is in Firmware Recovery mode you can restore it to factory defaults using the latest NVM
Update Package. Download the latest NVM Update Package from your vendor's support website and follow
the instructions in it.
*** NOTES:
- Before initiating device recovery, the integrity of the host operating system, device drivers
and firmware utilities must be verified and reinstalled if necessary. Fully functional operating
system, device drivers and tools are required for device recovery.
- AC power cycle your system even if the instructions do not indicate that an AC power cycle is required.
A power cycle is required to enable the device to restore and reload critical device settings to enable recovery.
To perform an AC power cycle, do the following:
a. Shut down the system if it is powered up.
b. Unplug all AC power cords from the system.
c. Leave the AC power cords unplugged for 15 seconds to allow the system power supply to discharge completely.
d. Plug in AC power cords to the system.
- Firmware Recovery Mode Errors and Messages:
When a device is in Firmware Recovery mode, the device drivers and preboot software and utilities may log or
display messages such as the following:
a. Firmware recovery mode detected. Limiting functionality.
Refer to the Intel(R) Ethernet Adapters and Devices User Guide for details on firmware recovery mode.
b. Firmware recovery mode detected. Initialization failed.
c. Firmware recovery mode detected. Limiting functionality.
d. PXE-E0C: Firmware recovery mode detected. Initialization failed.
2.0 Web Sites and Support Phone Number
______________________________________
o You can download new and updated files for Lenovo products from the Lenovo
Web site:
http://datacentersupport.lenovo.com/
o With the original purchase of an Lenovo hardware product, you have access to
extensive support coverage. During the Lenovo hardware product warranty
period, you may call the Lenovo HelpCenter for hardware product assistance
covered under the terms of the Lenovo hardware warranty.
3.0 Trademarks and Notices
__________________________
Lenovo is a registered trademark of Lenovo Corporation in the United States
and other countries.
Intel is a registered trademark of Intel Corporation in the United States
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States and
other countries.
Other company, product, and service names may be trademarks or service marks
of others.
4.0 Disclaimer
______________
THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.
Lenovo DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED,
INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS
FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE
INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, Lenovo
GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.
Note to U.S. Government Users -- Documentation related to
restricted rights -- Use, duplication or disclosure is subject
to restrictions set forth in GSA ADP Schedule Contract with
Lenovo Corporation.
Intel Networking Adapter/Device Utility
Release: 07/27/2022
===================
E810
-------------
New features:
- Support Windows 11
- Support RHEL8.6/9.0, SLES 15SP4
- Support scalable IOV feature (S-IOV) on the 4th Gen Intel® Xeon®
Scalable Processor with the following drivers and OS:
o ice 1.9.11 or later
o iavf 4.5.3 or later
o RHEL 7.9 and 8.5
o SLES 12.5 and 15.3
Note: Please refer to document for more details.
Bug fixes:
- IPS: 00665409 - [IO_Tatlow_BBFV[UEFI] Intel E810-DA2 PCIE Ethernet
Adapter changes do not take effect in network device.
Description:
During POST, in UEFI setup, set "Active Physical Functions" to "PF0"
and save. However, it will still be set to "All" after reboot.
Fix:
Added a check to ensure only PF0 is used during HII value set.
- IPS: 00673260 - E810 OCP adapter fails to link on D-Link switch but
E810 PCIe adapter is able to establish link
Description:
With the same setup, E810 PCIe adapter links up, but E810 OCP adapter
can't link up.
Fix:
Added new section in NVM to match the requirement and bring up link
correctly.
- IPS: 00688647 - BSOD seen on E810 ICEA driver when using SRIOV/RDMA
Description:
A customer has SR645 servers in a cluster running Windows 2019 Hyper-V.
with SRIOV and RDMA. Randomly the server crashes with a BSOD.
Fix:
Updated driver to use correct lock and set correct status of queues in
passive level thread
- IPS: 00711180 - E810-DA2 has no Share NIC feature
IPS: 00733937 - [PA_Bona_OOB_SDV_USI_SO] Unable to display XCC Shared
port of Intel E810 Network OCP under UEFI BMC Network Setting page
Description:
No Shared option and only Dedicated in the field of Network Interface
Port.
Fix:
Uses correct packageID definition in NVM image.
FVL/SGVL
--------
New features:
- Windows 10,11 support for X710-T2L/T4L and XXV710
- Support RHEL8.6/9.0, SLES 15SP4
Bug fixes:
- IPS: 00685894 - I210 Option Rom Request
Description:
Lenovo required support for specific 4-part ID, additional HII fields
in "NIC Configuration" menu for I210 AT, remove "Device Level
Configuration" and "iSCSI Configuration" fields
Fix:
Added and removed corresponding fields.
- IPS: 00729600 - XXV710 Link issues
Description:
While DC power cycle, the port maybe lose the link
Fix:
When the FW starts to run, retry to configure the Retimer in case of
error.
Release: 04/18/2022
===================
New adapters:
- Intel(R) Ethernet I210-T1 LOM
E810
-------------
None
FVL/SGVL
--------
New features:
- SPR PCIe BUS Segmentation with Single MCTP Bus Owner - Platform Errata
Workaround
Description:
ICX/Sapphire Rapids have implemented PCIe BUS Segmentation while using
a single MCTP bus owner across all segments. It is expected that
segmentation will be used on SPR platforms due to the large number of
PCIe lanes. Chipset uses the high 3 bits of the MCTP Destination
Endpoint ID as a segment number to route the MCTP over PCIe VDM packets
to the proper segment. Once the Endpoint has been enumerated, this is
OK since the endpoint will recognize the EID. However, the DMTF
DSP0238 spec defines a NULL destination EID for the Set Endpoint ID
command, and FVL will drop packets that have an unrecognized
destination EID. The Platform team has been requested to submit an
Errata.
Long term requirement may be addressed in the DMTF. Short term to
ensure NIC devices (FVL onwards) can work on SPR the pDCR proposes a
Workaround to accommodate the Platform behavior.
- Prevent PFR Failure caused by Full Switch Table
Description:
PF reset timeout on SW side was too low in case were PF was loaded with
filters. This resulted in PF not able to finish the reset in time and
SW reporting PF reset failed. PF reset fails because the MAC/VLAN table
is full. Add filters to one PF, then PFR to another PF.
- Customer option to replace Powerville with FVL-based Carlsville
Adapters restricted to 1GbT / 100M at a lower price
Bug fixes:
- IPS: 00654228 - XXV710 Ping failure with VXLAN and Duplicate MAC
address across different VNI
Description:
When using VXLAN on XXV710, 2 VMs in different VNI's with the same MAC
address. Ping from VM01 to VM02 failed when the intel NIC offload
function is enabled, but it did not fail when the intel NIC offload
function is disabled.
Fix:
Added the filter class type check, configure Rx queue additional MAC
filter for inner MAC of overlay network
- IPS: 00606050 - Swapping x722 2port PHY card with 4 port PHY causes issue
Description:
Swap 2 ports card for 4 ports card. After swap, 4 ports card is not seen.
Fix:
If the PCIe Alt Autoload section does not match the OCP PHY card, the
FW does not update the PCIe Alt Autoload contents when a new OCP card
is found. It results in the default Device ID is used.
Cover the different PHY while the device ID doesn't match.
- FW has dropped the Discovery Notify Response from Bus Owner if Rq Bit
is False but accepts otherwise
Description:
Expected Discovery Notify Request received and response is accepted.
However, response is NOT accepted if Rq Bit in response is cleared.
Fix:
Exception for discovery notify response added
- Thermal sensor update interval miscalculated at initialization
Description:
The thermal sensor update interval is miscalculated when assigning it
to sensor register struct. The value should be multiplied by 10,
instead it is multiplied by 1000
Fix:
Implemented new macro for update interval conversion for all thermal sensors.
- Size of Vendor Revision on QSFP isn't equal to 2 bytes
Description:
This field is used for comparison on QSFP modules. If word contains
some data not equal to zero, then Vendor Revision field comparison with
data from EEPROM will fail. Vendor Revision mask in SFP/QSFP Exception
List section cannot work properly on QSFP modules.
Fix:
Use correct size for QSFP.
- Default PLDM polling time used as minimum sensor period
Description:
Default PLDM polling time was used as minimum polling time when
registering a sensor. It makes it so the highest value is always
assigned to PLDM polling time.
Fix:
Changed conditional assignment to direct assignment for sensorEnt.
- FVL sends MCTP Resolve Endpoint ID command as a datagram
Description:
FVL sends Resolve Endpoint ID commands with the D bit set in the MCTP
header. This is incorrect since a response is expected.
Fix:
Fixed D bit.
- FVL sends unexpected MCTP Resolve Endpoint ID command
Description:
After a reboot and MCTP enumeration, FVL sends an unexpected Resolve
Endpoint ID command.
Fix:
A switch between SMBUS and PCIe implemented
- After set Link Down or Link Up connection dropped event and connection
established event occurs after 40s.
Description:
After set Link Down or Link Up connection dropped event and connection
established event occurs after 40s instead of right after trigger event
Fix:
RDE Events are now independent of PLDM polling.
- FW does not response for Get Endpoint ID command when OOB is bus master
Description:
FW does not response for Get Endpoint ID command when OOB is bus
master, discovery process not completed
Fix:
Remove particular code to prevent reset when Endpoint discovery already
triggered
Release: 02/11/2022
===================
New adapters:
- Intel E810-DA4 10/25GbE SFP28 4-port PCIe Ethernet Adapter
- Intel E810-DA4 10/25GbE SFP28 4-port OCP Ethernet Adapter
- Intel E810-DA2 10/25GbE SFP28 2-Port Internal Lock OCP Ethernet Adapter
- Intel X710-T2L 10GBASE-T 2-Port PCIe Ethernet Adapter
- Intel X710-T4L 10GBASE-T 4-Port PCIe Ethernet Adapter
- Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter
- Intel X710-T2L 10GBASE-T 2-port Internal Lock OCP Ethernet Adapter
- Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter
E810
-------------
New features:
- 8x10/2x100 PSM4 Link Management Support
Description:
Support for multiple port options (2x100, 8x10) with external PHY
- Control thermals on SFF modules
Description:
Proper logic control for thermals on SFF modules, including a valid /
invalid thermal Measurement and valid / invalid thermal threshold.
- Allow separate FC Configuration
Description:
Support differential configuration of Flow Control for Rx and Tx.
- CWDM SFP Optic Support
- Driver Start/Stop, Disable/Reset Cmdlet and configuration FW Logging on
Windows
Description:
Improvements to firmware log files from customers to show more detailed
information by adding cmdlets making it easier to start and stop
logging to a log file, disable/reset logging levels for all modules.
It only applies to Windows OS
- Align Lenovo AIM Firmware Information 2 version display in UEFI HII
with PLDM changes
Description:
Lenovo requests that UEFI HII portion which implements Lenovo AIM
formset shall display the same version information.
- Added support for Intel PSM4 optical module
- Added ADQ rules results in allocating Recipes, which are limited
resources that are shared across all PFs
- RDE Port Schema Support
Description:
Replace the deprecated NetworkPort schema based resources with new Port
schema based resources. Additionally, support Port.Reset action.
- RDE PCIeFunction FunctionID Property
Description:
Support the FunctionId property in the PCIeFunction schema
Bug fixes:
- After RDE Operation Kill port to phy update isn't available
Description:
After RDE OperationKill, port 0 isn't available to execute phy update.
Fix:
Add phy access flag clear after operation kill.
- Health Status Code 0x511 not generated
Description:
Health Status Code 0x511 not generated if new NetList is unsigned
during update, which results in no failure info.
Fix:
Added health status report in the needed fail flows.
- Following a firmware update and reboot/power cycle on the Intel
Ethernet CQDA2 Adapter, Port 1 is displaying NO-CARRIER and is not
functional.
- Added a state machine to the thermal threshold activity so that when
the switch page fails, it tries again from the same state.
- FW not allow link if module not supported in lenient mode.
- RDE Device is reporting a RevisionID property of PCIeFunctions schema
as 0x00, instead 0x02.
- The RDE device reports its status as Starting (with low power), even
though it is in standby mode.
FVL/SGVL
--------
New features:
- Redefine Lenovo Value and Proton Maps
Description:
Lenovo Value and Proton platforms use Lenovo's PHY3 and PHY4 PHY cards.
Lenovo's ODM swap the KR routing of the card but keep the I2C control
the same.
Create new Adaptive NVM Super-Features for use on Lenovo’s Value and
Proton platforms when PHY3 or PHY4 are used.
- Exposes Link Status CSRs
Description:
Exposes PRTMAC_LINKSTA and PRTMAC_PCS_LINK_STATUS1 which are used to
determine the MAC clock frequency. Otherwise when a link goes down, the
MAC clock frequency can revert to default settings, independent of the
previous link speed.
- Sageville X550 - NC-SI OEM command to configure PXE VLAN from BMC
Description:
A new Intel OEM NC-SI command to get temperature. Please refer to
"System Manageability" chapter in the latest version of datasheet for
more details.
Bug fixes:
- Ping latency issues using SRIOV with x722 on Linux
with Cisco N5K, link flapping occurs
IPS: 00595945/00631653 Ping latency issues using SRIOV with x722
Description:
ping latency from VMs using SRIOV VF of function ID 1 to the external
switch was very big like 7-15 seconds per the log.
Fix:
Calculates MSI_X VF vectors and the PCI VF count properly.
- Linked 2-3 ports from 4-port FPK (SR630 or SR650 with x722 4x10Gb SFP+)
with Cisco N5K, link flapping occurs
IPS: 00558803 x722 4x10Gb SFP+ fails to link with Cisco N5K switch
Description:
SR630 or SR650 with x722 4x10Gb SFP+ Cisco N5k switch fw 7.3(3)N1(1)
and 7.3(5)N1(1) OS is NA. The failure can be seen when booted to F1
setup.
Fix:
Enable KR-Cortina-Swap bit and get Cortina Channels mapped properly
- NCSI is not responding
IPS: 00594654 NCSI is not supported on port 2 of X722 on SD530
Description:
The ncsi response of "clear init state command" from the port2 is
abnormal and only port 1 is supported on NCSI response
Fix:
Sending the command with the same IID can cause that NCSI will went
into "wrong" state and will not respond for command, need one context
to store the most recent response.
- FVL-1G/10G: Use Fixed CTLE on SFP NICs
IPS: 00580545 Intel XXV710-DA2 PCIe 25Gb 2-Port SFP28 Adapter LED issue
Description:
Harbor Channel reports that the link is up when a 10G optical module is
inserted with no fiber connected. The failing modules are
Lenovo-branded Finisar SR modules: Lenovo PN 46C3447
Fix:
Change the FW such that the Rx Calibration Mode field in the NVM is
used for any optical module. Since the mode is set to Fixed CTLE on all
SFP FVL25 NICs, this change will result in using Fixed CTLE for all
optical modules.
- NCSI response of Controller Information - missing uEFI firmware version
Description:
When using NCSI OEM command of "controller information" to get the uEFI
firmware version. NCSI response data may only return PXE firmware
version but missing uEFI firmware version information.
Fix:
To fill up this structure with correct data length.
- No audit log is generated while plugging/unplugging cable.
IPS: 00652126 When the cable is plugged and unplugged ML2, there is no
audit log in XCC
Description:
In UEFI, plug in the cable -> wait 3 mins -> unplug the cable -> wait 3
mins, then check the audit log in XCC => no log
Fix:
Generate proper log and output.
- X550 card missing during JPMT MQT2 AC cycle
IPS: 00639948 Intel X550 card missing during JPMT MQT2 AC cycle
Description:
Intel X550 card will be missing during JPMT MQT2 AC cycle, could be
reproduced on other SUT with different Intel X550 card.
Fix:
The failure is caused by a hang of the PCIe Gen3 equalization process
in the PCIe PHY on short channels. As a result of this hang, there is
a timeout in the LTSSM of the root port and the link test fails.
Relax the stability criterion for VGA1 such that it will be considered
stable even with the additional jitter.
Release: 07/16/2021
===================
E810
-------------
New features:
- Get SFF Temperature reporting via Intel OEM NC-SI command
Description:
A new Intel OEM NC-SI command to get temperature. Please refer to
"System Manageability" chapter in the latest version of datasheet for
more details.
- Get serial Number and Product Number via Intel OEM NC-SI command
Description:
A new Intel OEM NC-SI command to get SN and PN. Please refer to "System
Manageability" chapter in the latest version of datasheet for more
details.
- Enable and disable LLDP via Intel OEM NC-SI command
Description:
A new Intel OEM NC-SI command to configure the current and persistent
settings of the FW LLDP agent and returns the configurations. Please
refer to "System Manageability" chapter in the latest version of
datasheet for more details.
- Define response to NCSI command Get Version ID
Description:
Dev Starter version from NVM instead of FW Build will be reported.
Please refer to "System Manageability" chapter in the latest version of
datasheet for more details.
- Double VLAN Mode and RDMA Compatibility
Description:
Update FW for RDMA can determine a VLAN tag in double VLAN mode.
- RDMA VMware support
Description:
Support RDMA in VMware
- Health Status Message Reporting
Description:
Provide end-user friendly critical error and message reporting
mechanism, including detectable & recoverable issues, both errors and
other important messages. Below are some message examples, the message
will be in the dmesg log.
* the device is in firmware recovery mode
* the flash chip cannot be accessed
* NVM authentication failed
* option ROM authentication failed
- FW logging support
Description:
Improve FW logging mechanism, support info acquire, sync log, etc.
linux example:
make -j CFLAGS_EXTRA='-DFWLOG_SUPPORT'
modprobe ice dyndbg='+p' fwlog_events=0x0FFFFFFF fwlog_level=0x8 (# Log only ERROR for ALL events)
firmware log will be reported in dmesg.
windows example:
$AdapterName = "YourTestAdapterHere"
$LoggingConfig = @("C008") (to enable module 8 (AQ module) for error and flow level logging)
New-NetAdapterAdvancedProperty -Name $AdapterName -RegistryKeyword FwLoggingMode -RegistryDataType REG_DWORD -RegistryValue 1
New-NetAdapterAdvancedProperty -Name $AdapterName -RegistryKeyword FwLoggingConfigs -RegistryDataType REG_MULTI_SZ -RegistryValue $LoggingConfig
firmware log will be reported in ETL log.
For more details, please contact intel.
- 10G speed support during link establishment even if the SFP28 optic
module EEPROM doesn't specify 10G support (specific to Lenovo E810 NVM
images)
Description:
without this feature, E810 with such SFP28 optics will not link up when
the link partner supports 10G only.
- UEFI HII Port Disable feature
Description:
Implement a BIOS setup option (HII) that allows the end users to
configure the LAN to disable the port.
Bug fixes:
- PLDM reports corrupted Plug Thermal sensor thresholds
Description:
To support for reading SFF Thermal sensor thresholds, module thresholds
are used. Some PLDM flows keep using structures allocated for Netlist,
which are invalid in the context of SFF modules/plugs.
DNL always zeros 'fractional' part of the thresholds, Warning and Fatal
thresholds initialized to 0 while only Critical threshold incidentally
gets the correct value.
'Zero' thresholds are reported by PLDM and potentially mislead the BMC
into making fatal decisions:
- Zero Warning - BMC may decide to constantly drive the fan
- Zero Fatal - BMC may decide to shut-down the entire server
Fix:
Properly use thermal sensor parameters output of Link API for case of
SFP thermal sensors
- PLDM FW update fails
Description:
PLDM FW update reports "the image may be invalid"
Fix:
In PLDM Header, Netlist version string have two null characters at the
end. However, one is expected. Changed null symbol filtering inside
netlist version string parsing function. Now FW support any number of
null symbols at the end of string.
- CVL/Link not restored unless Asynchronous Health Status message is cleared
Description:
When an empty cage health status event is triggered, until the message
is cleared the affected port will not link, even after the cage is
filled
Fix:
After the cage is filled, recover the link.
- When sending a get link status command (0x0a) on channels 1 the link
status of channel 2 is reported and vice versa
Description:
When sending a get link status command (0x0a) on channels 1 the link
status of channel 2 is reported and vice versa
Fix:
Do necessary logical port, mac port conversions
- TEMP_WARN, TEMP_CRIT & FAN_ON_AUX signals are not set properly as per
OCP spec for Aspen flat
Description:
The signals of TEMP_WARN, TEMP_CRIT & FAN_ON_AUX are not set as OCP
spec.
Fix:
Polarity is configured by netlist and should be set differently for
FAN_ON_AUX (positive) and TEMP_WARN_N and TEMP_CRIT_N (negative).
FVL/SGVL
--------
New features:
- Report EETRACK ID via NC-SI
Description:
A new Intel OEM NC-SI command to get EETrack Id. Please refer to
"System Manageability" chapter in the latest version of datasheet for
more details.
- Report Manufacturing Date via NC-SI
Description:
A new Intel OEM NC-SI command to get manufacturing date. Please refer
to chapter "System Manageability" chapter in the latest version of
datasheet for more details.
- NC-SI ASIC Temperature Reading
Description:
A new Intel OEM NC-SI command to get ASIC temperature. Please refer to
chapter "System Manageability" chapter in the latest version of
datasheet for more details.
- FW Version in NC-SI Get Version ID
Description:
A new Intel OEM NC-SI command to get FW version. Please refer to
chapter "System Manageability" chapter in the latest version of
datasheet for more details.
- Intel OEM Get VPD over NC-SI
Description:
A new Intel OEM NC-SI command to get VPD information. Please refer to
chapter "System Manageability" chapter in the latest version of
datasheet for more details.
Bug fixes:
- Add the hot fix to "boot menu issue" of all FVL8.4 UEFI drivers
IPS: 00632987 Boot menu display abnormal after updating Intel FW.
Description:
Update FW to 1.2992.0. Reboot the SUT and press F12 to boot to the boot
menu, Error occurred. The function of the card is still normal.
Generic UEFI string was used instead of branching string for child
handle.
Fix:
For child handle, branding string is displayed.
- Add the hot fix to the "x710/x722 firmware version string issue"
IPS: 00631440 NVM ID of x722 lom display abnormal under UEFI & XCC
after upgrade the firmware
Description:
Update fw to 1.2992.0-all-0 (OSS:123002), check version under uefi, it
displays "0x80002E63", it should be "80002E63".
Fix:
Remove 0x.
- xxv710-DA2 mdio bus confliction
IPS: 00635602 XXV710 link down when disconnect/reconnect fiber cable
with 10Gb SFP+ optics
Description:
Disconnect the fiber cable from the SFP+ module multiple times can lead
to link down.
Fix:
FVL7.2 added UNVL temperature polling which is indirect action. FVL
firmware is asking UNVL FW that it will "read" the temperature in next
few cycles, and after 460ms it's coming to read UNVL temperature. In
the "polling temperature period" FVL firmware read/write some
information from UNVL through DNL actions which caused UNVL FW stuck.
- x722 NVM images to enable WOL for all ports
IPS: 00514245 x722 NIC port down after excessive reboot
Description:
While rebooting the server many times, ethtool reports no link on port.
Fix:
the workaround is to enable wol on all x722 ports
- x722/x710 NVM images to enable "allow pxe disable"
IPS: 00626858 The system can still boot into PXE server(Legacy mode)
when set "Legacy Boot Protocol" to None.
Description:
In UEFI Setup, Setup Menu - Boot Manager - Boot Modes - System Boot
Mode, set "Legacy Boot Protocol" to None, the system still boots into
PXE mode.
Fix:
enable "allow pxe disable" bit in the NVM image.
- Proton/Value uses a new version map
Description:
* The Identifier of the OCP PHY used and the Super-Feature IDs are
incorrect. This causes the FW not to identify the PHY as one of the
Cortina PHY’s that need to the I2C channel swap. The fix is a FW change
only.
* The bit to enable the “KR Cortina Swap” feature is located in a RO
word. This means that Lenovo FPKs images will not be able to be updated
to enable the feature
Fix:
the nvm image uses a new version map to fix the issue.
- EETrackId is returned in wrong endianess
Description:
Intel OEM NC-SI command reports EETrackId which is in wrong endianess.
Fix:
Swapped bytes in two words of eetrackid
- FW provided contain wrong FW version information
Description:
FW doesn't contain the correct minor version information
Fix:
Changed to correct minor version.
- Link speed conflict error reporting is not accurate
Description:
While setting Phy config and NC-SI Set Link are in different speed, Set
link Parameter Conflict error instead of Set link Speed Conflict error
is reported.
Fix:
Check all combinations to decide the error.
