From: Khalid Aziz <khalid@gonehiking.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Dave Young <dyoung@redhat.com>,
horms@verge.net.au, kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH v2] kdump: pass acpi_rsdp= to 2nd kernel for efi booting
Date: Fri, 19 Oct 2012 14:09:38 -0600 [thread overview]
Message-ID: <1350677378.30243.19.camel@rhapsody> (raw)
In-Reply-To: <20121019145300.GC27052@redhat.com>
On Fri, 2012-10-19 at 10:53 -0400, Vivek Goyal wrote:
> On Thu, Oct 18, 2012 at 02:20:46PM -0700, Eric W. Biederman wrote:
> >
> > If we are passing the acpi sections is that not enough for the kernel
> > to find the rdsp area? I'm just a bit surprised we need this patch
> > is all.
> >
> > Somehow it seems a bit ugly to pass information that could be conveyed
> > in the memory map on the command line.
>
> I have no idea how UEFI case is working. Dave/Khalid might have more
> details on this.
On a UEFI machine with CSM, kernel finds RSDP in EBDA. On a UEFI machine
with no CSM, kernel fails to find RSDP and here is the message I see:
ACPI BIOS Bug: Error: A valid RSDP was not found (20120913/tbxfroot-219)
--
Khalid
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-10-19 20:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 3:16 [PATCH v2] kdump: pass acpi_rsdp= to 2nd kernel for efi booting Dave Young
2012-10-18 21:20 ` Eric W. Biederman
2012-10-19 0:26 ` Simon Horman
2012-10-19 14:53 ` Vivek Goyal
2012-10-19 20:09 ` Khalid Aziz [this message]
2012-10-21 3:06 ` Eric W. Biederman
2012-10-22 15:43 ` Vivek Goyal
2012-10-23 13:33 ` Khalid Aziz
-- strict thread matches above, loose matches on Subject: below --
2012-10-18 3:10 Dave Young
2012-10-18 14:56 ` Khalid Aziz
2012-10-18 19:11 ` Vivek Goyal
2012-10-18 19:22 ` Khalid Aziz
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=1350677378.30243.19.camel@rhapsody \
--to=khalid@gonehiking.org \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox