On Fri, 24 May, at 03:49:38PM, Russ Anderson wrote: > 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?
CONFIG_EFI_VARS will try to create /sys/firmware/efivars even without the additional info from the early EFI boot variable code. The early variable code is only a heuristic that is supposed to improve the anti-bricking algorithm in the EFI variable code. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
