From: Russ Anderson <rja@sgi.com>
To: Valdis.Kletnieks@vt.edu
Cc: Cliff Wickman <cpw@sgi.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu, hpa@zytor.com,
tglx@linutronix.de, rja@americas.sgi.com
Subject: Re: [PATCH v3] x86: UV kdump reboot fix
Date: Sat, 2 Apr 2011 19:01:53 -0500 [thread overview]
Message-ID: <20110403000153.GC31742@sgi.com> (raw)
In-Reply-To: <45253.1301777257@localhost>
On Sat, Apr 02, 2011 at 04:47:37PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 31 Mar 2011 09:32:02 CDT, Cliff Wickman said:
> > From: Cliff Wickman <cpw@sgi.com>
> >
> > After a crash dump on an SGI Altix UV system the crash kernel fails to
> > cause a reboot. EFI mode is disabled in the kdump kernel, so only the
> > reboot_type of BOOT_ACPI works.
>
> > + /*
> > + * for a kdump kernel the reset must be BOOT_ACPI, not BOOT_EFI, as
> > + * EFI is not enabled in the kdump kernel.
> > + */
> > + if (is_kdump_kernel())
> > + reboot_type = BOOT_ACPI;
> > }
>
> What happens if some bozo builds their own kdump kernel that has EFI enabled?
kdump can use the same EFI enabled kernel currently running on the
system. When kexec starts the kdump kernel it indicates that
EFI is not enabled so the kernel does not use EFI.
So what would happen is the bozo built kdump kernel would
work just fine.
There are a lot of detailed discussions of EFI & kdump if you want
to know the details.
http://lkml.org/lkml/2010/7/27/315
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
prev parent reply other threads:[~2011-04-03 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 14:32 [PATCH v3] x86: UV kdump reboot fix Cliff Wickman
2011-03-31 15:57 ` Ingo Molnar
2011-03-31 20:06 ` [tip:x86/urgent] x86, UV: Fix kdump reboot tip-bot for Cliff Wickman
2011-04-02 20:47 ` [PATCH v3] x86: UV kdump reboot fix Valdis.Kletnieks
2011-04-03 0:01 ` Russ Anderson [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=20110403000153.GC31742@sgi.com \
--to=rja@sgi.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cpw@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rja@americas.sgi.com \
--cc=tglx@linutronix.de \
/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