From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: xen-devel@lists.xen.org, daniel.kiper@oracle.com
Subject: Re: Xen 4.2 with EFI on IBM x3650 ACPI Bug
Date: Fri, 30 Nov 2012 11:26:25 -0500 [thread overview]
Message-ID: <20121130162623.GA5481@localhost.localdomain> (raw)
In-Reply-To: <20121108084258.GA5544@jajo.eggsoft>
On Thu, Nov 08, 2012 at 09:42:58AM +0100, Jacek Konieczny wrote:
> Hello,
>
> I am digging up the old thread just to show a workaround for the
> IBM xSeries ACPI problem under EFI…
Great. Thx
>
> On Fri, Oct 19, 2012 at 01:33:07PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Fri, Oct 19, 2012 at 09:10:36AM +0100, Jan Beulich wrote:
> > > >>> On 19.10.12 at 01:43, Allan Scheid <avs.009@gmail.com> wrote:
> > > > Bad news, i am seeing the log output and after the xen.efi boot this still
> > > > appears on log:
> > > >
> > > > Into messages:
> > > > Oct 18 20:27:36 lca-fw kernel: [ 0.000000] ACPI BIOS Bug: Error: A valid
> > > > RSDP was not found (20120711/tbxfroot-219)
> > > > Oct 18 20:27:36 lca-fw kernel: [ 0.000000] NUMA turned off
> > > > Oct 18 20:27:36 lca-fw kernel: [ 3.759750] pci 0000:00:01.0: can't find
> > > > IRQ for PCI INT A; please try using pci=biosirq
> > > > Oct 18 20:27:36 lca-fw kernel: [ 3.764011] pci 0000:00:1a.0: can't find
> > > > IRQ for PCI INT A; please try using pci=biosirq
>
> IRQs are not the only problem. Only a single CPU would be detected
> without ACPI.
>
> > > Of course - you also need the kernel to be capable of obtaining
> > > the necessary EFI information from Xen. That's a separate patch
> > > (an early port of the one we have to the pvops kernel was
> > > posted on the list a few months ago, but I don't know what its
> > > status or disposition is - Konrad?).
>
> Yeah… it will be great to see this patch set updated and included
> upstream.
Daniel is the one that is going to take a hard look at making this
work nicely. CC-ing him here so he knows about this work-around.
>
> >
> > Daniel is taking a stab at it. He got the hardware. But this is good
> > to know that there is hardware that removes the RSDT from the low memory
> > and only allows to get it from the EFI.
>
> The firmware rather does not copy the RSDT to the low memory before
> trying to boot in the legacy BIOS mode.
>
>
>
> And here is the workaround, which does not require kernel patching:
>
> 1. Make sure your kernel is compiled with CONFIG_KEXEC=y (kexec is not
> needed for the workaround, but it enables the Linux kernel command-line
> option used later)
>
> 2. Boot xen natively via EFI – use xen.efi not GRUB multiboot (GRUB
> EFI chainloader will be ok too)
>
> 3. Note the RSDP address found by Xen:
>
> # xl dmesg | grep RSDP
> (XEN) ACPI: RSDP 7F7FE014, 0024 (r2 IBM )
>
> 4. Add this to the dom0 kernel command-line (in the xen.cfg file used by
> xen.efi):
>
> acpi_rsdp=0x7F7FE014
>
> The Linux kernel will find the ACPI RSDP and will be able to initialize
> IRQs and SMP properly. This still won't be a proper EFI interface, so
> the 'efivars' module and 'efibootmgr' utility won't work, but this is
> not as critical as ACPI.
>
> Greets,
> Jacek
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-11-30 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 4:09 Xen 4.2 with EFI on IBM x3650 ACPI Bug Allan Scheid
2012-10-15 10:53 ` Jan Beulich
[not found] ` <CANchcZxqXDrsXEAnatWca+YWzoqB5b0nDWzfMk+6aj_SfPFBsw@mail.gmail.com>
2012-10-18 23:43 ` Allan Scheid
2012-10-19 8:10 ` Jan Beulich
2012-10-19 17:33 ` Konrad Rzeszutek Wilk
2012-10-22 20:02 ` Allan Scheid
2012-11-08 8:42 ` Jacek Konieczny
2012-11-30 16:26 ` Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-23 10:16 Daniel Kiper
2012-11-02 2:02 ` Allan Scheid
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=20121130162623.GA5481@localhost.localdomain \
--to=konrad@kernel.org \
--cc=daniel.kiper@oracle.com \
--cc=xen-devel@lists.xen.org \
/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).