From: Julien Grall <julien.grall@citrix.com>
To: Riku Voipio <riku.voipio@linaro.org>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: xl: libxl_domain_info: getting domain info list: Bad address
Date: Fri, 11 Sep 2015 10:50:25 +0100 [thread overview]
Message-ID: <55F2A3E1.3010106@citrix.com> (raw)
In-Reply-To: <CAAqcGHnGyUvizboGSDNpoH_QLH=5B4RPmiRCKC+4ka7jzdYC7w@mail.gmail.com>
On 11/09/2015 08:55, Riku Voipio wrote:
> It looks like the errors started Sep 4th, while Sep 3rd was still OK.
> The Xen binary was same for both test runs, only the kernel (which
> follows mainline) was changed.
>
> Failing kernel was 807249d3ada1ff28a47c4054ca4edd479421b671
> While last succeeding was 1e1a4e8f439113b7820bc7150569f685e1cc2b43
Thank you for narrowing down.
> This range includes merge of ARM development updates from Russell King
> for 4.3, which probably contains the change that breaks Xen.
I've been able to reproduce it on midway so it's not related to the
Arndale board.
Although, I don't see anything obvious in the log which could break Xen.
I will try a manual bisection to see if I can fingered a specific commit.
--
Julien Grall
next prev parent reply other threads:[~2015-09-11 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 17:07 xl: libxl_domain_info: getting domain info list: Bad address Julien Grall
2015-09-11 7:55 ` Riku Voipio
2015-09-11 9:50 ` Julien Grall [this message]
2015-09-11 8:52 ` Ian Campbell
2015-09-11 9:26 ` Julien Grall
2015-09-11 9:38 ` Ian Campbell
2015-09-11 15:34 ` Ian Jackson
2015-09-11 16:01 ` Ian Campbell
2015-09-11 14:50 ` Julien Grall
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=55F2A3E1.3010106@citrix.com \
--to=julien.grall@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=riku.voipio@linaro.org \
--cc=wei.liu2@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.