xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "dwight at supercomputer.org" <dwight@supercomputer.org>
To: xen-devel@lists.xensource.com
Subject: Re: XCP: Epilog - Crashes on dual Xeon HP ProLiant systems
Date: Mon, 24 May 2010 09:35:37 -0700	[thread overview]
Message-ID: <201005240935.37338.dwight@supercomputer.org> (raw)
In-Reply-To: <201004300932.37495.dwight@supercomputer.org>

On Friday 30 April 2010 09:32:37 am I wrote:
> Is anyone else running the latest XCP on HP ProLiant DL380
> systems? Or a similar dual Xeon 8-core system? I'm seeing
> spontaneous reboots when under a load.
>

I wanted to follow up to the list on this issue, particularly if 
someone else in the future comes across this with the ProLiant 
series.

The bottom line is that it was a firmware issue (actually, at least 
two different components needed a firmware update. Thanks to Pasi 
and Ian for the replies and suggestions. Also, I was able to repeat 
the odd behavior of 64-bit CentOS 5.4 not installing, while the 
32-bit version worked. This also went away after the firmware 
upgrade.

Here are some more details which probably aren't of interest to the 
list, but I'm sending them along in the hopes of sparing someone 
else who comes across this, and does a Google search.

The key test here was running a continual loop of a -j8 kernel build, 
from scratch. One test failed after 14 hours; another after 9 hours. 
memtestx86 and prime95 in torture test mode worked fine.

The bottom line here is that it looks like we got some machines from 
one of the early manufacturing runs back in July. HP has put in a 
lot of effort in fixing a number of issues since then. One needs at 
least the general firmware update ISO from their website, which is 
presently at Version 9. This is necessary, but not sufficient. One 
of our machines would still crash (though 64-bit CentOS would now 
install). The final missing piece was a CPLD update, which HP 
support was kind enough to quickly send me. With that, all machines 
have been running XCP and numerous VMs quite solidly under a heavy 
load.

In spite of these problems, I have to give kudos to HP for the 
support effort that they've put into fixing all of these problems 
over the past year. Some manufacturers wouldn't put nearly as much 
effort into it.

Thanks again,

   -dwight-

      parent reply	other threads:[~2010-05-24 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 16:32 XCP: Crashes on dual Xeon HP ProLiant systems dwight at supercomputer.org
2010-04-30 18:20 ` Pasi Kärkkäinen
2010-05-01 21:06   ` dwight at supercomputer.org
2010-04-30 19:15 ` Ian Campbell
2010-05-01 21:07   ` dwight at supercomputer.org
2010-05-24 16:35 ` dwight at supercomputer.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201005240935.37338.dwight@supercomputer.org \
    --to=dwight@supercomputer.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).