are you able to tell what's reading/writing the EFI variables? what are the few lines right before the loop starts?
On Fri, Dec 6, 2019 at 10:23 AM Jose Trujillo via coreboot coreboot@coreboot.org wrote:
Dear Matt/All:
I enabled Tianocore debug in coreboot and the serial debug dump showed me Tianocore was trying to open a ATA / ATAPI device and was getting stuck there, so, i disabled a still driverless "ATA" device devicetree until I attach some driver.
After flashing this change, the first boot/reboot will go without delay (normal fast tianocore boot) but after the second boot/reboot the serial dump shows the following long and repeated loop of the following:
Added variable: 0x0, val size: 0 Found variable: key size: 0x0, val size: 0 Added variable: 0x0, val size: 0 Found variable: key size: 0x0, val size: 0 Added variable: 0x0, val size: 0 Found variable: key size: 0x0, val size: 0 Added variable: 0x0, val size: 0 Found variable: key size: 0x0, val size: 0 Added variable: 0x0, val size: 0 Found variable: key size: 0x0, val size: 0 Added variable: 0x0, val size: 0 Found variable: key size: 0x0, val size: 0
Several minutes later boots normal. If someone here knows how to fix it or suspect which could be the reason please let me know. I will ask for help in the EDK2 mail list too.
Thank you, Jose Trujillo.
are you getting serial output via it from coreboot? If not, enabling Tianocore debug output is just going to make that boot time longer.
I'd recommend disabling all serial output and seeing what your boot time is then. If normal, then you know it's the culprit and can start debugging the coreboot side of things
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org