Operational Defect Database
BugZero found this defect 1029 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Hewlett Packard Enterprise | a00060570en_us
Advisory: (Revision) ProLiant Gen9 Series Servers - Unexpected Reset or Shutdown May Occur on ProLiant Gen9 Servers
Last update date:
2/23/2024
Affected products:
HPE ProLiant BL460c Gen9 Server Blade
HPE ProLiant BL660c Gen9 Server Blade
HPE ProLiant DL120 Gen9 Server
HPE ProLiant DL180 Gen9 Server
HPE ProLiant DL360 Gen9 Server
HPE ProLiant DL380 Gen9 Server
HPE ProLiant DL580 Gen9 Server
HPE ProLiant ML110 Gen9 Server
HPE ProLiant ML150 Gen9 Server
HPE ProLiant ML350 Gen9 Server
HPE ProLiant WS460c Gen9 Graphics Server Blade
HPE ProLiant XL170r Gen9 Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
Document Version Release Date Details 6 07/26/2021 Added additional impacted processor and impacted platforms 5 05/28/2020 Updated Resolution to make clarification of Step 7 4 04/22/2020 Updated Step 7 in Resolution 3 10/15/2019 Added additional information to advisory 2 08/21/2019 Updated Resolution section with additional information 1 11/29/2018 Original document release HPE ProLiant Gen9 servers may experience an unexpected reset or shutdown event described in the scenarios below: Scenario 1: The server experiences an unexpected reboot or shutdown with no Integrated Management Log entries present to indicate that a failure occurred. Scenario 2: The server experiences an unexpected reboot or shutdown, and an error similar to the following MAY appear during Power-On Self-Test (POST) on the next system boot, and in the Integrated Management Log: Option ROM POST Error: 1719-Slot 0 Drive Array - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x12) Action: Install the latest controller firmware. If the problem persists, replace the controller. The important item to note in the error message above is the lockup code 0x12. Other lockup codes do not apply to this advisory. The slot number in the error message may vary. Scenario 3: The server experiences an unexpected reboot or shutdown, and the Integrated Management Log has an entry similar to the one below: Uncorrectable Machine Check Exception (Board 0, Processor 2, APIC ID 0x00000040, Bank 0x00000004, Status 0xBA000000'73000402, Address 0x00000000'00000000, Misc 0x00000000'00000000) The following items in the UMCE entry above must be matched: -Bank 0x00000004 -Status 0xBA000000'73000402' Other Uncorrectable Machine Check Exception entries that occur at the same time MAY be present in the Integrated Management Log. The following error MAY or MAY NOT be present during POST or in the Integrated Management Log: Option ROM POST Error: 1719-Slot 0 Drive Array - A controller failure event occurred prior to this power-up. (Previous lock up code = 0x12) Action: Install the latest controller firmware. If the problem persists, replace the controller. The important item to note in the error message above is the lockup code 0x12. Other lockup codes do not apply to this advisory. The slot number in the error message may vary.
Scope
Any of the ProLiant servers listed in the "Products" section and that are configured with either of the following processor models: - E5-2600 v4 Series Intel Processor - E5-4600 v4 Series Intel Processor - E7-4800 v4 Series Intel Processor
Resolution
Important: Although error messages may be present indicating a Smart Array controller error, the Smart Array controller is not defective. A previous version of this advisory indicated System ROM 2.64 or later has a microcode patch to address this problem. HPE is modifying our guidance to update affected servers to System ROM version 2.74, which includes the Intel microcode to address this issue and should be applied to any servers experiencing this failure. Intel has documented this issue as errata BDF103 in the Intel Xeon E5-2600 v4 Processor Product Family Specification Update Revision 20.0. The System ROM can be downloaded from the HPE Support Center at https://support.hpe.com/hpesc/public/home In the search field, enter the name of the server platform. In the dropdown list of search results, select "Drivers and Software" for the item in the dropdown list that matches the search term. On the Drivers and Software page, use the filter options on the left to more quickly find the desired System ROM component. Entitlement is required to download System ROM updates. Should this problem recur even after system ROM version 2.64 and later is applied, follow the steps below. 1. Update System ROM to version 2.74 if this has not already been done. 2. Reboot the server. 3. During POST, press F9 to boot into the System Utilities menu. 4. In the System Utilities menu, navigate to "System Configuration --> BIOS/Platform Configuration (RBSU) --> Advanced Options --> Uncore Frequency Limiting". 5. Select "Enabled" and press "Enter". 6. Press F10 to save the change, then press "Y" when prompted to accept the change. 7.Press the "ESC" key repeatedly to navigate back to the top menu level. There are two options: Exit and Resume System Boot, or "reboot the system." Select "Reboot the System" and exit System Utilities, then press "Enter" when prompted to exit and reboot the server. 8. Allow the server to reboot and boot the OS. If further assistance is needed, contact HPE Customer Support and refer to this number: CFI 21295 . Click on the following URL to locate the HPE Customer Support phone number in your country: https://h20195.www2.hpe.com/v2/Getdocument.aspx?docname=A00039121ENW .
