On Thu, Aug 29, 2013 at 3:15 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Aug 29, 2013 at 08:18:39AM -0400, Josh Boyer wrote: >> On Wed, Aug 28, 2013 at 10:26 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >> > Hi all, >> > >> > I've been messing with UEFI booting a kernel and then later on, using >> > kexec to boot another kernel, and noticed that the kexec'ed kernel is >> > not really in EFI mode, although the EFI framebuffer seems present and >> > able to be used. >> > >> > Is this to be expected? I'd think that the EFI framebuffer wouldn't be >> > around anymore. Odds are this is a BIOS bug, given that the machine I'm >> > using is a really old UEFI mode (i.e. before secure boot mode ever >> > showed up), but should it work this way? >> >> AFAIK, it's to be expected at this point. kexec doesn't work as it >> should with UEFI. > > How "should" it work? It seems to boot a kernel just fine, although not > in EFI mode, which makes sense (I had forgotten about the BootServices > stuff.) Right, well in my ideal world if you kexec a kernel on a UEFI machine, the resulting kernel is up and running as the previous kernel was. Which is to say, it's in UEFI mode. Maybe that's more hassle than it's worth but that was what I was thinking when I said "should". It may be possible to use a kexec'd kernel as it boots today on these machines. I believe the current line of thought from the kdump people is that kdump kernels could operate in this mode, for example. That's a short-lived uptime and scoped usecase though. josh -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
