<?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 HP SPP-2016.10 fails to boot in legacy mode on DL180 Gen9 in HPE ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/hp-spp-2016-10-fails-to-boot-in-legacy-mode-on-dl180-gen9/m-p/6940655#M156454</link>
    <description>&lt;P&gt;Dear Community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're currently experiencing an unusual behavior of some of our DL180 Gen9 machines which were recently ordered from HPE. If the HP SPP (for upgrading the firmware) is booted in legacy-mode (UEFI works fine!) kernel messages are displayed, stating multiple "CPU soft lockups" and the system remains in an unresponsive state.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What could be the reason for the image not booting properly on some machines while others with the same HW-configuration load the image perfectly fine? We've tried this with several servers, all on factory defaults except for the Legacy/UEFI-Boot setting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Help or some hints would be appreciated.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Rene&lt;/P&gt;</description>
    <pubDate>Thu, 16 Feb 2017 07:09:15 GMT</pubDate>
    <dc:creator>DerKito</dc:creator>
    <dc:date>2017-02-16T07:09:15Z</dc:date>
    <item>
      <title>HP SPP-2016.10 fails to boot in legacy mode on DL180 Gen9</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/hp-spp-2016-10-fails-to-boot-in-legacy-mode-on-dl180-gen9/m-p/6940655#M156454</link>
      <description>&lt;P&gt;Dear Community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're currently experiencing an unusual behavior of some of our DL180 Gen9 machines which were recently ordered from HPE. If the HP SPP (for upgrading the firmware) is booted in legacy-mode (UEFI works fine!) kernel messages are displayed, stating multiple "CPU soft lockups" and the system remains in an unresponsive state.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What could be the reason for the image not booting properly on some machines while others with the same HW-configuration load the image perfectly fine? We've tried this with several servers, all on factory defaults except for the Legacy/UEFI-Boot setting.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Help or some hints would be appreciated.&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;Rene&lt;/P&gt;</description>
      <pubDate>Thu, 16 Feb 2017 07:09:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/hp-spp-2016-10-fails-to-boot-in-legacy-mode-on-dl180-gen9/m-p/6940655#M156454</guid>
      <dc:creator>DerKito</dc:creator>
      <dc:date>2017-02-16T07:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: HP SPP-2016.10 fails to boot in legacy mode on DL180 Gen9</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/hp-spp-2016-10-fails-to-boot-in-legacy-mode-on-dl180-gen9/m-p/6987809#M159749</link>
      <description>&lt;P&gt;I've seen the same behaviour on the DL380 G9 servers we have with 2017.07.02 SPP ISO. It's just random.&amp;nbsp; HP support didn't help. Resetting the NVRAM is sort of hit and miss.&amp;nbsp; So I always switch to the UEFI mode before doing the SPP firmware update. I suspect the mini linux kernel the SPP may have some sort of issues when the boot mode is "Legacy BIOS"&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you gotten any update from HP Support or have you concluded a probable cause of the problem?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 08 Nov 2017 04:28:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/hp-spp-2016-10-fails-to-boot-in-legacy-mode-on-dl180-gen9/m-p/6987809#M159749</guid>
      <dc:creator>rccmum1</dc:creator>
      <dc:date>2017-11-08T04:28:40Z</dc:date>
    </item>
  </channel>
</rss>

