All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Andrew Bennieston <andrew.bennieston@citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
	jan Beulich <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Investigating a SLES11 guest crash
Date: Fri, 13 Sep 2013 12:50:29 +0100	[thread overview]
Message-ID: <5232FC05.2040409@citrix.com> (raw)
In-Reply-To: <5232F85A.8040501@citrix.com>

On 13/09/2013 12:34, Andrew Bennieston wrote:
> On 13/09/13 12:14, Sander Eikelenboom wrote:
>> Not by any chance running a 3.12 merge window kernel ?
> Nope, the regular SLES11 SP0 2.6.27 kernel.

Some thinks should be pointed out.

This crash is because the guest takes a pagefault before setting up a
pagefault handler.

9 times in 10, the guest boots perfectly well.

This crash is *only* visible with a debug build of Xen, and is a
regression from 4.1

The point of this query is to find out whether there is a bug in the
identified Xen changeset, or whether it simply exposed some other bug.

As things currently stand, there is some regression causing crashes for
older kernels, and we (XenServer) would like to understand what the
regression is and whether it affects more guests than just SLES11 SP0
(irrespective of the fact that people using SLES11 SP0 should really
upgrade)

~Andrew

  reply	other threads:[~2013-09-13 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 10:49 Investigating a SLES11 guest crash Andrew Bennieston
2013-09-13 11:14 ` Sander Eikelenboom
2013-09-13 11:34   ` Andrew Bennieston
2013-09-13 11:50     ` Andrew Cooper [this message]
2013-09-13 12:09       ` Jan Beulich
2013-09-16  9:44       ` George Dunlap
2013-09-13 12:06 ` Jan Beulich

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=5232FC05.2040409@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.bennieston@citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xen.org \
    /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.