Server Products
Data Center Products including boards, integrated systems, Intel® Xeon® Processors, RAID Storage; and Intel® Xeon® Processors
Announcements
The Intel sign-in experience is changing in February to support enhanced security controls. If you sign in, click here for more information.
4481 Discussions

HP DL360 G8 (Xeon(R) CPU E5-2690 v2) and firmware updates for Linux causing boot issues.

jcdick11
Beginner
863 Views

I am running XCP-NG on three HP DL360 G8 servers, with E5-2690 v2 Xeon CPUs.

 

The intel linux-firmware packages 20190314-1 and 20190314-2 were recently pushed, and now booting the servers is problematic due to CPU panics and "failed to bring up CPU X (error code -5)" messages, with X being a different CPU each time it loops.  I've managed to get two of the three servers in the cluster to eventually get past it and boot just by letting them reboot a few times, but the third I've been unable to get booted.

 

Has anyone else experienced anything similar?

Labels (1)
0 Kudos
9 Replies
JoseH_Intel
Moderator
853 Views

Hello jcdick11,


Thank you for joining the Intel community.


Could you please share the link for the Intel linux-firmware packages 20190314-1 and 20190314-2. Usually you want to apply the updates provided by the system OEM (HP) first.

Besides that, please try the Intel® Processor Diagnostic Tool and let us know the results.


Regards


Jose A.

Intel Customer Support Technician

For firmware updates and troubleshooting tips, visit:

https://intel.com/support/serverbios


jcdick11
Beginner
847 Views

The 20190314-1 package has been moved to the base repository here:

 

https://updates.xcp-ng.org/8/8.2/base/x86_64/Packages/

 

And the 20190314-2 package is in the updates repo here:

 

https://updates.xcp-ng.org/8/8.2/updates/x86_64/Packages/

 

I can't use the Processor Diagnostic Tool, as this is a Linux-based system, and so a Windows-only tool can't be run.

JoseH_Intel
Moderator
836 Views

Hello jcdick11,


Is this repository an Intel officially managed repository?


Regards


Jose A.

Intel Customer Support Technician

For firmware updates and troubleshooting tips, visit:

https://intel.com/support/serverbios


jcdick11
Beginner
830 Views

No, its the XCP-NG repository for the Xen-based hypervisor.

JoseH_Intel
Moderator
827 Views

Hello jcdick11,


In this case the best option is to contact XCP-NG or HP since they release their own firmware for their systems. Intel only release firmware updates for the Intel server boards.


Regards


Jose A.

Intel Customer Support Technician

For firmware updates and troubleshooting tips, visit:

https://intel.com/support/serverbios


jcdick11
Beginner
823 Views

I realize I said "firmware" in the title, as that is what the packages are called.  But actually, they are the Intel microcode updates that usually accompany Linux kernel releases.

 

I'm just wondering if anyone else has had the Linux Intel microcode updates result in CPU panics and "failure to bring up CPU x (error -5)"
 issues.

JoseH_Intel
Moderator
819 Views

Hello jcdick11,


Let me try to do some research on this. I will get back to you soon.


Regards


Jose A.

Intel Customer Support Technician

For firmware updates and troubleshooting tips, visit:

https://intel.com/support/serverbios


JoseH_Intel
Moderator
811 Views

Hello jcdick11,


Due to this product being discontinued, Intel Customer Service no longer supports inquiries for it, but perhaps fellow community members have the knowledge to jump in and help. You may also find the Discontinued Products website helpful to address your request. Thank you for understanding.


Regards


Jose A.

Intel Customer Support Technician

For firmware updates and troubleshooting tips, visit:

https://intel.com/support/serverbios


jcdick11
Beginner
744 Views

I think I've figured it out, and its strange, considering the platform.  These are DL360s with fully licensed iLOs.  If I do everything via the remote console in the iLO, I get the error "bringing up CPU X (error -5)".  If I go to the machine, and connect a USB keyboard, then go back to my workstation and do the reboot, the machines come up fine.  As long as a physical keyboard is connected at reboot, the CPU error does not present itself.

Reply