<?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: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330) in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6880386#M154196</link>
    <description>&lt;P&gt;Refer to my posting above for explanation, these two errors have no impact on the OS or performance of the system&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jul 2016 15:50:01 GMT</pubDate>
    <dc:creator>Jimmy Vance</dc:creator>
    <dc:date>2016-07-20T15:50:01Z</dc:date>
    <item>
      <title>ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6831360#M152673</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;during boot I press F10 to run Hp Intelligent Provisioning, before IP starts the system show this messages:&lt;/P&gt;&lt;P&gt;[Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)&lt;BR /&gt;i8042: Can't read the CTR while initializing i8042&lt;/P&gt;&lt;P&gt;I tried to reset the CMOS and NVRAM with position 6 of the system maintenance switch but error remains.&lt;BR /&gt;I tried to reset the BIOS settings to default values but error remains.&lt;BR /&gt;I tried CTRL+A in BIOS (F9 during boot) but system not show Service Option&lt;/P&gt;&lt;P&gt;I have another identical server and does not give me this problem&lt;/P&gt;&lt;P&gt;The system is updated.&lt;BR /&gt;System ROM P92 v1.50 (07/20/2015)&lt;BR /&gt;Intelligent Provisioning Image: 2.30.75&lt;/P&gt;&lt;P&gt;What can I do?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Feb 2016 09:45:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6831360#M152673</guid>
      <dc:creator>AlessandroSfe</dc:creator>
      <dc:date>2016-02-09T09:45:00Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6831422#M152674</link>
      <description>&lt;P&gt;&amp;gt; [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 38d is 330)&lt;/P&gt;&lt;P&gt;This is caused by the ROM using&amp;nbsp;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&amp;nbsp;message and doesn't have any impact on the system. or the operation of the OS.&lt;/P&gt;&lt;P&gt;&amp;gt; i8042: Can't read the CTR while initializing i8042&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Feb 2016 13:27:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6831422#M152674</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2016-02-09T13:27:15Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6880351#M154194</link>
      <description>&lt;P&gt;I got same situation except my machine is ML150. &amp;nbsp;I wonder if this is affecting my OS installation as I also see these messages after OS installation failure. &amp;nbsp;Can anyone shed me light to fix it? &amp;nbsp;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.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2016 15:20:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6880351#M154194</guid>
      <dc:creator>JW266</dc:creator>
      <dc:date>2016-07-20T15:20:21Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6880386#M154196</link>
      <description>&lt;P&gt;Refer to my posting above for explanation, these two errors have no impact on the OS or performance of the system&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2016 15:50:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6880386#M154196</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2016-07-20T15:50:01Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6880392#M154198</link>
      <description>&lt;P&gt;Thank you for clarification. &amp;nbsp;I will create a new for OS installation issue.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2016 15:56:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/6880392#M154198</guid>
      <dc:creator>JW266</dc:creator>
      <dc:date>2016-07-20T15:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7005770#M162494</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Network and Bios error" style="width: 1040px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/103323i2C9F99E1968ED984/image-size/large?v=v2&amp;amp;px=2000" role="button" title="HP_DL360P_Gen9_NetworkAndBIOS_error.jpeg" alt="Network and Bios error" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Network and Bios error&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2018 08:39:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7005770#M162494</guid>
      <dc:creator>DarshanS</dc:creator>
      <dc:date>2018-05-14T08:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7005771#M162495</link>
      <description>&lt;P&gt;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...?&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2018 08:42:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7005771#M162495</guid>
      <dc:creator>DarshanS</dc:creator>
      <dc:date>2018-05-14T08:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7005802#M162506</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1924699"&gt;@DarshanS&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;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...?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The HW-PMU, i8042,, and power cap messages are just informational.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2018 11:57:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7005802#M162506</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2018-05-14T11:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7072368#M168880</link>
      <description>&lt;P&gt;Hello i also encountered a similar problem and hope to get your help&lt;/P&gt;&lt;P&gt;dl380 gen8&lt;/P&gt;&lt;P&gt;the bios has corrupted hw-pmu resources (msr 38d is 330)&lt;/P&gt;&lt;P&gt;ERST:Failed to get Error log Address Range&lt;/P&gt;&lt;P&gt;sd 3:0:0:0 {sdc} no caching mode page found&lt;/P&gt;&lt;P&gt;sd 3:0:0:0 {sdc}assuming drive cache write through&amp;nbsp;&lt;/P&gt;&lt;P&gt;systemd-readahead[2009]:Failed to open pack file :Read -only file system&lt;/P&gt;&lt;P&gt;many thanks&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2019 09:16:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7072368#M168880</guid>
      <dc:creator>yangxiaodong</dc:creator>
      <dc:date>2019-12-10T09:16:51Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7072429#M168886</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2001158"&gt;@yangxiaodong&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Hello i also encountered a similar problem and hope to get your help&lt;/P&gt;&lt;P&gt;dl380 gen8&lt;/P&gt;&lt;P&gt;the bios has corrupted hw-pmu resources (msr 38d is 330)&lt;/P&gt;&lt;P&gt;ERST:Failed to get Error log Address Range&lt;/P&gt;&lt;P&gt;sd 3:0:0:0 {sdc} no caching mode page found&lt;/P&gt;&lt;P&gt;sd 3:0:0:0 {sdc}assuming drive cache write through&amp;nbsp;&lt;/P&gt;&lt;P&gt;systemd-readahead[2009]:Failed to open pack file :Read -only file system&lt;/P&gt;&lt;P&gt;many thanks&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I replied to your other thread and pointed you back to this one &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2019 13:02:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7072429#M168886</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2019-12-10T13:02:37Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7100688#M172217</link>
      <description>&lt;P&gt;Beg to differ. Fails the install - install does not progress past the error.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 06:35:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7100688#M172217</guid>
      <dc:creator>agood</dc:creator>
      <dc:date>2020-09-09T06:35:40Z</dc:date>
    </item>
    <item>
      <title>Re: ML350 G9 BIOS has corrupted hw-PMU resources (MSR 38d is 330)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7100858#M172232</link>
      <description>&lt;P&gt;I think u should try creating a new thread instead...no response for old ones..&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2020 11:09:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml350-g9-bios-has-corrupted-hw-pmu-resources-msr-38d-is-330/m-p/7100858#M172232</guid>
      <dc:creator>techin</dc:creator>
      <dc:date>2020-09-10T11:09:56Z</dc:date>
    </item>
  </channel>
</rss>

