On Fri, May 24, 2013 at 08:11:01PM +0000, Matthew Garrett wrote: > On Fri, 2013-05-24 at 15:05 -0500, Russ Anderson wrote: > > > One other data point is if the query_variable_info call is hacked to > > remove one of the EFI flags (ie comment out EFI_VARIABLE_BOOTSERVICE_ACCESS) > > the efi_call_phys4() call fails with EFI_INVALID_PARAMETER and > > the system boots. Of course it does not create /sys/firmware/efivars > > entries and complains "[Firmware Bug]: efi: Inconsistent initial sizes". > > But at least it boots. > > EFI_VARIABLE_RUNTIME_ACCESS is only legal if > EFI_VARIABLE_BOOTSERVICE_ACCESS is set, so it's correct to throw > EFI_INVALID_PARAMETER there. Yes. The point of the experiment was to see if it returned a valid failure status (which it did) and see if the boot still failed (which it didn't). So something about going deeper into that call seems to trigger the failure. Why does the kernel still try to create /sys/firmware/efivars/ entries in the original failure even though efi_call_phys4() failed? Or does it always try to create those entries and GetNextVariable() blows up in the original failure but not in my experiment? Thanks, -- Russ Anderson, OS RAS/Partitioning Project Lead SGI - Silicon Graphics Inc rja@xxxxxxx -- 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
