All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com, andrew.thomas@oracle.com,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	keir.xen@gmail.com, swente@infinitumb.de,
	gianni.tedesco@citrix.com
Subject: Re: L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works?
Date: Thu, 17 Mar 2011 12:12:16 -0400	[thread overview]
Message-ID: <20110317161216.GB15417@dumpdata.com> (raw)
In-Reply-To: <20110317155211.GA29603@dumpdata.com>

On Thu, Mar 17, 2011 at 11:52:12AM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 17, 2011 at 10:25:11AM +0000, Jan Beulich wrote:
> > >>> On 16.03.11 at 23:19, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > > But one thing I can't understand is why on one machine (IBM x3850)
> > > I get this crash, while another one with the same pagetable contents
> > > (L1 has nothing for 0x1fb) it works just fine? I added a panic and used
> > > the Xen hypervisor kdb to manually inspect the pagetable, and it has
> > > the same contents as the IBM x3850 -but it boots fine with this invalid 
> > > value.
> > > Any ideas?
> > 
> > Without seeing the full stack trace it's hard to tell. To me, it looks
> > like a mistake for native_apic_read() to be called at all under Xen,
> > and perhaps there's one lurking somewhere that gets hit only on
> > those IBM (Summit?) machines.
> 
> That was it. When we bootup we call 'set_xen_basic_apic_ops' which

Forgot to mention it but thank you for steering me in the right direction!

The patches are in
 git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git for-2.6.32/bug-fixes

  reply	other threads:[~2011-03-17 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 22:19 L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works? Konrad Rzeszutek Wilk
2011-03-16 22:32 ` Keir Fraser
2011-03-17 10:25 ` Jan Beulich
2011-03-17 15:52   ` Konrad Rzeszutek Wilk
2011-03-17 16:12     ` Konrad Rzeszutek Wilk [this message]
2011-03-17 16:12     ` Jan Beulich
2011-03-17 16:41       ` Konrad Rzeszutek Wilk
2011-03-17 17:21         ` Jeremy Fitzhardinge
2011-03-17 19:56         ` [PATCH] xen/apic: Provide an 'apic_xen' to set the override the apic->[read|write] for all cases Konrad Rzeszutek Wilk
2011-03-22 13:10 ` L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works? Gianni Tedesco

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=20110317161216.GB15417@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=andrew.thomas@oracle.com \
    --cc=gianni.tedesco@citrix.com \
    --cc=jeremy@goop.org \
    --cc=keir.xen@gmail.com \
    --cc=swente@infinitumb.de \
    --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.