On 03/21/2013 07:22 AM, Lingzhu Xiang wrote: > Tested-by: Lingzhu Xiang <lxiang@xxxxxxxxxx> Great, thanks! > Reproduced with 3.9-rc3 in QEMU/OVMF. The kernel gets stuck in a loop. > > Verified with 3.9-rc3 with this patch. The kernel survives. efivarfs > continues working, though some variables won't show up, as expected. > > [ 2.033855] efivars: duplicate variable: Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c > > This patch has no real impact for users with normal firmware as tested > before on a Windows 8 logo desktop. > > For the record, here is how I create duplicate variables in QEMU/OVMF: > > OVMF EmuVariableFvbRuntimeDxe emulates nvram with a reserved area of > memory (ReserveEmuVariableNvStore). But there seems to be some layers > of cache above this, so directly writing a new duplicate variable here > won't make a difference. I ended up writing an EFI app to scan the > entire memory and replace all L"Boot0004" with L"Boot0001", which > seemed to actually break things (e.g. dmpstore will get stuck). Thanks for going to such lengths to test this. -- Matt Fleming, Intel Open Source Technology Center -- 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
