ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

BIOS HAS CORRUPT [hw] PMU RESOURCES....

 
CSG-IT
Member

BIOS HAS CORRUPT [hw] PMU RESOURCES....

This error comes up, booting to a fresh install of

 

Debian/CentOS/Fedora

 

on a DL 380 G5 with latest BIOS and FW.

RESULT: Server doesn't boot, hangs after grub, blank screen, no more details.

 

 

I urgently need a fix or workaround for this problem.

Any suggestions?

Thank you,

 

Oliver

 

 

 

Moved from ProLiant Servers - Netservers to ProLiant Servers (ML,DL,SL)

26 REPLIES 26
Highlighted

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....

1. You may try clearing the server’s NVRAM. To do so, you may perform the following steps:

 

i. Power down the server and remove the access panel.

 

ii. Please refer to item 9 of the System board components diagram, on page 84 of 104 of the server’s maintenance and service guide to identify the system maintenance switch. The guide is locatable at the following link:

 

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00710359/c00710359.pdf

 

iii. Locate individual switch S6, and set it from the default position of ‘Off’ to ‘On’. Replace the access panel and power it on. Wait till the message indicates that the server has been reset. Then power off the server, remove the power cable from the wall jack, and remove the access panel, revert switch S6 to position back to ‘Off’ and then power it on.

 

After clearing NVRAM, please re-enter the serial number in the server's RBSU. You may perform the following steps:

 

i. During the server startup sequence, press the F9 key to access RBSU.

 

ii. Select the System Options menu.

 

iii. Select Serial Number. The following warning is displayed:  

 

                                WARNING! WARNING! WARNING! The serial number is loaded into the system during the manufacturing process and should NOT be modified. This option should only be used by qualified service personnel. This value should always match the serial number sticker located on the chassis.  

 

iv. Press the Enter key to clear the warning.

 

v. Enter the serial number and press the Enter key.

 

vi. Select Product ID.

 

vii. Enter the product ID and press the Enter key.

 

viii. Press the Esc key to close the menu.

 

ix. Press the Esc key to exit RBSU.

 

x. Press the F10 key to confirm exiting RBSU. The server will automatically reboot.

 

2. If the issue is not resolved, then activate redundant ROM. To do so, locate the system maintenance switch as listed above and set switches S1, S5, S6 to “On” position from the default “OFF” position and power it on. Once the message appears, then proceed to power off the server and reverse the switch settings.

 

3. If the issue is persists, then re-flash the server’s BIOS. To do so, you may perform the following steps:

                i. Download the ROMPaq from the following link and follow instructions seen under tab ‘Installation instructions’ to create a bootable USB ROMPaq flashkey:

 

                x86:

               

                                http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=5351&prodSeriesId=1121516&swItem=MTX-970dc8e46003491394f328f1ca&prodNameId=3288134&swEnvOID=4033&swLang=8&taskId=135&mode=4&idx=1

 

 

                x64:

 

                http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=5351&prodSeriesId=1121516&swItem=MTX-970dc8e46003491394f328f1ca&prodNameId=3288134&swEnvOID=4032&swLang=8&taskId=135&mode=4&idx=1

 

 

                ii. Once the bootable USB ROMPaq flash key  is created, connect it to the server and power cycle it so that the server boots from  the USB key. If there is a message that the BIOS is already updated and option to re-flash it, then re-flash it again.

 

4. If the issue is still not resolved, then check if there are any POST error messages and update it.

 

 

Regards,

 

Vijayasarathy

I work for HPE
Views expressed herein are my personal opinion and is not the views of HPE

Accept or Kudo

CSG-IT
Member

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....

Hi Vijayasarathy,

I am sorry but none of your given options works for me. Any other suggestions?
Here is (maybe) a more specific error message: 
After this "BIOS has corrupt..", the 2nd line reads
"ERST: Failed to get Error-Log Adress range..."

 

Thank you!

Jimmy Vance
HPE Pro

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....

 

 

"the BIOS has corrupted hw-PMU resources" gets displayed as the OS is trying to use a performance counter the BIOS is using.  You can either ignore the message, or turn off performance monitoring in the BIOS as shown in this advisory:

 http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c03265132

 

Currently ProLiant BIOS does not support the ACPI ERST feature and can be safely ignored

 

No support by private messages. Please ask the forum! Accept or KudoI work for HPE
CSG-IT
Member

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....

Hi Jimmy,

 

thanks for your reply.

 

Ignoring this message is not an option, because the server doesn't boot.

The link above is for G7 servers, I do own G5s only.

(Pressing CTRL+A in RBSU does nothing  ;) )

 

Regards

valor88
Occasional Visitor

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....

Hi, could I also confirm that regarding the ERST Failed to get Error Log message also applies to G7 proliant servers?

 

According to the this doc,

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=5268290&prodTypeId=15351&prodSeriesId=5268290&objectID=c03731635

 

it affects only g8 servers?

Jimmy Vance
HPE Pro

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....


@CSG-IT wrote:

Ignoring this message is not an option, because the server doesn't boot.

The link above is for G7 servers, I do own G5s only.

(Pressing CTRL+A in RBSU does nothing  ;) )

 

Both of these messages are warnings and will not stop a system from booting. I had to go back and check, G5 doesn't have the CTRL+A feature.

No support by private messages. Please ask the forum! Accept or KudoI work for HPE
Jimmy Vance
HPE Pro

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....

One thing you might try is edit the boot line and add nomodeset

 

No support by private messages. Please ask the forum! Accept or KudoI work for HPE
Jimmy Vance
HPE Pro

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....


valor88 wrote:

Hi, could I also confirm that regarding the ERST Failed to get Error Log message also applies to G7 proliant servers?

 

According to the this doc,

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=5268290&prodTypeId=15351&prodSeriesId=5268290&objectID=c03731635

 

it affects only g8 servers?



The ERST message was found when testing Gen 8 systems. Since the Gen 8 system ROM doesn't support this feature, I think I can safely say the G7 system ROM doesn't either.  I dont recall when the ERST option was added to the kernel, but I don't think it was there when the G7 was certified.

 

As I've stated, the message is informative, it doesn't effect system performance

No support by private messages. Please ask the forum! Accept or KudoI work for HPE
valor88
Occasional Visitor

Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....

I currently have another same server which is running on linux 6.2. However it doesn't encounter the BIOS error. The current server which encounters the error is on 6.3. 

 

Any idea why this is the case?