<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: BIOS HAS CORRUPT [hw] PMU RESOURCES.... in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920627#M155666</link>
    <description>&lt;P&gt;No i didnt, but i will try, I thought that the first message is the main trouble )&lt;/P&gt;</description>
    <pubDate>Thu, 24 Nov 2016 12:50:11 GMT</pubDate>
    <dc:creator>Haman_Oleh</dc:creator>
    <dc:date>2016-11-24T12:50:11Z</dc:date>
    <item>
      <title>BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6006799#M135536</link>
      <description>&lt;P&gt;This error comes up, booting to a fresh install of&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Debian/CentOS/Fedora&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;on a DL 380 G5 with latest BIOS and FW.&lt;BR /&gt;&lt;BR /&gt;RESULT: &lt;FONT color="#FF0000"&gt;Server doesn't boot, hangs after grub, blank screen, no more details.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#FF0000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000"&gt;I urgently need a fix or workaround for this problem.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Any suggestions?&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Oliver&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Moved from ProLiant Servers - Netservers to ProLiant Servers (ML,DL,SL)&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2013 02:47:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6006799#M135536</guid>
      <dc:creator>CSG-IT</dc:creator>
      <dc:date>2013-03-26T02:47:14Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6007357#M135537</link>
      <description>&lt;P&gt;&lt;FONT size="3"&gt;1. You may try clearing the server’s NVRAM. To do so, you may perform the following steps:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;i. Power down the server and remove the access panel.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;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:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c00710359" target="_blank" rel="noopener"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c00710359&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;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.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;After clearing NVRAM, please re-enter the serial number in the server's RBSU. You may perform the following steps:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;i. During the server startup sequence, press the F9 key to access RBSU. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;ii. Select the System Options menu. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;iii. Select Serial Number. The following warning is displayed:&amp;nbsp;&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 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.&amp;nbsp;&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;iv. Press the Enter key to clear the warning. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;v. Enter the serial number and press the Enter key. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;vi. Select Product ID. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;vii. Enter the product ID and press the Enter key. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;viii. Press the Esc key to close the menu. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;ix. Press the Esc key to exit RBSU. &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;x. Press the F10 key to confirm exiting RBSU. The server will automatically reboot.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;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.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;3. If the issue is persists, then re-flash the server’s BIOS. To do so, you may perform the following steps:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; i. Download the ROMPaq from the following link and follow instructions seen under tab ‘Installation instructions’ to create a bootable USB ROMPaq flashkey:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; x86:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_57720d956df94dfcbaa0e28256&amp;amp;swEnvOid=4168" target="_blank" rel="noopener"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_57720d956df94dfcbaa0e28256&amp;amp;swEnvOid=4168&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; x64:&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_57720d956df94dfcbaa0e28256&amp;amp;swEnvOid=4168" target="_blank" rel="noopener"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_57720d956df94dfcbaa0e28256&amp;amp;swEnvOid=4168&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://techlibrary.hpe.com/docs/iss/proliant-gen10-uefi/s_enbable_intel_perf_montoring.html" target="_blank" rel="noopener"&gt;&lt;FONT size="3"&gt;https://techlibrary.hpe.com/docs/iss/proliant-gen10-uefi/s_enbable_intel_perf_montoring.html&lt;/FONT&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ii. Once the bootable USB ROMPaq flash key &amp;nbsp;is created, connect it to the server and power cycle it so that the server boots from&amp;nbsp; 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.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;4. If the issue is still not resolved, then check if there are any POST error messages and update it.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;Regards,&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;Vijayasarathy&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="3"&gt;&amp;nbsp;&lt;U&gt;&lt;STRONG&gt;Moderator Note:&lt;/STRONG&gt;&lt;/U&gt;&lt;SPAN&gt;&amp;nbsp;[Updated with new links]&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Oct 2020 06:53:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6007357#M135537</guid>
      <dc:creator>TVVJ</dc:creator>
      <dc:date>2020-10-29T06:53:43Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6010849#M135551</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Vijayasarathy,&lt;BR /&gt;&lt;BR /&gt;I am sorry but none of your given options works for me. Any other suggestions?&lt;BR /&gt;Here is (maybe) a more specific error message:&amp;nbsp;&lt;BR /&gt;After this "BIOS has corrupt..", the 2nd line reads&lt;BR /&gt;"ERST: Failed to get Error-Log Adress range..."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2013 06:58:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6010849#M135551</guid>
      <dc:creator>CSG-IT</dc:creator>
      <dc:date>2013-03-27T06:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6011415#M135556</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"the BIOS has corrupted hw-PMU resources" gets displayed as the OS is trying to use a performance counter the BIOS is using.&amp;nbsp; You can either ignore the message, or turn off performance monitoring in the BIOS as shown in this advisory:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;A href="http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c03265132" target="_blank"&gt;http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c03265132&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently ProLiant&amp;nbsp;BIOS does not support the&amp;nbsp;ACPI ERST feature and can be safely ignored&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2017 03:30:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6011415#M135556</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2017-07-27T03:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6011551#M135557</link>
      <description>&lt;P&gt;Hi Jimmy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for your reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ignoring this message is not an option, because the server doesn't boot.&lt;/P&gt;&lt;P&gt;The link above is for G7 servers, I do own G5s only.&lt;/P&gt;&lt;P&gt;(Pressing CTRL+A in RBSU does nothing &amp;nbsp;;) )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2013 16:28:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6011551#M135557</guid>
      <dc:creator>CSG-IT</dc:creator>
      <dc:date>2013-03-27T16:28:08Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6029985#M135835</link>
      <description>&lt;P&gt;Hi, could I also confirm that regarding the ERST Failed to get Error Log message also applies to G7 proliant servers?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;According to the this doc,&lt;/P&gt;
&lt;P&gt;&lt;STRIKE&gt;&lt;A&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=mmr_sf-EN_US000020344&lt;/A&gt;&lt;/STRIKE&gt;&lt;/P&gt;
&lt;P&gt;it affects only g8 servers?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&lt;U&gt;&lt;STRONG&gt;[Moderator Note:&lt;/STRONG&gt;&lt;/U&gt;&lt;SPAN&gt;&amp;nbsp;Removed the broken link. Please refer to &lt;A href="https://support.hpe.com/" target="_blank"&gt;https://support.hpe.com/&lt;/A&gt;]&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 14:56:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6029985#M135835</guid>
      <dc:creator>valor88</dc:creator>
      <dc:date>2023-10-04T14:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6030323#M135842</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1399641"&gt;@CSG-IT&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;&lt;FONT size="2"&gt;Ignoring this message is not an option, because the server doesn't boot.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;The link above is for G7 servers, I do own G5s only.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;(Pressing CTRL+A in RBSU does nothing &amp;nbsp;;) )&lt;/FONT&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2013 15:48:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6030323#M135842</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2013-04-15T15:48:01Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6030333#M135843</link>
      <description>&lt;P&gt;One thing you might try is edit the boot line and add nomodeset&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2013 15:57:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6030333#M135843</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2013-04-15T15:57:45Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6030345#M135845</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;FONT size="2"&gt;valor88 wrote:&lt;/FONT&gt;&lt;BR /&gt;
&lt;P&gt;&lt;FONT size="2"&gt;Hi, could I also confirm that regarding the ERST Failed to get Error Log message also applies to G7 proliant servers?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;According to the this doc,&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=c03731635" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=c03731635&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;it affects only g8 servers?&lt;/FONT&gt;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&lt;BR /&gt;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.&amp;nbsp; 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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As I've stated, the message is informative, it doesn't effect system performance&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;[Moderator edit: Updated the valid link.]&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Oct 2023 14:55:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6030345#M135845</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2023-10-04T14:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6031937#M135881</link>
      <description>&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any idea why this is the case?&lt;/P&gt;</description>
      <pubDate>Wed, 17 Apr 2013 01:27:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6031937#M135881</guid>
      <dc:creator>valor88</dc:creator>
      <dc:date>2013-04-17T01:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6732220#M148031</link>
      <description>&lt;P&gt;i am also ubuntu 14.04 lts but it giving me the error of "firmaware biu: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)". What should i do? I am using HP DL120 servers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;any help please?&lt;/P&gt;</description>
      <pubDate>Tue, 14 Apr 2015 07:22:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6732220#M148031</guid>
      <dc:creator>zou15</dc:creator>
      <dc:date>2015-04-14T07:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6734012#M148089</link>
      <description>&lt;P&gt;The answer is in the 4th post of this thread date 03/27//2013&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2015 08:01:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6734012#M148089</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2015-04-18T08:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6742774#M148435</link>
      <description>Unfortunately, the 4th posting does NOT contain the solution to this issue. The original question was regarding a DL380 G5. I am having the same issue. This appears to be universal with newer Linux releases. If anyone has a fix, I'd love to hear it.</description>
      <pubDate>Sat, 09 May 2015 19:08:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6742774#M148435</guid>
      <dc:creator>Hpoley</dc:creator>
      <dc:date>2015-05-09T19:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6742870#M148438</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1622942"&gt;@Hpoley&lt;/a&gt; wrote:&lt;BR /&gt;Unfortunately, the 4th posting does NOT contain the solution to this issue. The original question was regarding a DL380 G5. I am having the same issue. This appears to be universal with newer Linux releases. If anyone has a fix, I'd love to hear it.&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Both the Customer Advisory listed in the 4th post and the Red Hat bugzilla that is referenced from within the advisory list the resolution&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Either ignore the message as it has no impact on the server or OS performance or turn off the performance counters in the BIOS.&lt;/P&gt;</description>
      <pubDate>Sun, 10 May 2015 18:53:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6742870#M148438</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2015-05-10T18:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6784413#M151073</link>
      <description>&lt;P&gt;I am having the same problem after firmware update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The message does not prevent the server from booting,&amp;nbsp;but the local console connection goes "black" when the Linux part of the boot sequence starts. It still boots and can be managed through ILO, but the local console remains unusable.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2015 05:58:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6784413#M151073</guid>
      <dc:creator>Maddas69</dc:creator>
      <dc:date>2015-09-14T05:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6784510#M151079</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1641531"&gt;@Maddas69&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;I am having the same problem after firmware update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The message does not prevent the server from booting,&amp;nbsp;but the local console connection goes "black" when the Linux part of the boot sequence starts. It still boots and can be managed through ILO, but the local console remains unusable.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Not sure what is casuing your issue, but it is not 'BIOS HAS CORRUPT [hw] PMU RESOURCES....'&amp;nbsp; This error is Linux wanting to use a performance counter that the ProLiant BIOS is already using.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What model server are you working with and what ROM firmware did you install?&amp;nbsp; Try adding 'nomodeset' to your boot options&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2015 13:11:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6784510#M151079</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2015-09-14T13:11:45Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920597#M155662</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1062529"&gt;@Jimmy Vance&lt;/a&gt; wrote:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1641531"&gt;@Maddas69&lt;/a&gt; wrote:&lt;BR /&gt;&lt;P&gt;I am having the same problem after firmware update.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The message does not prevent the server from booting,&amp;nbsp;but the local console connection goes "black" when the Linux part of the boot sequence starts. It still boots and can be managed through ILO, but the local console remains unusable.&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Not sure what is casuing your issue, but it is not 'BIOS HAS CORRUPT [hw] PMU RESOURCES....'&amp;nbsp; This error is Linux wanting to use a performance counter that the ProLiant BIOS is already using.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What model server are you working with and what ROM firmware did you install?&amp;nbsp; Try adding 'nomodeset' to your boot options&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I have same problem&amp;nbsp; whith installing ProxMox 4.3 to HP ProLiant D360 G7 , I am alredy Disabled&lt;/P&gt;&lt;PRE&gt;Processor Power Monitoring &lt;/PRE&gt;&lt;P&gt;but that is not solution ( I steel coud not use Remoute Console in ILO3, it show black screen. That is video of booting &lt;A href="http://screencast.com/t/cYvBo6TeVrE" target="_blank"&gt;http://screencast.com/t/cYvBo6TeVrE&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2016 11:19:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920597#M155662</guid>
      <dc:creator>Haman_Oleh</dc:creator>
      <dc:date>2016-11-24T11:19:56Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920607#M155663</link>
      <description>&lt;P&gt;Regarding&lt;/P&gt;
&lt;P&gt;The BIOS has Corrupted hw-PMU Resources (MSR 38d is 330)&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03265132" target="_blank" rel="noopener"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c03265132&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Did you google&lt;/P&gt;
&lt;P&gt;"Error: Driver 'pcspkr' is already registered, aborting"?&lt;/P&gt;
&lt;P&gt;There are some possible solutions.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Oct 2020 06:49:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920607#M155663</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2020-10-29T06:49:18Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920627#M155666</link>
      <description>&lt;P&gt;No i didnt, but i will try, I thought that the first message is the main trouble )&lt;/P&gt;</description>
      <pubDate>Thu, 24 Nov 2016 12:50:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920627#M155666</guid>
      <dc:creator>Haman_Oleh</dc:creator>
      <dc:date>2016-11-24T12:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: BIOS HAS CORRUPT [hw] PMU RESOURCES....</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920930#M155683</link>
      <description>&lt;P&gt;Thank you, after doing /etc/modprobe.d/blacklist: blacklist pcspkr that the error is gone&lt;/P&gt;&lt;P&gt;But now i have black screen in remoute console iLO3 but all ok on monitor screen or i got this error &lt;A href="http://screencast.com/t/lxnCdsb5gE" target="_blank"&gt;http://screencast.com/t/lxnCdsb5gE&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Somebody know why? Sorry if this is offtop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Nov 2016 17:47:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/bios-has-corrupt-hw-pmu-resources/m-p/6920930#M155683</guid>
      <dc:creator>Haman_Oleh</dc:creator>
      <dc:date>2016-11-25T17:47:26Z</dc:date>
    </item>
  </channel>
</rss>

