All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Heinlein <heinlein@okit.de>
To: xen-devel@lists.xensource.com
Cc: 2013pfoley@tjhsst.edu
Subject: Re: Re: Xen dom0 linux kernel 3.1 boot failure ptwr_emulate: could not get_page_from_l1e
Date: Tue, 01 Nov 2011 13:47:15 +0100	[thread overview]
Message-ID: <4EAFEA53.7070009@okit.de> (raw)
In-Reply-To: <20111031140836.GA9245@phenom.dumpdata.com>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

I'm not sure if it was obvious, but yesterday I noticed that setting the
"MPS table mode" to 'Disabled' actually made SMP stop working, i.e. the
kernel only recognized a single CPU. This is of course not an option, so
I enabled (set to 'Full Table APIC') the setting again and played around
with my kernel config a bit. The kernel that crashed had
CONFIG_X86_MPPARSE=y, and if I disable that, it boots fine (with SMP,
and with the BIOS setting set to 'Full Table APIC').

So, I for one am quite happy now as I finally found a working
configuration. But I'd still like to know if this is a hardware-specific
issue, and/or a bug in Xen.

Konrad Rzeszutek Wilk wrote, on 10/31/2011 03:08 PM:
> Oh nice. What does you /proc/interrupts look like compared to
> baremetal?

While I was performing all my kernel tests, I saved the outputs of
`dmesg` and `cat /proc/interrupts`. Sorry for attaching a tarball, but
I'd like to give you as much information as possible. You'll probably
only need the latest tests (#5 to #7), but just in case, I also included
the others.

Contents of the tarball:

Baremetal tests:
xen-hp/1/: MPS mode 'Full Table APIC', CONFIG_X86_MPPARSE=y, SMP working
xen-hp/2/: MPS mode 'Full Table APIC', CONFIG_X86_MPPARSE=n, SMP working
xen-hp/3/: MPS mode 'Disabled', CONFIG_X86_MPPARSE=y, SMP not working
xen-hp/4/: MPS mode 'Disabled', CONFIG_X86_MPPARSE=n, SMP not working

Xen tests:
xen-hp/5/: MPS mode 'Disabled', CONFIG_X86_MPPARSE=n, SMP not working
xen-hp/6/: MPS mode 'Full Table APIC', CONFIG_X86_MPPARSE=n, SMP working
xen-hp/7/: MPS mode 'Full Table APIC', CONFIG_X86_MPPARSE=y, CRASHES

(Therefore, #6 is the best working solution; #7 is what originally
triggered the crash.)

Thanks.


[-- Attachment #2: xen-hp.tar.bz2 --]
[-- Type: application/x-bzip, Size: 97821 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-11-01 12:47 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
2011-11-01 12:47     ` Tobias Heinlein [this message]
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=4EAFEA53.7070009@okit.de \
    --to=heinlein@okit.de \
    --cc=2013pfoley@tjhsst.edu \
    --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.