From: "H. Peter Anvin" <hpa@zytor.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] kdump: do not drop entire e820 in crash kernel
Date: Sun, 03 Feb 2013 20:52:35 -0800 [thread overview]
Message-ID: <510F3E93.9080708@zytor.com> (raw)
In-Reply-To: <E1U2DId-0001E4-Df@eag09.americas.sgi.com>
On 02/03/2013 08:04 PM, Cliff Wickman wrote:
> From: Cliff Wickman <cpw@sgi.com>
>
> The crash kernel is not able to find its root device if that device is not
> on PCI 0.
>
> This is because it is booted with the command line option memmap=exactmap
> which currently clears the e820 table. So ACPI processing does not
> find reserved i/o spaces.
>
> This works for a device on PCI 0 because ACPI falls back to a legacy mode.
> But the error message " [Firmware Bug]: PCI: MMCONFIG at
> [mem 0x80000000-0x80cfffff] not reserved in ACPI motherboard resources"
> is written to the log even in this functioning case.
>
> It fails for some devices on UV2, and only for UV2, because SGI seems to
> be the only manufacturer currently using the extended PCI(>0).
>
> The fix is to not drop the entire e820 table on a memmap=exactmap, but
> to preserve all the non-E820_RAM reservations that the BIOS has made.
>
NAK. This is a fundamntal semantic change to something that isn't just
affecting kexec.
This ultimately is the result of the very bad design decision to use the
command line to muck with the target kernel memory map.
The work is underway to fix this, but this is not the right fix.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-02-04 4:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 4:04 [PATCH] kdump: do not drop entire e820 in crash kernel Cliff Wickman
2013-02-04 4:52 ` H. Peter Anvin [this message]
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=510F3E93.9080708@zytor.com \
--to=hpa@zytor.com \
--cc=cpw@sgi.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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