All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Traugott <stevegt@TerraLuna.Org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: stress testing was: Re: blocking Xen 3.X production use: soft lockup bugs
Date: Fri, 11 Aug 2006 18:46:58 -0700	[thread overview]
Message-ID: <20060812014657.GF14094@terraluna.org> (raw)
In-Reply-To: <C0FA1A65.27D%Keir.Fraser@cl.cam.ac.uk>

On Sat, Aug 05, 2006 at 09:50:29AM +0100, Keir Fraser wrote:
> On 4/8/06 9:21 pm, "Steve Traugott" <stevegt@TerraLuna.Org> wrote:
> > On Thu, Aug 03, 2006 at 09:03:18AM +0100, Keir Fraser wrote:
> >> Also older versions using sedf scheduler (which has now been patched to
> >> avoid this) could end up with domain0 consuming all CPU and starving
> >> other guests, leading to softlockup errors. We haven't seen any such
> >> errors on our own test machines since this was fixed. Of course, that
> >> doesn't mean there aren't problems with other test scenarios!
> > 
> > That is exactly what was happening.  I did more testing yesterday and
> > last night (-testing changeset 9732), and realized that I was only
> > seeing soft lockups on the second of two domU guests, and only when
> > running a heavy load in dom0.  According to 'xm vcpu-list' the second
> > guest was on CPU 0, as was the workload in dom0...  I added more
> > workload processes to consume both CPUs in dom0, and of course when I
> > did that, the first guest ground to a halt and started showing soft
> > lockups as well.
> 
> It's *always* worth trying the tip of 3.0-testing if you're seeing problems
> with a strictly older version. In this case there are about 50 newer
> changesets, many of which are the result of aggressive testing by Suse for
> SLES10. Well worth having.

In between everything else I'm partway through a build of testing tip;
I really need to automate that, including all my local modules, some
stress tests, and so on -- ever since Xen 1.0 we've been using various
combinations of Xen, AFS, DRBD, and soon aoe, in an environment which
is apparently good at finding bugs and regression in all of the
above...  :-}

Because we rely on these things so much it would be in my best
interests to write a "daily build" style stress test harness -- if I
do this, I'd probably do a periodic post similar to Rick's and David's
xm-test results, maybe some web stats and so on.  Does this sound
like something that would be useful to other folks?

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
Managing Partner, TerraLuna LLC
stevegt@TerraLuna.Org -- http://www.t7a.org

      parent reply	other threads:[~2006-08-12  1:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 22:25 blocking Xen 3.X production use: soft lockup bugs Ian Pratt
2006-08-03  0:27 ` Steve Traugott
2006-08-03  8:07   ` Keir Fraser
2006-08-03  8:03 ` Keir Fraser
2006-08-04 20:21   ` Steve Traugott
2006-08-05  8:50     ` Keir Fraser
2006-08-05 11:59       ` Harry Butterworth
2006-08-05 13:45         ` Keir Fraser
2006-08-05 14:33           ` Harry Butterworth
2006-08-12  1:46       ` Steve Traugott [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=20060812014657.GF14094@terraluna.org \
    --to=stevegt@terraluna.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.