xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Goncalo Gomes <Goncalo.Gomes@EU.CITRIX.COM>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: crash in is_xen_swiotlb_buffer
Date: Tue, 13 Mar 2012 12:57:38 -0400	[thread overview]
Message-ID: <20120313165738.GI19228@phenom.dumpdata.com> (raw)
In-Reply-To: <20120313155842.GA24715@eire.uk.xensource.com>

On Tue, Mar 13, 2012 at 03:58:42PM +0000, Goncalo Gomes wrote:
> On Tue, 13 Mar 2012, Goncalo Gomes wrote:
> 
> > On Tue, 13 Mar 2012, Konrad Rzeszutek Wilk wrote:
> > 
> > > 
> > > On Mar 12, 2012 12:28 PM, "Goncalo Gomes" <Goncalo.Gomes@eu.citrix.com<mailto:Goncalo.Gomes@eu.citrix.com>> wrote:
> > > >
> > > > I've compiled unstable c/s: 5d20d2f6ffed and linux 3.2.9 but I've been
> > > 
> > > Do you get similar issues with Xen 4.1?
> > 
> > Can't say I tried it, but I can give it a spin. Any specific tag?
> 
> As I cloned unstable from a local dir into a different dir in the 
> server to checkout 4.1.0, the server crashed again, which leads me to 
> think minimal dom0 stress may be just enough to reproduce it in my 
> environment. I'll be doing some more testing to see if I can find out 
> what it takes.
> 
> In any case, I've done some minimal testing with 4.1.0-branch, such as 
> having 10 instances of update-grub running in parallel, a find / -ls, 
> etc.
> 
> 4.1.0 seems to handle it well, AFAICT.

OK. So xen-unstable looks to have a bug somewhere.
> 
> Goncalo
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2012-03-13 16:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 16:32 crash in is_xen_swiotlb_buffer Goncalo Gomes
2012-03-13  8:39 ` Konrad Rzeszutek Wilk
2012-03-13 14:26   ` Goncalo Gomes
2012-03-13 14:27     ` Goncalo Gomes
2012-03-13 15:58     ` Goncalo Gomes
2012-03-13 16:57       ` Konrad Rzeszutek Wilk [this message]
2012-03-13 17:14       ` Goncalo Gomes
2012-03-13 16:55     ` Konrad Rzeszutek Wilk
2012-03-13 17:15       ` Goncalo Gomes
2012-03-13 17:32         ` Goncalo Gomes
2012-03-13 17:35           ` Konrad Rzeszutek Wilk
2012-03-13 18:04             ` Goncalo Gomes
2012-03-13 19:09               ` Goncalo Gomes
2012-03-13 19:25                 ` Konrad Rzeszutek Wilk
2012-03-13 22:34                   ` Goncalo Gomes
2012-03-13 22:33                     ` Konrad Rzeszutek Wilk
2012-03-13 23:45                     ` Konrad Rzeszutek Wilk
2012-03-16 19:11                       ` Goncalo Gomes
2012-03-16 19:59                         ` Konrad Rzeszutek Wilk
2012-03-18 15:50                           ` Goncalo Gomes
2012-05-02 19:50                             ` Konrad Rzeszutek Wilk
2012-05-03 10:20                               ` Goncalo Gomes

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=20120313165738.GI19228@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Goncalo.Gomes@EU.CITRIX.COM \
    --cc=konrad@darnok.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).