From: Keir Fraser <keir.xen@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xensource.com, gianni.tedesco@citrix.com,
andrew.thomas@oracle.com, Jeremy Fitzhardinge <jeremy@goop.org>,
Ian
Cc: swente@infinitumb.de
Subject: Re: L1[0x1fb] = 0000000000000000 which faults on one type of machine but on another works?
Date: Wed, 16 Mar 2011 22:32:16 +0000 [thread overview]
Message-ID: <C9A6EAF0.14F24%keir.xen@gmail.com> (raw)
In-Reply-To: <20110316221912.GA13035@dumpdata.com>
On 16/03/2011 22:19, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> wrote:
> OK, so I've come up a fix that is a back-port of how 2.6.38 does it
> which is that it removes the check I mentioned above and in xen_set_fixmap
> we set the FIX_APIC_BASE to actually point to a dummy ioapic_mapping.
> It is 7cb068cf1ba90425e12f3a7b3caed9d018fa9b8c in for-2.6.32/bug-fixes
>
> Gianni, you might want to check this out in case it fixes the problem you
> are experiencing.
>
> 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?
Could the native_apic_read() come from ACPI DSDT of that particular machine
type (x3850)?
K.
next prev parent reply other threads:[~2011-03-16 22:32 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 [this message]
2011-03-17 10:25 ` Jan Beulich
2011-03-17 15:52 ` Konrad Rzeszutek Wilk
2011-03-17 16:12 ` Konrad Rzeszutek Wilk
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=C9A6EAF0.14F24%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=andrew.thomas@oracle.com \
--cc=gianni.tedesco@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).