From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tobias Heinlein <theinlein@vandium.net>, 2013pfoley@tjhsst.edu
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com
Subject: Re: Xen dom0 linux kernel 3.1 boot failure ptwr_emulate: could not get_page_from_l1e
Date: Mon, 31 Oct 2011 10:08:36 -0400 [thread overview]
Message-ID: <20111031140836.GA9245@phenom.dumpdata.com> (raw)
In-Reply-To: <loom.20111031T140651-901@post.gmane.org>
On Mon, Oct 31, 2011 at 01:17:09PM +0000, Tobias Heinlein wrote:
> Hi,
>
> 2013pfoley <2013pfoley <at> tjhsst.edu> writes:
> > [..]
> >
> > [ 0.000000] last_pfn = 0x63b5ef max_arch_pfn = 0x400000000
> > [ 0.000000] last_pfn = 0xdf62d max_arch_pfn = 0x400000000
> > [ 0.000000] found SMP MP-table at [ffff8800000f4f80] f4f80
> > (XEN) mm.c:945:d0 Error getting mfn 100 (pfn 5555555555555555) from L1
> > entry 8000000000100461 for l1e_owner=0, pg_owner=0
> > (XEN) mm.c:5046:d0 ptwr_emulate: could not get_page_from_l1e()
> > [ 0.000000] BUG: unable to handle kernel NULL pointer dereference at
> > (null)
> > [ 0.000000] IP: [<ffffffff81008a5a>] xen_set_pte+0x3a/0x1f0
> > [ 0.000000] PGD 0
> > [ 0.000000] Oops: 0003 [#1] SMP
> > [ 0.000000] CPU 0
> > [ 0.000000] Modules linked in:
> > [ 0.000000]
> > [ 0.000000] Pid: 0, comm: swapper Not tainted 3.1.0 #4 HP ProLiant
> > DL380 G6
>
> I get the exact same error here. Reading from your output, it seems we have the
> same hardware; I have this problem on a HP ProLiant DL380 G6, too.
>
> After a wild hint from a guy on ##xen to play around with the BIOS settings, I
> was able to narrow down the problem to a setting called "MPS Table Mode". It is
> set to "Full Table APIC" by default (with which the crash occurs), but when it's
> set to "Disabled" Xen boots the kernel just fine.
>
> FWIW, the help text of the setting is: "Multi Processor Specification (MPS)
> Table / APIC Setting is used for interrupt routing. Certain unsupported
> operating systems may require setting the MPS Table Mode to APIC Disabled."
Oh nice. What does you /proc/interrupts look like compared to baremetal?
>
> (BTW, the kernel itself boots fine without Xen. So I'm not sure if this belongs
> to the LKML at all.)
It does not. But CC-ing xen-devel here for further tracking.
next prev parent reply other threads:[~2011-10-31 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 19:34 Xen dom0 linux kernel 3.1 boot failure ptwr_emulate: could not get_page_from_l1e 2013pfoley
2011-10-24 19:34 ` 2013pfoley
2011-10-25 19:25 ` Konrad Rzeszutek Wilk
2011-10-31 13:17 ` Tobias Heinlein
2011-10-31 14:08 ` Konrad Rzeszutek Wilk [this message]
2011-11-01 12:47 ` Tobias Heinlein
2011-11-10 16:36 ` Konrad Rzeszutek Wilk
2011-11-12 21:13 ` Tobias Heinlein
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=20111031140836.GA9245@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=2013pfoley@tjhsst.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=theinlein@vandium.net \
--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.