HBA 1200 Software/Firmware Release Notes

1. About This Release

The release described in this document includes firmware, OS drivers, tools, and host management software for the HBA 1200 solutions from Microchip.

1.1 Release Identification

The firmware, software, and driver versions for this release are shown in the following table.

ARCCONF/maxView: 4.14.0.26064

PLDM: 6.25.9.0

1.2 Files Included in this Release

This section details the files included in this release.

Driver Files

Table 1-4. Windows Drivers

Table 1-5. Linux Drivers

Notes:

• New OS support—minimally tested drivers in this release. Fully supported drivers are expected in the next release.
• Support based off August 2022 RHEL 9.0 ISO refresh.

Table 1-6. FreeBSD and VMware Drivers

Note: Though provided driver bundle includes drivers for several other OSes, only versions mentioned above have been QA tested and are officially supported in this release.

Host Management Software

2. What's New?

This section shows what's new in this release.

2.1 Fixes and Enhancements

This section shows the fixes and enhancements for this release.

2.1.1 Firmware Fixes

This section shows the firmware fixes and enhancements for this release.

2.1.1.1 Fixes and Enhancements for Firmware Release 03.01.23.72

• Added support for Remote Key Management of Managed SED.
• Added support for 256 bytes Key Management Service (KMS) key identifier.
• Added support to improve flash interoperability with UBM backplanes.
• Enabled power sensor monitoring.
• Added support for full 15-byte controller serial number through PBSI.
• Added support for cascaded expander to uniquely identify the attached enclosure and physical devices.
• Moved VDM message processing to a lower priority thread to allow for quicker responses to PCIe configuration cycles from the Host.
• Added support in PBSI to show maximum and negotiated link rate for physical drives.
• Fixed an issue for Managed SED in Local Key Management (LKM) mode where firmware allows to import the foreign SED while the adapter password is not received yet.
  • Root Cause: Firmware does not check for the received adapter password while processing the request to import a foreign SED. Firmware should fail the request if the adapter password is not provided as the master key is not available until the adapter password is provided. Without the master key, importing a foreign SED cannot be performed.
  • Fix: Firmware will check if the adapter password is not received then fail the request.
  • Risk: Low
• Fixed an issue where the slot number is shown as unknown for a failed physical drive present in SES supported enclosure.
  • Root Cause: The SCSI Enclosure Services (SES) supported enclosure will provide multiple additional status pages(0Ah), which consist of each physical drive's information such as the device type, WWN or SAS address, slot number and so on. This additional status page data will be compared against the controller-detected enclosure-specific data. On a successful comparison, the firmware will assign the slot number for the physical drive. For a failed physical drive, the WWN or SAS address comparison failed and resulted in firmware skipping the slot number assignment.
  • Fix: If the physical drive is detected by the controller and WWN or SAS address comparison failed, then compare the device slot number. If it matches, assign the slot number to the physical drive.
  • Risk: Low
• Fixed an issue where the controller is reset to factory defaults and RAID is lost after an abrupt reboot.
  • Root Cause: An abrupt reboot during the local controller settings update caused its corruption and the discovery protocol of all the connectors got reset to default (that is, SGPIO). When the UBMx4 backplane is connected to the controller using a bifurcated connector, each bay will have two PHYs. As controller settings were reset, the firmware is not aware that each bay supports multiple PHYs and added both handles from the same PHY as different entries. Now firmware detects identical RAID metadata in two physical drives, fails to identify the right data, and ignores the RAID metadata.
  • Fix: Added logic to check and discard duplicate handles from the same physical drives.
  • Risk: Low
• Fixed an issue where the foreign unconfigured SED is not exposed to the OS after import.
  • Root Cause: If any foreign unconfigured SED is connected to the controller, the controller firmware will fail to access the RAID metadata region of the SED, as it is locked. The controller firmware will not expose this foreign SED to OS until it gets unlocked, to avoid any operations on the SED. While importing the foreign SED, firmware does not try to access the RAID metadata region and is not exposing the SED to the host.
  • Fix: Firmware will access the RAID metadata region of the SED while importing. If the read is successful, the firmware will expose the SED to the host.
  • Risk: Low
• Fixed an issue where a controller lockup may occur after an interrupted clear configuration operation with Managed SED logical drives.
  • Root Cause: When a clear configuration operation is interrupted due to a panic shutdown, the next boot up results in the controller reading the datastore on the SED that may indicate a RAID metadata range is enabled. The firmware then sets a flag indicating the RAID metadata range already exists. When a new Managed SED logical drive is created, the controller skips creating the RAID metadata range and the next system boot sequence the firmware has a lockup trying to save the RAID metadata because the firmware should not have skipped creating the RAID metadata range.
  • Fix: Firmware saves a flag in NVRAM to indicate a clear configuration process is occurring, and if interrupted, on the next boot up reverts the SED to OFS. Subsequent logical drive creations will ensure the RAID metadata range is created.
  • Risk: Low
• Fixed an issue where the firmware does not block the revert with PSID on a configured foreign SED.
  • Root Cause: Firmware should block the revert with PSID for a configured foreign SED.
  • Fix: Firmware blocks the revert with PSID on a configured foreign SED.
  • Risk: Low
• Fixed an issue where an Uncorrectable error PSOD observed after power on Nutanix VM.
  • Root Cause: The firmware logs to the UART every time there is a BME bit change. Logging to the UART adds additional latency. In some corner cases, using the UART logging results in the firmware taking longer than 10 ms to respond to the PCIe Configuration Write to change the BME bit, resulting in an Unsupported Request response back to the originator of the PCIe Configuration Write TLP.
  • Fix: Moved the logging of the BME bit change to the internal logging system rather than to the UART.
  • Risk: Low
• Fixed an issue where Non-fast path commands stuck in SAT firmware pending queue.
  • Root Cause: In some special cases, non-fast path commands such as INQUIRY can remain stuck in the firmware's SAT command pending queue, if the command cannot be sent out during NCQ traffic.
  • Fix: On completion of NCQ commands, add firmware to service the pending queue.
  • Risk: Medium
• Fixed an issue where Error on Test Unit Ready (TUR) command for NVMe SEDs.
  • Root Cause: The SCSI-to-NVMe translation for the TUR issues a Read command which the drive rejects if the drive is still locked.
  • Fix: Added a unique flag to mark I/Os as TURs. The NVMe completion path detects the completion for the TUR with the check condition for SCSI sense key MEDIUM ERROR (03) and ASC/ASCQ ACCESS DENIED - INVALID LU IDENTIFIER (20/09) and if the drive is NVMe SED, the firmware changes the check condition status to a good status.
  • Risk: Low
• Fixed an issue where controller not assigned with EID.
  • Root Cause: In this issue, BME is disabled when the controller attempts to send a Discovery Notify to the MCTP bus owner as per the specification. The controller will set a retry timer to attempt another Discovery Notify after 5 seconds. There is a corner case where BME is enabled, the Set EID comes from the host, and the retry timer expires and the controller sends the Discovery Notify. This sequence violates the specification because the Discovery Notify follows the Set EID. For this reason, the discovery fails and the controller is marked as Unknown by the MCTP Bus owner.
  • Fix: If the Discovery Notify return timer is enabled when a Set EID message is received, disable the Discovery retry mechanism.
  • Risk: Medium
• Fixed an issue where the Unique ID of different SATA disks is the same in Windows.
  • Root Cause: The controller is reporting the same unique ID for a SATA drive in the same slot, even if the SATA drives are different family models because the lower level firmware did not register its API to the upper level callback firmware function pointer used to enable retrieving the unique ID from the SATA drive.
  • Fix: Register the lower level firmware API to the upper level firmware callback function pointer to enable retrieving the unique ID from the SATA drive.
  • Risk: Low
• Fixed an issue where controller was incorrectly returning mode page information regarding the Write Cache attribute of NVMe drives.
  • Root Cause: The controller is incorrectly marking the write cache setting as non-changeable.
  • Fix: Add translation to the SCSI-to-NVME translation firmware to ensure that if the NVMe drive supports volatile write cache, then to report the write cache is changeable.
  • Risk: Low
• Fixed an issue where OS fails to see controller due to long boot time due to a locked SED timing out command.
  • Root Cause: When an I/O times out, it takes a long time to recover that I/O. SED drive is timing out lots of I/Os so it takes too long to discover this drive. This failure does go away when the drive is unlocked.
  • Fix: Set a flag when a locked SED fails a command for I/O timeout and stop post spinup operations. When drive is unlocked, check this flag and then do post spinup operations.
  • Risk: Medium
• Fixed an issue when the local mode has managed SED encryption enabled and tries to change the master key identifier without changing the master key does not successfully update the new master key identifier.
  • Root Cause: Logic was not saving the new master key/master key identifier values in the NVRAM.
  • Fix: Updated logic to make sure to check if master key/master key identifier has valid data, so it gets updated in NVRAM.
  • Risk: Low
• Fixed an issue that controller firmware flashed event has random characters at the end of the event message.
  • Root Cause: When logging the event, a local variable that saves the active ROM image is used without being initialized. The variable is a two-byte array. The first byte is used to save "A" or "B", ROM image version. The second byte is expected to be 0, and it is used at the end of the event message. Since the array is not initialized, "A" or "B" is not null terminated, so random characters could appear at the end of the event message.
  • Fix: Initialize the local variable before putting it into use.
  • Risk: Low
• Fixed an issue where taking ownership of enterprise drive was failing on boot after panic shutdown.
  • Root Cause: When changing a master key occurs, several SED authorities are changed to a new key. This SED flow (open the session, perform an SED task, and end session) gets interrupted due to panic shutdown, but drives are not power-cycled (hence, not reset) since the drives are attached to an enclosure which has its own power source. The drive is left in some state and expecting the next SED operation. Instead, now due to reboot, firmware restarts and attempts to open a new session to validate the datastore on the drive and a start session failure occurs.
  • Fix: When start session failure occurs, depending on the failure, error recovery is implemented and then retries a start session.
  • Risk: Low
• Fixed an issue where firmware lockup is observed after hot removing a SES device while a LUN reset to the device is in progress.
  • Root Cause: While processing a host-issued LUN reset to the device and if the device is hot removed, LUN reset task management is completed and cleared from the management list for the device. Lockup is observed when firmware attempts to clear LUN reset task management again for the removed device.
  • Fix: Before issuing reset to the device, if the device does not exist and LUN reset task management is not present in the list, then the reset request is already cleared, so firmware should not attempt to clear it again.
  • Risk: Low
• Fixed an issue where the I/O latency value is not as expected for NCQ priority SMR drives.
  • Root Cause: The RAID path did not have support for NCQ priority commands.
  • Fix: Added support for priority bits in messages derived from the driver and propagate to lower layer firmware interface.
  • Risk: Low
• Fixed an issue where firmware fails to capture vendor-specific expander log.
  • Root Cause: This is caused by a code change that firmware relies on the driver to provide data transaction direction. The Linux SCSI layer is providing direction as data-out instead of data-in. This failed in CentOS 7.9 but passed in RHEL 9.1. This kind of incompatibility happened among various flavors of Linux if we depended on the driver for data transaction direction.
  • Fix: For T10 supported commands like inquiry, firmware does not depend on the driver for data transfer direction. It sets it according to the T10 specification. The fix is that firmware sets the data transfer direction as data-in for the read expander log only based on the WDC OEM specification, and does not rely on the driver's input.
  • Risk: Low
• Fixed an issue where maxView reports for an NVMe SSD Predictive fail but other tools do not report any failure.
  • Root Cause: The NVMe Translation layer is returning Predictive Failure if any of the “critical” bits are set in a drive's SMART/Health Information log page. Specifically in this issue, the bits indicating under or over temperature are set to “1” which will cause a Predictive Failure response.
  • Fix: The bit for over or under temperature should be excluded from this check as this condition is not representative of a Predictive Failure.
  • Risk: Low

2.1.2 UEFI/Legacy BIOS Fixes

This section shows the UEFI/Legacy BIOS fixes and enhancements for this release.

2.1.2.1 Fixes and Enhancements for UEFI Build 2.8.3/Legacy BIOS Build 2.8.2

• Added Remote Key Management support for controller-managed SED encryption. The remote key management server is utilized for encryption key generation and storage.
• Added controller password support for the Remote mode controller-managed SED encryption.
• Added multi actuator devices support for EFI SCSI pass through protocol. The EFI SCSI pass through protocol supports device enumeration and pass thru commands to multi actuator devices.
• Fixed an issue where PCIe slot information is not provided in the configuration tools.
  • Root Cause: UEFI driver does not get the PCIe slot information from EFI SMBIOS protocol.
  • Fix: Find PCIe slot number from the connected host root bridge configuration space if the slot information is not found in EFI SMBIOS protocol method.
  • Risk: Low

2.1.3 Driver Fixes

This section shows the driver fixes and enhancements for this release.

2.1.3.1 Windows Driver Fixes

This section shows the Windows driver fixes and enhancements for this release.

2.1.3.1.1 Fixes and Enhancements for Windows Driver Build 1010.74.0.1020

• Added registry value "LunResetBehavior" feature. Setting this registry value changes the SRB_FUNCTION_RESET_LOGICAL_UNIT behavior. The new LUN reset behavior is to return the SRB status after the internal TMF LUN reset command completes. If the TMF does not complete, the driver will let it hang until timeout. The new behavior for the TMF LUN reset timeout is set to what the SRB timeout passes into the miniport. HW_RESET_BUS hardware callback routine will pause the controller I/O for up to 25 seconds while checking to see if controller completes all I/O within 18 seconds. If I/O is still not completed then the callback hardware bus reset will be failed. If the driver does not detect any outstanding I/O after 18 seconds, then the hardware bus reset callback will be marked as successful. Note: The new reset LUN behavior will only occur if the registry value "LunResetBehavior" is present and set to 1.
• Fixed an issue where the random drives in the system were going offline after a hot plug and reboot.
  • Root Cause: Incorrect logic in traversing the report_physical_lun response while hot adding drives to the system. In the drive hotplug handling path, the driver was using an incorrect size while traversing the list of physical devices without checking the firmware feature support.
  • Fix: Added logic to check the firmware feature set to determine the size of the RPL entry while traversing the RPL response.
  • Risk: Low
• Fixed an issue where an incorrect tag table is assigned for PQI queue groups.
  • Root Cause: The incorrect tag table assignment for the PQI queue groups when there are more than eight NUMA nodes present in the system. The driver was skipping the creation of IOBypass queues associated with certain queue groups because of the invalid tag table assignment.
  • Fix: Resolved issues with the invalid tag table assignment when there are more than eight NUMA nodes present within the system.
  • Risk: Medium

2.1.3.2 Linux Driver Fixes

This section shows the Linux driver fixes and enhancements for this release.

2.1.3.2.1 Fixes and Enhancements for Linux Driver Build 2.1.24-046

• Added support for ABORT handler in the driver in order to avoid I/O stalls across all devices attached to a controller when I/O requests time out.
• Added sysfs entry for NUMA node in /sys/block/sdX/device. NUMA node detail is added for each exposed device similar to NVMe devices.

2.1.3.3 VMware Driver Fixes

This section shows the VMware driver fixes and enhancements for this release.

2.1.3.3.1 Fixes and Enhancements for VMware Driver Build 4530.0.104

• Fixed an issue when PSOD occurs while attempting to access memory which had already been released.
  • Root Cause: PSOD happened when one CPU released a device and freed memory. Simultaneously, another CPU was attempting to free the same memory triggered by a hot-plug timeout.
  • Fix: Modifications made to avoid the double-freeing of the device memory.
  • Risk: Medium
• Fixed an issue where the Hotswapped HBA drives are detected after 20 minutes or when a manual rescan is done.
  • Root Cause: When a new device is hotswapped with an old device on the same slot, both the new and the old device will have the same scsi3addr. Due to this, the new device will be assigned the marked for removal flag status, resulting in not being added to the new device list during device discovery.
  • Fix: The device marked for removal flag status will only be set if scsi3addr, model number, and serial number of both devices are equal. If scsi3addr is the same but serial or model number are different, the drive will be detected as new and will be added to the new device list.
  • Risk: Low

2.1.3.4 FreeBSD Driver Fixes

This section shows the FreeBSD driver fixes and enhancements for this release.

2.1.3.4.1 Fixes and Enhancements for FreeBSD Driver Build 4410.0.1005

There are no known fixes for this release.

2.1.4 Management Software Fixes

This section shows the management software fixes and enhancements for this release.

2.1.4.1 maxView Storage Manager/ARCCONF Fixes

This section shows the maxView Storage Manager/ARCCONF fixes and enhancements for this release.

2.1.4.1.1 Fixes and Enhancements for maxView Storage Manager/ARCCONF Build 26064

• Added remote Key management service (KMS) support for the managed SED.
• Added support to display the CPLD revision and Platform image revision in Arcconf and maxView.
• Added UBM controller firmware upgrade support in Arcconf and maxView.
• Added SPDM Certificate Storage and Management support.
• Fixed an issue where phantom enclosures are displayed under every connector when there was a VPP backplane in the configuration.
  • Root Cause: maxView/Arcconf was discovering invalid enclosure object per connector when there is a VPP backplane in the configuration.
  • Fix: Implemented changes to skip adding the invalid enclosure objects without a SEP device to the configuration.
  • Risk: Low
• Fixed an issue where invalid enclosure slot count was displayed in maxView.
  • Root Cause: maxView was displaying invalid connector IDs for an enclosure where enclosure has multiple expanders in it, resulting in wrong slot count.
  • Fix: Implemented changes to add the proper connector ID for the enclosure with multiple expanders.
  • Risk: Low
• Fixed an issue where GETSMARTSTATS command is failing in Arcconf.
  • Root Cause: The Arcconf command resolver could not find the associated GETSMARTSTATS command resulting in a failure to execute the command.
  • Fix: Implemented changes to load the GETSMARTSTATS command in Arcconf.
  • Risk: Low
• Fixed an issue where auto discovery function in maxView is not working in a specific configuration.
  • Root Cause: The firewall setting was blocking SSDP packets which were used for auto discovery functionality. This resulted in maxView not discovering the specific windows machines during auto discovery.
  • Fix: Added firewall inbound rule for the maxView Redfish server port. Also, a discover button in auto discovery dialog to refresh the auto discovered servers in maxView.
  • Risk: Low

2.1.4.2 PLDM Fixes

This section shows the PLDM fixes and enhancements for this release.

2.1.4.2.1 Fixes and Enhancements for PLDM Release 6.25.9.0

• Added support for self-contained activation of storage enclosure firmware flashed using Type 5 downstream device firmware update.
• Added RDE READ support for the following property annotations to the VolumeCapabilities resource:
  • CapacityBytes@Redfish.AllowableNumbers
  • MediaSpanCount@Redfish.AllowableNumbers
  • StripSizeBytes@Redfish.AllowableNumbers
• Added a new descriptor of Type 0x010A (IEEE EUI-64 Identifier) for NVMe drives appearing in the response to a QueryDownstreamIdentifiers request.
• Changed the Availability state set of the controller composite state sensor to require a rearm in order to transition from a state of Starting to Enabled.
• Changed the Version state set of the controller composite state sensor to reflect changes in firmware version in downstream devices in addition to the controller.
• Updated the Storage resource to use the v1.14.0 schema and added RDE READ support for the following properties:
  • Encryption Mode
  • LocalEncryptionMode
• All drives connected to the controller which are not configured as a data or spare drive for a RAID Volume resource will now have an associated Volume resource, informally referred to as an HBA Volume or JBOD Volume, with RAIDType of "None" automatically created by the controller.
• These Volumes will have Redfish URIs and PLDM Type 5 resource IDs listed in the Volume PDR published using a GetPDR request for that PDR handle.
• Configuration changes such as creation and deletion of RAID Volumes and unconfigured drive removal or insertion will result in pldmPDRRepositoryChgEvent events being sent to any active event listeners.
• RDE READ for an unconfigured drive resource will have a Links.Volumes entry for its associated HBA Volume resource.
• RDE READ for the StorageController resource will have the value of "None" added to its SupportedRAIDTypes value array.
• RDE READ for the VolumeCollection resource will have entries for HBA Volumes in its Members property array, and Members@odata.count will add these Volume resources to its count value.
• Fixed an issue where PLDM Type 5 downstream device firmware update fails on Microchip (SXP 24G SAS-4 Expander) SEPs.
  • Symptom: PLDM Type 5 GetFirmwareData fails on SXP 24G SAS-4 Expanders.
  • Root Cause: PLDM uses 16K buffer chunks; whereas, SXP 24G SAS-4 Expanders will only accept 4K buffers.
  • Fix: For expander SEPs, break the 16K buffer into 4K chunks for flashing.
  • Risk: Low
• Fixed an issue of inappropriate returning Allow equal to POST on Storage and Drive to advertise the actions.
  • Symptom: Redfish clients observe the POST value being returned in the Allow header for Redfish requests for Drive and Storage resources when only GET and HEAD should be returned.
  • Root Cause: The implementation of RDE ACTION operations for these resources erroneously included a change to set the CREATE bit in the PermissionFlags bitfield in RDE command responses.
  • Fix: Reverted the setting of the PermissionFlags CREATE bit for these resources when ACTION operation support has been negotiated.
  • Risk: Low.
• Fixed an issue when the energy pack is not required, StorageController[CacheSummary] [Status][Health] shall be OK.
  • Symptom: Users would receive cache and battery alerts on systems where an energy pack is not applicable. Redfish StorageController[CacheSummary][Status][Health] would show statuses other than OK when an energy pack was not applicable and there were no ECC errors.
  • Root Cause: Incorrect assumptions on what hardware setups are available to users.
  • Fix: Added checks for read cache percentage and NBWC to determine if a backup power source is applicable. Cache and battery alerts are filtered if a backup power source is not applicable. Redfish StorageController[CacheSummary][Status][Health] will be OK if a backup power source is not applicable and there are no ECC errors.
  • Risk: Medium
• Fixed an issue for possible memory leak in RDE GET on a Drive resource.
  • Symptom: An RDE Get operation will have a memory leak if one of the Binary Encoded JSON (BEJ) encoding calls fails while encoding the Identifiers section of the response.
  • Root Cause: The macros used to perform the BEJ encoding perform an early return after logging the error. In the case of the Identifiers section there is a buffer that is allocated before the encoding starts which needs to be freed once the encoding completes. The early return skips the code that performs the free.
  • Fix: New macros were created that set a flag rather than return early. The flag is used to skip down to the free call early. After the free, if the flag is set the code performs the return.
  • Risk: Low
• Fixed an issue where PLDM Type 2 GetPDRRepositoryInfo returns incorrect RepositorySize when no physical drives are present.
  • Symptom: Mismatch in the PDR Repository size and number of records for a PLDM terminus when a user queries the PLDM Type 2 GetPDRRepositoryInfo command for a configuration with zero drives.
  • Root Cause: A Drive Action PDR is still present in the repository despite there not being any drives present on the device.
  • Fix: Deleting Drive Action PDR when all drives are removed if Action is negotiated. Re-adding Drive Action PDR when the first drive gets added if Action is negotiated.
  • Risk: Low

2.2 Limitations

This section shows the limitations for this release.

2.2.1 General Limitations

This release includes the following general limitations.

• The following are the limitations of Multi-Actuator:
  • Supports only:
    • HBA drive
    • Windows/Linux/VMware
    • Intel/AMD
    • UEFI mode (for multi-LUN display)

2.2.2 Firmware Limitations

This section shows the firmware limitations for this release.

2.2.2.1 Limitations for Firmware Release 03.01.23.72

• Persistent Event Logs (PEL) will be cleared under the following conditions:
  • Upgrading from firmware releases prior to 03.01.17.56 to 03.01.17.56 or later firmware releases
  • Downgrading from firmware releases 03.01.17.56 or later to firmware releases prior to 03.01.17.56
• Firmware downgrade from firmware version 3.01.23.72 to any older firmware version is blocked if Managed SED is enabled.
  • Workaround: Disable Managed SED and try firmware downgrade.
• Managed SED cannot be enabled on the controller when reboot is pending after firmware downgrade from firmware version 3.01.23.72 to any older firmware version.
  • Workaround: Reboot the controller and enable the Managed SED.
• Power cycle to the enclosure may be needed if connected server goes through abnormal shutdown under the following condition: SED operation on OPAL drives like taking ownership, reverting the ownership, or changing the master key where firmware internally performs open session, performs SED management, and ends session gets interrupted due to abnormal shutdown on the server. This condition causes firmware to restart on reboot while drives are left off in the middle of performing SED task so drives need to be power cycled also.
  • Workaround: Allow the change master key operation to complete before shutting down the server.
• If SEDs are in an external enclosure, power cycle the external enclosure and SEDs before powering up the server with the controller.
• Under certain high-traffic conditions, if SATA drives are present on a port with Dynamic Channel Multiplexing (DCM) 6G SATA operation enabled and the drives are attached to an expander, controller lockup may occur.
  • Workaround: Firmware detects this configuration and will drop the link to 12G from 24G.

2.2.3 UEFI/Legacy BIOS Limitations

This section shows the UEFI/Legacy BIOS limitations for this release.

2.2.3.1 Limitations for UEFI Build 2.8.3/Legacy BIOS Build 2.8.2

There are no known limitations for this release.

2.2.4 Driver Limitations

This section shows the driver limitations for this release.

2.2.4.1 Windows Driver Limitations

This section shows the Windows driver limitations for this release.

2.2.4.1.1 Limitations for Windows Driver Build 1010.74.0.1020

There are no known limitations for this release.

2.2.4.2 Linux Driver Limitations

This section shows the Linux driver limitations for this release.

2.2.4.2.1 Limitations for Linux Driver Build 2.1.24-046

• This release includes the following limitation when doing a driver injection (DUD) install. On some distributions (RHEL7.9, RHEL8.2, RHEL8.3, SLES15SP2, and SLES15SP3), the DUD install will hang if an attached drive (either HBA mode or Logical Volume) has Write Cache enabled.
  • Workaround: There are two workarounds for this issue:
    • Ensure that the Write Cache is disabled for any attached drive.
    • For RHEL7.9/8.2/8.3 add rd.driver.blacklist=smartpqi to the grub entry along with inst.dd.
• RHEL driver injection (DUD) install where OS ISO is mounted as virtual media on BMC-based servers (non-ILO). Installer will hang after driver injection. It is reported on RHEL 8.5, 8.6, 9.0, and 9.1.
  • Workaround:
    • Load the OS from a USB device instead of virtual media.
    • Load the OS from virtual media but initiate ISO verification (media test) during the installation followed by ESC to cancel the media test.
    • Edit grub to include the boot argument "nompath". Replace "inst.dd" with "nompath inst.dd" for DUD install.
• Oracle 9 UEK 7 kernel causes SmartPQI rpm dependency failures. This is an issue with how the kernel package was created by Oracle. Correct UEK7 kernel for Oracle 9, which is expected in the mid-October UEK7 release, version number is still pending. Note: This does not affect Oracle 8 UEK 7.
  • Workaround: Install the rpm using "--nodeps" when dependency failures occur.
• Update:
  • For SmartPQI driver versions > 2.1.20-020 and UEK7 kernels >= 5.15.0-3.60.2.el9uek.x86_64, the SmartPQI rpm will install normally.
  • For UEK7 kernels < 5.15.0-3.60.2.el9uek.x86_64, the SmartPQI rpm needs to be installed using the "--nodeps".
• On AMD systems, the system might crash or hang due to a bug in the IOMMU module. For details, see lore.kernel.org/linux-iommu/20191018093830.GA26328@suse.de/t/.
  • Workaround: Disable the IOMMU setting option in BIOS.
• When multiple controllers are in a system, udev(systemd) can timeout during kdump/kexec resulting in an incomplete kdump operation. The indication of the timeout is the following console log entry: "scsi_hostX: error handler thread failed to spawn, error = -4".
  • Workaround: Extend the udev(systemd) timeout during a kdump operation. Perform the following steps to increase the timeout for udev(systemd):
    1. vi /etc/sysconfig/kdump
    2. add udev.event-timeout=300 to KDUMP_COMMANDLINE_APPEND
    3. systemctl restart kdump
    4. systemctl status kdump

2.2.4.3 VMware Driver Limitations

This section shows VMware driver limitations for this release.

2.2.4.3.1 Limitations for VMware Driver Build 4530.0.104

• A controller lockup may occur when using VMDirectPath on an single processor AMD system. Lockup has only been seen within a Linux Guest VM. No known workaround at the present time.

2.2.4.4 FreeBSD Driver Limitations

This section shows FreeBSD driver limitations for this release.

2.2.4.4.1 Limitations for FreeBSD Driver Build 4410.0.1005

There are no known limitations for this release.

2.2.5 Management Software Limitations

This section shows management software limitations for this release.

2.2.5.1 maxView Storage Manager/ARCCONF Limitations

This section shows the maxView Storage Manager/ARCCONF limitations for this release.

2.2.5.1.1 Limitations for maxView Storage Manager/ARCCONF Build 26064

• Import foreign device operation will fail to import the foreign drive/logical device when the remote master key is in ASCII format and the length is less than 32 characters.
  • Workaround: To import the foreign drive/logical device with an ASCII format master key which has less than 32 characters length, convert the master key from ASCII format to HEX format and input the HEX value.

2.2.5.2 PLDM Limitations

This section shows the PLDM limitations for this release.

2.2.5.2.1 Limitations for PLDM Release 6.25.9.0

There are no known limitations for this release.

3. Updating the Controller Firmware

This section describes how to update the controller firmware to the latest release.

3.1 Updating Controllers to Latest Firmware

If running firmware is 3.01.00.006 or lower, please contact Adaptec Apps team at ask.adaptec.com.

3.1.1 Upgrading to 3.0X.XX.XXX Firmware

1. For controllers running 3.01.02.042 or higher firmware, flash with 3.0X.XX.XXX version of firmware "SmartFWx200.bin" provided in this package using maxview or ARCCONF utility.
2. Power cycle the server.

4. Revision History

Microchip Information

The Microchip Website

Microchip provides online support via our website at www.microchip.com. This website is used to make files and information easily available to customers. Some of the content available includes:

• Product Support – Data sheets and errata, application notes and sample programs, design resources, user's guides and hardware support documents, latest software releases and archived software
• General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online discussion groups, Microchip design partner program member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factory representatives

Product Change Notification Service

Microchip's product change notification service helps keep customers current on Microchip products. Subscribers will receive email notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest.

To register, go to www.microchip.com/pcn and follow the registration instructions.

Customer Support

Users of Microchip products can receive assistance through several channels:

• Distributor or Representative
• Local Sales Office
• Embedded Solutions Engineer (ESE)
• Technical Support

Customers should contact their distributor, representative or ESE for support. Local sales offices are also available to help customers. A listing of sales offices and locations is included in this document. Technical support is available through the website at: www.microchip.com/support

Microchip Devices Code Protection Feature

Note the following details of the code protection feature on Microchip products:

• Microchip products meet the specifications contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is secure when used in the intended manner, within operating specifications, and under normal conditions.
• Microchip values and aggressively protects its intellectual property rights. Attempts to breach the code protection features of Microchip product is strictly prohibited and may violate the Digital Millennium Copyright Act.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code protection does not mean that we are guaranteeing the product is “unbreakable". Code protection is constantly evolving. Microchip is committed to continuously improving the code protection features of our products.

Legal Notice

This publication and the information herein may be used only with Microchip products, including to design, test, and integrate Microchip products with your application. Use of this information in any other manner violates these terms. Information regarding device applications is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. Contact your local Microchip sales office for additional support or, obtain additional support at www.microchip.com/en-us/support/design-help/client-support-services.

THIS INFORMATION IS PROVIDED BY MICROCHIP "AS IS". MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.

IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW, MICROCHIP'S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USE WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR THE INFORMATION.

Use of Microchip devices in life support and/or safety applications is entirely at the buyer's risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated.

Trademarks

The Microchip name and logo, the Microchip logo, Adaptec, AVR, AVR logo, AVR Freaks, BesTime, BitCloud, CryptoMemory, CryptoRF, dsPIC, flexPWR, HELDO, IGLOO, JukeBlox, KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST, MOST logo, MPLAB, OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer, QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.

AgileSwitch, APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, Flashtec, Hyper Speed Control, HyperLight Load, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus, ProASIC Plus logo, Quiet- Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra, TimeProvider, TrueTime, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A.

Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, Augmented Switching, BlueSky, BodyCom, Clockstudio, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, Espresso T1S, EtherGREEN, GridTime, IdealBridge, In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, IntelliMOS, Inter-Chip Connectivity, JitterBlocker, Knob-on-Display, KoD, maxCrypto, maxView, memBrain, Mindi, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE, Ripple Blocker, RTAX, RTG4, SAMICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SmartHLS, SMART-I.S., storClad, SQI, SuperSwitcher, SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, Trusted Time, TSHARC, USBCheck, VariSense, VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.

SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.

The Adaptec logo, Frequency on Demand, Silicon Storage Technology, and Symmcom are registered trademarks of Microchip Technology Inc. in other countries.

GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries.

All other trademarks mentioned herein are property of their respective companies.

Quality Management System

For information regarding Microchip's Quality Management Systems, please visit www.microchip.com/quality.

Worldwide Sales and Service

AMERICAS

Corporate Office
2355 West Chandler Blvd.
Chandler, AZ 85224-6199
Tel: 480-792-7200
Fax: 480-792-7277
Technical Support: www.microchip.com/support
Web Address: www.microchip.com

Atlanta
Duluth, GA
Tel: 678-957-9614
Fax: 678-957-1455

Austin, TX
Tel: 512-257-3370

Boston
Westborough, MA
Tel: 774-760-0087
Fax: 774-760-0088

Chicago
Itasca, IL
Tel: 630-285-0071
Fax: 630-285-0075

Dallas
Addison, TX
Tel: 972-818-7423
Fax: 972-818-2924

Detroit
Novi, MI
Tel: 248-848-4000

Houston, TX
Tel: 281-894-5983

Indianapolis
Noblesville, IN
Tel: 317-773-8323
Fax: 317-773-5453

Los Angeles
Mission Viejo, CA
Tel: 949-462-9523
Fax: 949-462-9608

Raleigh, NC
Tel: 919-844-7510

New York, NY
Tel: 631-435-6000

San Jose, CA
Tel: 408-735-9110
Tel: 408-436-4270

Canada - Toronto
Tel: 905-695-1980
Fax: 905-695-2078

ASIA/PACIFIC

Australia - Sydney
Tel: 61-2-9868-6733

China - Beijing
Tel: 86-10-8569-7000

China - Chengdu
Tel: 86-28-8665-5511

China - Chongqing
Tel: 86-23-8980-9588

China - Dongguan
Tel: 86-769-8702-9880

China - Guangzhou
Tel: 86-20-8755-8029

China - Hangzhou
Tel: 86-571-8792-8115

China - Hong Kong SAR
Tel: 852-2943-5100

China - Nanjing
Tel: 86-25-8473-2460

China - Qingdao
Tel: 86-532-8502-7355

China - Shanghai
Tel: 86-21-3326-8000

China - Shenyang
Tel: 86-24-2334-2829

China - Shenzhen
Tel: 86-755-8864-2200

China - Suzhou
Tel: 86-186-6233-1526

China - Wuhan
Tel: 86-27-5980-5300

China - Xian
Tel: 86-29-8833-7252

China - Xiamen
Tel: 86-592-2388138

China - Zhuhai
Tel: 86-756-3210040

India - Bangalore
Tel: 91-80-3090-4444

India - New Delhi
Tel: 91-11-4160-8631

India - Pune
Tel: 91-20-4121-0141

Japan - Osaka
Tel: 81-6-6152-7160

Japan - Tokyo
Tel: 81-3-6880-3770

Korea - Daegu
Tel: 82-53-744-4301

Korea - Seoul
Tel: 82-2-554-7200

Malaysia - Kuala Lumpur
Tel: 60-3-7651-7906

Malaysia - Penang
Tel: 60-4-227-8870

Philippines - Manila
Tel: 63-2-634-9065

Singapore
Tel: 65-6334-8870

Taiwan - Hsin Chu
Tel: 886-3-577-8366

Taiwan - Kaohsiung
Tel: 886-7-213-7830

Taiwan - Taipei
Tel: 886-2-2508-8600

Thailand - Bangkok
Tel: 66-2-694-1351

Vietnam - Ho Chi Minh
Tel: 84-28-5448-2100

EUROPE

Austria - Wels
Tel: 43-7242-2244-39
Fax: 43-7242-2244-393

Denmark - Copenhagen
Tel: 45-4485-5910
Fax: 45-4485-2829

Finland - Espoo
Tel: 358-9-4520-820

France - Paris
Tel: 33-1-69-53-63-20
Fax: 33-1-69-30-90-79

Germany - Garching
Tel: 49-8931-9700

Germany - Haan
Tel: 49-2129-3766400

Germany - Heilbronn
Tel: 49-7131-72400

Germany - Karlsruhe
Tel: 49-721-625370

Germany - Munich
Tel: 49-89-627-144-0
Fax: 49-89-627-144-44

Germany - Rosenheim
Tel: 49-8031-354-560

Israel - Ra'anana
Tel: 972-9-744-7705

Italy - Milan
Tel: 39-0331-742611
Fax: 39-0331-466781

Italy - Padova
Tel: 39-049-7625286

Netherlands - Drunen
Tel: 31-416-690399
Fax: 31-416-690340

Norway - Trondheim
Tel: 47-72884388

Poland - Warsaw
Tel: 48-22-3325737

Romania - Bucharest
Tel: 40-21-407-87-50

Spain - Madrid
Tel: 34-91-708-08-90
Fax: 34-91-708-08-91

Sweden - Gothenburg
Tel: 46-31-704-60-40

Sweden - Stockholm
Tel: 46-8-5090-4654

UK - Wokingham
Tel: 44-118-921-5800
Fax: 44-118-921-5820