From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [xen-unstable test] APIC error on CPU[x] in xcp dom0
Date: Tue, 1 Feb 2011 14:07:38 +0000 [thread overview]
Message-ID: <AANLkTinY3GXKdR4MhZfHiG67qR1o3zRUeK_xbE+ph-U3@mail.gmail.com> (raw)
In-Reply-To: <19776.12089.12569.256559@mariner.uk.xensource.com>
Seen again in flight 5506:
http://www.chiark.greenend.org.uk/~xensrcts/logs/5506/test-amd64-xcpkern-i386-pair/info.html
-George
On Wed, Jan 26, 2011 at 2:27 PM, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> George Dunlap writes ("Re: [Xen-devel] [xen-unstable test] APIC error on CPU[x] in xcp dom0"):
>> Then perhaps we should be testing the 2.6.32 kernel instead? There was
>> a reason we were testing 2.6.27 instead of 2.6.32, but I don't remember
>> the details.
>
> I tried updating it, but the .32 xcp kernel failed a lot of the tests
> that the .27 one passed. Since for the xen upstream tests I'm
> primarily using the xcp kernel as a baseline (to help differentiate
> xen vs dom0 pvops kernel bugs) it didn't seem very important to move
> up to .32.
>
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2011-02-01 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 10:52 [xen-unstable test] APIC error on CPU[x] in xcp dom0 George Dunlap
2011-01-25 11:53 ` Jan Beulich
2011-01-25 15:41 ` George Dunlap
2011-01-25 16:18 ` Jan Beulich
2011-01-25 17:41 ` Ian Campbell
2011-01-25 17:57 ` Pasi Kärkkäinen
2011-01-26 12:19 ` George Dunlap
2011-01-26 14:27 ` Ian Jackson
2011-02-01 14:07 ` George Dunlap [this message]
2011-01-25 17:36 ` Ian Jackson
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=AANLkTinY3GXKdR4MhZfHiG67qR1o3zRUeK_xbE+ph-U3@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@novell.com \
--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.