All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
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>,
	Steve Traugott <stevegt@TerraLuna.Org>
Subject: Re: blocking Xen 3.X production use: soft lockup bugs
Date: Sat, 05 Aug 2006 15:33:12 +0100	[thread overview]
Message-ID: <1154788392.18468.5.camel@localhost.localdomain> (raw)
In-Reply-To: <C0FA5F82.8AB%Keir.Fraser@cl.cam.ac.uk>

On Sat, 2006-08-05 at 14:45 +0100, Keir Fraser wrote:
> On 5/8/06 12:59 pm, "Harry Butterworth"
> <harry@hebutterworth.freeserve.co.uk> wrote:
> 
> > Another data point: Yesterday I was working with an unstable changeset
> > from the morning (I think about halfway through the qemu patches) and
> > running HVM xm-test to try to debug the create-concurrent failures.
> > qemu_dm was taking 100% of one core and I got about 6 soft lockups in
> > dom0 and 2 dom0 hangs.
> > 
> > I'm not sure exactly why HVM testing is all over the floor for me, maybe
> > I picked a bad changeset or perhaps the recent ubuntu updates have
> > broken something.
> > 
> > It's possible that there are still some lurking soft lockup issues
> > anyway.
> 
> Well, I believe the issues are sorted out for paravirtualised guests at
> least. Maybe there are lurkers for HVM guests -- if so, and they're of the
> scale of hangs and softlockups, we'd really like detailed info so we could
> try to repro.

I'll post the changeset and any more details I can when I get back into
work on Monday but dd was segfaulting for me due to a locale issue after
the ubuntu update so I don't really have a lot of confidence that it's
even a xen problem yet.

Harry.

  reply	other threads:[~2006-08-05 14:33 UTC|newest]

Thread overview: 14+ 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 [this message]
2006-08-12  1:46       ` stress testing was: " Steve Traugott
  -- strict thread matches above, loose matches on Subject: below --
2006-08-07 14:15 Harry Butterworth
2006-08-05  7:38 Ian Pratt
2006-08-02 20:54 Steve Traugott
2006-08-02 22:48 ` Steve Traugott

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=1154788392.18468.5.camel@localhost.localdomain \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=stevegt@TerraLuna.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 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.