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

ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

SOLVED
Go to solution

ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

Hi,

during boot I press F10 to run Hp Intelligent Provisioning, before IP starts the system show this messages:

[Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)
i8042: Can't read the CTR while initializing i8042

I tried to reset the CMOS and NVRAM with position 6 of the system maintenance switch but error remains.
I tried to reset the BIOS settings to default values but error remains.
I tried CTRL+A in BIOS (F9 during boot) but system not show Service Option

I have another identical server and does not give me this problem

The system is updated.
System ROM P92 v1.50 (07/20/2015)
Intelligent Provisioning Image: 2.30.75

What can I do?

Thanks in advance



7 REPLIES
Jimmy Vance
HPE Pro
Solution

Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

> [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)

This is caused by the ROM using performance counters Linux also wants to use. Linus doesn't like the hardware using any of these counters so he marks it as a bug. It's just a message and doesn't have any impact on the system. or the operation of the OS.

> i8042: Can't read the CTR while initializing i8042

This message is from the kernel as it tries to load a driver for hardware that doesn't exist. The i8042 is for the PS2 keyboard/mouse which Gen9 doesn' have. Again an erroneous message

 




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
JW266
Occasional Advisor

Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

I got same situation except my machine is ML150.  I wonder if this is affecting my OS installation as I also see these messages after OS installation failure.  Can anyone shed me light to fix it?  I had several attemps to install OS and always ends up with "Windows installation cannot continue because a required driver could not be installed" then the "..corrupted..." and "..can't read ctr..." messages came up.

Jimmy Vance
HPE Pro

Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

Refer to my posting above for explanation, these two errors have no impact on the OS or performance of the system




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!   
JW266
Occasional Advisor

Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

Thank you for clarification.  I will create a new for OS installation issue.

DarshanS
Occasional Visitor

Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

HP_DL360P_Gen9_NetworkAndBIOS_error.jpegNetwork and Bios error

DarshanS
Occasional Visitor

Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)

As i went through the above comments, i understand the BIOS error may be a warning but doesn't cause any issue. However, my network is completely down (i can see led blinks at the both ends of the CAT5). Only loopback address is pingable despite IP address been assigned to other eth ports. Is it related issue...? On the BIOS, PCIE are enabled. Any leads...?

Jimmy Vance
HPE Pro

Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)


@DarshanS wrote:

As i went through the above comments, i understand the BIOS error may be a warning but doesn't cause any issue. However, my network is completely down (i can see led blinks at the both ends of the CAT5). Only loopback address is pingable despite IP address been assigned to other eth ports. Is it related issue...? On the BIOS, PCIE are enabled. Any leads...?


The HW-PMU, i8042,, and power cap messages are just informational.

The system is not booting so the network drivers are not loaded. enter the root password and run journalctl -xb to see the logs which may show what the issue is.




__________________________________________________
No support by private messages. Please ask the forum!      I work for HPE

If you feel this was helpful please click the KUDOS! thumb below!