From: "Jan Beulich" <JBeulich@novell.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, "xen.org" <ian.jackson@eu.citrix.com>
Subject: Re: [xen-unstable test] APIC error on CPU[x] in xcp dom0
Date: Tue, 25 Jan 2011 16:18:42 +0000 [thread overview]
Message-ID: <4D3F05F2020000780002E691@vpn.id2.novell.com> (raw)
In-Reply-To: <AANLkTimyWAtGCoXgW0cuxrO6i6iD6X6HCK4AhK+cj3_y@mail.gmail.com>
>>> On 25.01.11 at 16:41, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
> On Tue, Jan 25, 2011 at 11:53 AM, Jan Beulich <JBeulich@novell.com> wrote:
>> It's derived from our kernel. Why do you ask, given that the initial
>> set of frightening messages come from the hypervisor?
>
> I haven't been doing bug-triaging very log; but IIUC IanJ's sense was
> that this failure only happened intermittently on XCP dom0 kernels
> (2.6.27.45-something), not on pvops or other kernels. I don't know
> much about the dom0-xen interface, so I was hoping someone who did
> could take a look.
The 2.6.27 kernel is dead as far as we're concerned. Does this
also happen with the 2.6.32 one? (And really I thought for .27
the project was still called XCI - does XCP have both .27 and
.32?)
Jan
next prev parent reply other threads:[~2011-01-25 16:18 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 [this message]
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
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=4D3F05F2020000780002E691@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.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.