Messages in this thread |  | | Date | Sat, 2 Apr 2011 19:01:53 -0500 | | From | Russ Anderson <> | | Subject | Re: [PATCH v3] x86: UV kdump reboot fix |
| |
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
|  |