Versions: - BIOS: R02.03.0003 - ME: 02.01.07.328 - BMC: 01.21.6038 - FRUSDR: 0.23 BIOS R02.03.0003 - This version enhances the protection of certain UEFI variables as described in Intel Security Advisory INTEL-SA-00038 BMC changes in release 01.21.6038 - Fixed: BMC User configuration is corrupted and users cannot be re-created. - Fixed: The response of getting satellite fw update status is always 01 - Fixed: HSC slots status present sensor showed NA in EWS. - Fixed: (X) Disk Drive LED - Locating drive is inconsistent in time to illuminate and stop - Fixed: Hot Plug Fan not changing system status on Fan failure. - Fixed: EWC Fan sensor readings disappear when filtered and there is a fan failure. - Fixed: (X) BMC hung after network Scan. - Fixed: Current power is incorrect on EWS while power down SUT by pressing power button. - Fixed: Special characters '<>' of FRU info can't be shown in the EWS page. - Fixed: Recurring temperature alarms on sensor #0x22(SSB). - Fixed: DIMM Thrm Mrgn sensor shows "unknown" when just plug DIMM in Channel3 - Fixed: [X] Updated Java signitures to support new JAVA requirements. - Fixed: Get SOL Configuration parameters 5 & 6 should not return invalid response. - Fixed: EWS is incorrectly decoding ME firmware update SEL events. - Fixed: BMC channle 1 can not ping succesfully and EWS login fail while using static IPV6 address. - Fixed: Baseboard IP address can't be assigned when IPv6 address set as auto-configuration. - Fixed: IP address can't be assigned when IPv6 address set as dynamic. - Fixed: BMC Hangs during first A/C power up. - Fixed: CFM calculation failed on PSU removal/insertion. - Fixed: Enable FPGA logic to preserve PWM registers. - Fixed: Check in 750AB V8 PSU image per PSU verification team's request - Fixed: Porting FRU discovery APIs from Grantley where the Auto-Configuration feature requires the operational status of the managed FRUs. - Fixed: Add the displaying of the PS HW Revison for the PS if update is required or not. ME changes in release 02.01.07.328 - Fixed: Platform is not able to power on properly after being shut down by NM Policy. - Fixed: Global platform power consumption reported by NM Statistics in S5 is incorrect. - Fixed: OOB (out-of-band) stress test by issuing the wrong username may cause connection to be unavailable. - Fixed: Shutdown action can be interrupted by cold reset when volatile NM policy is in use. FRUSDR changes in release 0.23 - Changed LC/LNC thresholds for all CPUs to match processor specs.
Скачать