================================================================================ Intel(R) Server Board S2600KP Product Family Firmware Update Package for Intel(R) One Boot Flash Update Utility and Windows* Preboot Execution Environment ================================================================================ Intel Enterprise Platform & Services Division - Marketing Intel Corporation 2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA ================================================================================ DATE : January 15, 2016 TO : Intel(R) Server Board S2600KP Product Family customers SUBJECT : Release Notes for System Firmware Update Package ================================================================================ ABOUT THIS RELEASE ================================================================================ BIOS: 01.01.0020 ME: 03.01.03.043 BMC: 01.48.10351 FRUSDR: 1.14 ================================================================================ Support Platforms and Dependency ================================================================================ Processors supported: Intel(R) Xeon processor E5-2600 v3 series Intel(R) Xeon processor E5-2600 v4 series Microcode update versions: CPUID Version Status 0x306f2 0x00000039 Production (E5-2600 v3 C0/C1) 0x406f1 0x0b00001f External (E5-2600 v4 B0) Production boards: Product Fab Version S2600KP Fab3 or above S2600KPF Fab3 or above The following update process must be followed to ensure a trouble free update. 1. Manageability Engine (ME) firmware 2. FD 2. BMC firmware 3. BIOS 4. FRUSDR ================================================================================ IMPORTANT NOTE!!! ================================================================================ - This Update package must be installed using Intel(R) One-boot Flash Update (OFU) V14.0 Build 14 ================================================================================ System Firmware Update Package Usage instructions ================================================================================ This package can be updated using one of the following methods: - Windows* or Linux* operating system using Intel(R) One-boot Flash Update (OFU) V14.0 Build 14 Intel(R) One boot Flash Update utility can be downloaded from http://downloadcenter.intel.com/ and it is part of the "BIOS, Firmware Update & Configuration Utilities" for Windows* and Linux*. Please refer to Intel(R) OFU user guide about the details of installation and usage of OFU. Use OFU to update system firmware by the following steps: - Install OFU on Windows* or Linux* system - Download the latest firmware update package from http://downloadcenter.intel.com/ - Unzip package to a folder - Run the following command in Windows* command line/Linux* terminal window: :\flashupdt -u \flashupdt.cfg To update from Windows* Preboot Execution Environment (WinPE) The System Firmware Update Package can be inserted to Windows* PE customized image for creating a bootable Windows* PE CD. User is able to update system firmware from customized WinPE CD by the following steps: - Boot server with customized WinPE CD - Run script "WinPE21_x64_Update.bat" (name may be varied depends on your own customization) Note: 1. The Intel(R) OFU utility is case sensitive. Therefore, when you transfer the Firmware Update Package using USB flash drive from a Microsoft Windows* system to a Linux environment, you must first extract under the Linux* environment. Otherwise, you will need to mount the USB flash drive manually with 'vfat' option under Linux to avoid conversion from upper case to lower case and vice versa. 2. To make Intel(R) OFU utility run properly under x86 or x64 OS, you have to read OFU release notes on known issues for OFU installation. 3. In this SFUP package, Intel only provide batch file "WinPE_x64_Update.bat" for WinPE2.1/3.0 64 bit solution as an example. Please refer to white paper "White Paper-Intel Server Utilities Procedure for WinPE.pdf" for details on building your own customized WinPE CD. 4. Windows PE 2.0 - built from Windows Vista SP1 EM64T 5. Windows PE 2.1 - built from Windows Vista SP1 or Windows Server 2008, EM64T 6. Windows PE 3.1 - built from Windows Server 2008 R2, EM64T 7. Microsoft IPMI driver is loaded by default from WinPE CD, if you want to use Intel IPMI driver instead of MS IPMI driver for firmware update, you can un-install Microsoft IPMI driver by: Devicesetup.exe ¨Cv remove *IPI0001 Note: IPI0001 is the device ID for Microsoft IPMI driver. 8. If to update backup BIOS region or NVRAM, you need to customize the OFU update scripts (eg.flashupdt.cfg) and add "UpdateBackupBios" or "UpdateNvram" parameter. ================================================================================ IMPORTANT NOTICE ================================================================================ 1. BIOS R01.01.0020 will include a security revision upgraded. BIOS downgrade is not allowed from the OS and can only be performed on uEFI shell using the BIOS recovery jumper method. 2. BIOS R01.01.0018 will include a security revision upgraded. BIOS downgrade is not allowed from the OS and can only be performed on uEFI shell using the BIOS recovery jumper method. 3. BIOS R01.01.0009 will enable UEFI Secure Boot and include below limitations: - Please read "BIOS UEFI SECURE BOOT IMPACT AND MITIGATION METHOD" section in this BIOS release notes - All customer settings saved in BIOS NVRAM will be lost after new BIOS upgrade - BIOS downgrade is not allowed if user has enabled BIOS secure boot. All customer setting will be lost also if downgrade to previous BIOS release - Backup BIOS region is also required to be updated to prevent recovery failure please use release package to update BIOS - There is downgrade hang risk if you don't follow above rules - Further BIOS release will not suffer from these side effects as the NVRAM region is formatted as authenticated variable storage 4. System will hang 0xbf after downgrading BIOS from D0055(E5-2600V4 code tree) to R0011/R0009(E5-2600V3 code tree) randomly - Set SUT to recovery mode to power on, then set it back to normal boot to see whether it is recovered 5. The iFlash32 utility parameter of 'UpdateNvram' is not supported under Normal Mode, however it is only supported under Recovery Mode 6. Design change from D076 for to change default setting from to <10>. Need to press to see the new default string 7. Suggest to press 'F9' to load default if using the 'IOU Non-posted prefetch control' setup options in the first time 8. Use I/O Quick Data(also known as CBDMA) feature to access PCIe MMIO space, such as NTB or PCIe bridge, user may observe I/O performance drop during stress test. The reason is under debug, the workaround is to disable Relax Ordering feature. ================================================================================ BIOS UEFI SECURE BOOT IMPACT AND MITIGATION METHOD ================================================================================= 1. Customer Setting Loss Issue and Mitigation Method When user upgrades BIOS with secure boot feature, the NVRAM will be automatically formatted as authenticated variable physical storage. However, all previous customer settings storage in NVRAM will be lost even if user does not enable UEFI secure boot feature. Users can take the follow recipe to save and restore their settings based on the actual NVRAM usage if they wish to upgrade or downgrade between BIOS with or without secure boot feature. Supposing customer requires to save & restore their specific NVRAM named 'var': Steps: 1. Prepare FAT partition USB key (or HDD). 2. Boot to EFI shell. 3. Check the file system mapping (e.g. fs0:) of the USB key with 'map -r' command. 4. Use 'dmpstore var -s fs0:\var.bin' to save the variable to the physical file. 5. Perform BIOS update and reboot system. 6. Boot to EFI shell. 7. Use 'dmpstore var -l fs0:\var.bin' to restore the variable. 8. Reboot the system if the customer setting requires reboot to take effect. Notes: 1. Immediate reboot after BIOS update is mandatory. Or the restore operation will not take effect. 2. Customers can repeat step 4 and step 7 for several times if they need to save & restore multiple NVRAM variables. 3. Most of BIOS customer settings by SysCfg can also be restored in this way. Customers can follow previous step1~8 by substituting 'Setup' for 'var' in the sample. 4. For BIOS downgrade case, step7 cannot be used to restore authenticate variables (e.g. PK, KEK, DB, DBX) to non-authenticated NVRAM storage 2. Recovery Mode Failure There is known bug that it cannot POST successfully with authenticated NVRAM storage. This will cause platform recovery failure and permanent deny of service (PDOS) if the primary BIOS region gets corrupted for some reason. It is required to update backup BIOS region when upgrade BIOS capsule with secure boot feature. Notes: For downgrade case, user is not required to update backup BIOS region as new BIOS with secure boot feature can handle NVRAM with old storage format: it will format it to new authenticated variable storage automatically. However, care must be taken when downgrading BIOS in recovery mode: After flashing BIOS without secure boot feature, user should restore recovery HW jumper immediately before platform reset.If platforms reset occurs before restoring recovery HW jumper, the backup BIOS will once again format NVRAM to new storage format, which will cause newly flashed BIOS (without secure boot feature) POST failure after user restores recovery HW jumper. ================================================================================ BIOS 01.01.0020 ================================================================================ CCB 480: To support OEM activation feature in ITK on Grantley EPSD 100255536 : Boot order in UEFI mode doesn’t change to default after saving changes and resetting system Update ucode 00000039 for E5-2600V3, 0b00001f for E5-2600V4 Update ME to 03.01.03.043 CCB 466: To support early VGA video display on Grantley EPSD 100035007 The screen which is provided for user to confirm TPM2 clear operation. Fix chipsec security Test failed in SMI 0x26, 0x28 and 0xef(BIOS Security enhancement for SMM communication buffer) EPSD 100034250 - [E5-2600V4] Slot ID shown in type9 is different from PciSlotTest.efi shown CCB488: Provide an option to enable/disable SSC in BIOS Setup Menu Update RC to 3.9.0 EPSD 100035506 : [E5-2600V4] SMBIOS Type 9 structures are wrong on WCP with some riser cards configurations EPSD 100035920: System will hang on diagnostic screen when press F2/F6 button continuous under MFG mode EPSD 100255932: Fix remote terminal show corrupt BIOS Setup screen when Console Redirection Baud Rate is 9.6k/19.2k/38.4k/57.6k issue ================================================================================ ME 03.01.03.043 ================================================================================ Flash from Grantley FW to Grantley-R FW could cause SPS reset. System unexpected shutdown with SPS FW exception error. ME FW changes P state value when no policy is active imapcting performance. C8h command power readings for CPU domain are invalid. =============================================================================== KNOWN ISSUES/WORKAROUNDS/REQUIREMENTS =============================================================================== - This BMC FW update package is to be used only on PCSD server baseboards and does NOT support customer reference boards (CRB) or silicon reference platforms (SRP). Contact your Intel Representatives to determine where to download the BMC FW for these products. - The BMC FW image file in this package is to be used only with the provided FWPIAUPD update utility. Using the FW image file with a SPI flash device programmer will result in a non-functional system. - Some open source ipmi utilities may automatically retry multiple times during access BMC using bad password and supporting IPMI specification 1.5 in Linux OS. CCB310 will log more bad password login SEL. =============================================================================== BMC 01.48.10351 =============================================================================== -EPSD100256480: The fault LED of NvME SSD keep blinking on S2600TP 24HDD system after AC cycle -EPSD100256247: S2600WT system (LWT2224YXXXX221, LWT2224YXXXX129 ) will hang on post after AC cycle with BIOS R16 -EPSD100255719: APPSOL-31180: Web Server Vulnerable to Redirection Page Cross-Site Scripting Attacks -EPSD100035907: The HDD fault LED no light and no rebuild event be logged when plug out the HDD from HSBP(G97158-371) and plug back the HDD to rebuild RAID. -EPSD100256365: [S2600WT]The NVMe HDD can not be detected in EWS web sensor reading interface when install the NVME HDD in the 2nd HSBP's NVMe slot. -EPSD100256457: In Redhat grub edit mode Backspace and cursor move operations can't be consistent between local Screen and remote KVM session's Screen -EPSD100035838: Can not display Simplified Chinese content after EWS was login when language was change to simplified Chinese. -EPSD100254723: S2600KP BMC FW Health reports HSBP Temp has failed -none: Fix generic overflow attack on port 5120 and 5123 for cdserver and fdserver -EPSD100255012: [S2600WT] - Riser2 Temp lower issue with A2UL8RISER2 -EPSD100255833: Linux Kernel vulnerability – Dirty COW attack -EPSD100254817: The HSBP's FRU can't be detected if install 4 HSBP in WCP system. (Long term solution) -EPSD100035118: HDD Fault LED didn't amber blinking at 1HZ frequence during HDD rebuilding -EPSD100033884: The HDD fault LED no light and no rebuild event be logged when plug out the HDD from HSBP(G94339-371) and plug back the HDD to rebuild RAID. -none: Upgrade openssh to 7.3 -EPSD100035162: LCD shown frusdr version is 1.3a, not 1.13a with BIOS setup. -EPSD100255280: BMC Debug Log does not dump IIO configuration in case of ERR2 -EPSD100255284: BMC Debug Log generation code reads wrong bus to get GFERRST value on socket 1 -EPSD100034909: It shows the HSBP FW update status as "00 01" by executing the "cmdtool 20 c0 38" command in power off status -none: Increase EWS stability after Nessus/Qualys scan -none: Update openssl to 1.0.2j ============================================================================= SYSTEM HARDWARE & SOFTWARE REQUIREMENTS/REVISIONS ============================================================================= - BMC firmware rev 1.41.9579(or later) MUST be preinstalled prior to installing this FRU/SDR package. - BIOS R01.01.0015 or later - MB Ver 03.01.03.021 ================================================================================ FRUSDR 1.14 ================================================================================ - (New) KNP FRUSDR String Error - Processing FRU file name is not correct - EPSD100029551 - The "successfully Completed" message will occur after FRUSDR package for other platform is update - EPSD100029318 - Fan duty issue - Add S2600KPR.fru file for BDW CPU and probe this fru - Update frusdr.efi and ipmi.efi utility 13.1 build 8 - Fixed master.cfg (Processing FRU file name is not correct) - Add DISABLE_NVME_FUNCTIONS record for Auto Detect in the master.cfg file - Add FSC Record Type = 1Dh (Backplane NVMe capabilities) records - Add S2600KPFR.fru file - Change SDR for NIC related tracker(EPSD100250298:Disable onboard NIC from BIOS of KNP/TLP, all system fan run at high speed) - Update master.cfg for KPFR.fru file - Add the Tag of "Others" to "NIC LAN Temp" SDR ============================================================================= LEGAL INFORMATION ============================================================================= Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any time, without notice. Intel is a registered trademark of Intel Corporation. *Other names and brands are the property of their respective owners. Copyright (c) 2017 Intel Corporation. A portion of this firmware is open source code, which falls under the GPL 2.0 license. [END OF RELEASE NOTES]