<?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: DL580 G3 illegal opcode in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/4087038#M70760</link>
    <description>i've unrepresented the SAN drives for this server but nothing changed.&lt;BR /&gt;I then tried applying the smart array 6i firmware update thinking that it could be an array controller issue, so i updated to 2.8 but again that didn't help.&lt;BR /&gt;The hardware left on the server now is the same that existed prior to OS installation.&lt;BR /&gt;what's even more surprising is that i reinstalled but this time without deleting the RAID and the OS booted just fine.&lt;BR /&gt;Frankly, i don't know where the problem is or how to look for it, i'm just assuming it's a BIOS problem because i have seen some hp docs that recommend updating the server's BIOS to prevent such a problem, in fact it's the only place i ever seen a reference to this.&lt;BR /&gt;simply,still can't figure it out!</description>
    <pubDate>Wed, 17 Oct 2007 09:12:24 GMT</pubDate>
    <dc:creator>kc_kazan</dc:creator>
    <dc:date>2007-10-17T09:12:24Z</dc:date>
    <item>
      <title>DL580 G3 illegal opcode</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/4087037#M70759</link>
      <description>&lt;!--!*#--&gt;we have recently bought a new line of servers among them is a  DL580 G3 P38 server it has 4 AMD64 processors and 18 GB of RAM.we installed RHEL 4 U4 x86_64 linux on it, the installation went ok , error clean, but when reinstalling after a crash the server hangs at a red screen with an illegal opcode error.&lt;BR /&gt;we contacted hp support and they advised to upgrade the servers' BIOS - which was already up to date in fact with the latest version 2006.08.08. &lt;BR /&gt;i don't know if this is relevant to mention, i read it somewhere, but the server had SAN drives prior to the crash.&lt;BR /&gt;but the server kept crashing with the following&lt;BR /&gt;&lt;BR /&gt;illegal opcode&lt;BR /&gt;EAX=00007CFE            EBX=00007C00            ECX=00000007            EDX=00000180&lt;BR /&gt;EBP=0000FBFA            ESI=000007BE            EDI=00000800&lt;BR /&gt;DS=0000                 ES=0000                 FS=0000                 GS=0004&lt;BR /&gt;CS:EIP=0000:0000835A            SS:ESP=1000:0000B000&lt;BR /&gt;EFLAGS=0000213&lt;BR /&gt;&lt;BR /&gt;i've been fighting with this for over 3 days so any help is really appreciated&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Oct 2007 11:00:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/4087037#M70759</guid>
      <dc:creator>kc_kazan</dc:creator>
      <dc:date>2007-10-16T11:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: DL580 G3 illegal opcode</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/4087038#M70760</link>
      <description>i've unrepresented the SAN drives for this server but nothing changed.&lt;BR /&gt;I then tried applying the smart array 6i firmware update thinking that it could be an array controller issue, so i updated to 2.8 but again that didn't help.&lt;BR /&gt;The hardware left on the server now is the same that existed prior to OS installation.&lt;BR /&gt;what's even more surprising is that i reinstalled but this time without deleting the RAID and the OS booted just fine.&lt;BR /&gt;Frankly, i don't know where the problem is or how to look for it, i'm just assuming it's a BIOS problem because i have seen some hp docs that recommend updating the server's BIOS to prevent such a problem, in fact it's the only place i ever seen a reference to this.&lt;BR /&gt;simply,still can't figure it out!</description>
      <pubDate>Wed, 17 Oct 2007 09:12:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/4087038#M70760</guid>
      <dc:creator>kc_kazan</dc:creator>
      <dc:date>2007-10-17T09:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: DL580 G3 illegal opcode</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/6132751#M137287</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I having also an illegal opcode error. I have an HP DL 580 G5 server running windows server 2008 std. There was a power outage and the server was powered off. Since that i'm getting that op code error with red screen.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please note that before installing windows, the server had Solaris installed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After applying firmware, i was able to boot windows &amp;nbsp;but after a reboot i again got the red screen and op code error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So whenever i reboot, i have to put the firmware cd, Although nothing is applied (as the firmware is already updated), the system is booted successfully.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What can be the problem?&lt;/P&gt;&lt;P&gt;Is it the mbr has been corrupted?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your precious help.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kind Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Atish G&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2013 20:41:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/6132751#M137287</guid>
      <dc:creator>atishG</dc:creator>
      <dc:date>2013-07-11T20:41:44Z</dc:date>
    </item>
    <item>
      <title>Re: DL580 G3 illegal opcode</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/6132795#M137289</link>
      <description>&lt;P&gt;Yes, you can get the Red illegal opcode screen when the MBR is corrupted.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2013 21:44:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/dl580-g3-illegal-opcode/m-p/6132795#M137289</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2013-07-11T21:44:27Z</dc:date>
    </item>
  </channel>
</rss>

