From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: Xen-4.3 and -unstable regression from changeset "numa-sched: leave node-affinity alone if not in 'auto' mode"
Date: Fri, 29 Nov 2013 11:04:27 +0000 [thread overview]
Message-ID: <529874BB.7070803@citrix.com> (raw)
In-Reply-To: <1385722276.25763.12.camel@kazak.uk.xensource.com>
On 29/11/13 10:51, Ian Campbell wrote:
> On Thu, 2013-11-28 at 21:17 +0000, Andrew Cooper wrote:
>> the XenServer patch queue on
> Are you positive that the bug is in the underlying Xen tree and not some
> interaction with a patch in your queue?
>
> A boot time issue ought to be reasonably easy to test with a bare tree.
>
> Ian.
>
I am not sure of anything at the moment, although I have found one
instance of a crash with none of the XenServer patch queue whatsoever.
At the moment, I have narrowed the problem down to a handful of
instructions writing 0s into a well-formed region of the stack.
Clearly, this is not correct, and every tweak of the debugging causes
the problem to jump around.
~Andrew
next prev parent reply other threads:[~2013-11-29 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 12:31 Xen-4.3 and -unstable regression from changeset "numa-sched: leave node-affinity alone if not in 'auto' mode" Andrew Cooper
2013-11-28 13:05 ` Dario Faggioli
2013-11-28 15:09 ` George Dunlap
2013-11-28 15:14 ` Dario Faggioli
2013-11-28 15:16 ` Andrew Cooper
2013-11-28 21:17 ` Andrew Cooper
2013-11-28 23:30 ` George Dunlap
2013-11-29 10:51 ` Ian Campbell
2013-11-29 11:04 ` Andrew Cooper [this message]
2013-12-02 14:01 ` Andrew Cooper
2013-12-02 14:36 ` Jan Beulich
2013-12-03 19:53 ` Andrew Cooper
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=529874BB.7070803@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--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.