From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen/stable 2.6.32.9 32bit dom0 kernel crashes early on boot
Date: Thu, 04 Mar 2010 12:18:05 -0800 [thread overview]
Message-ID: <4B90157D.5090900@goop.org> (raw)
In-Reply-To: <20100304195337.GF2761@reaktio.net>
On 03/04/2010 11:53 AM, Pasi Kärkkäinen wrote:
> 32bit PAE 2.6.32.9 xen/stable dom0 kernel crashes early on my (old) testbox..
>
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-xen-stable-2.6.32.9-32b-crash-log01.txt
>
> ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
> ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
> ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
> (XEN) mm.c:1746:d0 Bad L1 flags 80000100
> (XEN) mm.c:778:d0 Bad L1 flags 80000100
>
Does the machine support NX? I'm guessing no.
J
next prev parent reply other threads:[~2010-03-04 20:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 19:53 xen/stable 2.6.32.9 32bit dom0 kernel crashes early on boot Pasi Kärkkäinen
2010-03-04 20:18 ` Jeremy Fitzhardinge [this message]
2010-03-04 20:23 ` Pasi Kärkkäinen
2010-03-04 20:28 ` Pasi Kärkkäinen
2010-03-04 21:33 ` Jeremy Fitzhardinge
2010-03-05 7:13 ` Pasi Kärkkäinen
2010-03-05 10:51 ` Pasi Kärkkäinen
2010-03-06 15:05 ` Pasi Kärkkäinen
2010-03-08 18:17 ` Konrad Rzeszutek Wilk
2010-03-09 18:37 ` Pasi Kärkkäinen
2010-03-09 19:33 ` Jeremy Fitzhardinge
2010-03-18 22:59 ` Pasi Kärkkäinen
2010-03-18 23:25 ` Jeremy Fitzhardinge
2010-03-18 23:32 ` Jeremy Fitzhardinge
2010-03-18 23:37 ` Pasi Kärkkäinen
2010-03-19 22:20 ` M A Young
2010-03-19 22:57 ` Jeremy Fitzhardinge
2010-03-20 1:00 ` Jeremy Fitzhardinge
2010-03-23 4:03 ` Jeremy Fitzhardinge
2010-03-23 7:02 ` Pasi Kärkkäinen
2010-03-23 11:18 ` Re: xen/stable 2.6.32.9 32bit dom0 kernel crashes early on boot / works now! Pasi Kärkkäinen
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=4B90157D.5090900@goop.org \
--to=jeremy@goop.org \
--cc=pasik@iki.fi \
--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.