All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
	Xen Developers List <xen-devel@lists.xensource.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Problems booting latest xen pv-ops linux kernel
Date: Wed, 25 Nov 2009 11:34:24 -0800	[thread overview]
Message-ID: <4B0D86C0.6000301@goop.org> (raw)
In-Reply-To: <102901357.20091125124659@eikelenboom.it>

On 11/25/09 03:46, Sander Eikelenboom wrote:
> It seems with the bios option "ACPI APIC" on disabled:
> (BTW the description of this bios option is: "Allows you to enable or disable the ACPI support in the APIC, When enabled the ACPI APIC table pointer is included in the RSDT pointer list.")
>   

I wonder what the rationale for this is?  I guess for some legacy OS
support?

> - xen 3.5 tip && 2.6.18.8-xen                            boots fine
> - 2.6.31.6 jeremy's tree (without hypervisor)            boots fine
> - xen 3.5 tip && 2.6.31.6 jeremy's tree                  doesn't boot completely at gives the problems reported.
>
> With the option on enabled, it also boots xen 3.5 tip && 2.6.31.6 fine, but for what i recall i have seen the same problem occur rarely too.
>   

I think we're approaching the point of officially not supporting legacy
modes of operation (non-ACPI, non-APIC).  At the moment we're trying to
support them, but it just adds extra complexity for what I suspect is
little value.

    J

  reply	other threads:[~2009-11-25 19:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 23:18 Problems booting latest xen pv-ops linux kernel Goswin von Brederlow
2009-11-18  7:10 ` Pasi Kärkkäinen
2009-11-18 15:08   ` Konrad Rzeszutek Wilk
2009-11-18 15:28     ` Pasi Kärkkäinen
2009-11-19  5:43       ` Goswin von Brederlow
2009-11-19 17:41         ` Konrad Rzeszutek Wilk
2009-11-20  1:41           ` Goswin von Brederlow
2009-11-20 11:25             ` Sander Eikelenboom
2009-11-20 11:49               ` Sander Eikelenboom
2009-11-20 12:33                 ` Sander Eikelenboom
2009-11-20 14:50               ` Konrad Rzeszutek Wilk
2009-11-20 15:05                 ` Sander Eikelenboom
2009-11-20 22:26                 ` Sander Eikelenboom
2009-11-25 11:46                   ` Sander Eikelenboom
2009-11-25 19:34                     ` Jeremy Fitzhardinge [this message]
2009-11-21  1:26                 ` Goswin von Brederlow
2009-11-23 14:48                   ` Konrad Rzeszutek Wilk
2009-11-19  5:40   ` Goswin von Brederlow
2009-11-19  7:55     ` Pasi Kärkkäinen
2009-11-19  8:00       ` Pasi Kärkkäinen
2009-11-19 10:16         ` Fasiha Ashraf
2009-11-19 10:21           ` Pasi Kärkkäinen
2009-11-20  6:56             ` Fasiha Ashraf
2009-11-20 13:53             ` Fasiha Ashraf

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=4B0D86C0.6000301@goop.org \
    --to=jeremy@goop.org \
    --cc=goswin-v-b@web.de \
    --cc=konrad.wilk@oracle.com \
    --cc=linux@eikelenboom.it \
    --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.