I'm enjoying the new EFI STUB interface for booting the kernel without additional bootloaders.
Particularly, I have an entry that the UEFI bios boots automatically on startup, where the entry was added with efibootmgr.
Yesterday, I've tried building 3.5-rc1. Upon rebooting, my system could not boot up, with the UEFI bios jumping to the second entry in the boot order, which is an UEFI shell.
From the UEFI shell, upon issuing:
-> vmlinuz.efi initrd=initramfs-linux.img root=/dev/...
I get a Load: Error and the system halts.
The same procedure works beautifully with 3.3 and 3.4 and the boot process gives me a working linux laptop.
Bad news for me, I do not how to debug it further.
My machine is a Thinkpad T420s, and at least another Thinkpad user is experiencing the same problem at https://bbs.archlinux.org/viewtopic.php?id=136833&p=4 (end of the page)
On the same forum post, another user reports that it works for him, hence it may very well be that the Thinkpad UEFI does something strange this time.
I am sorry if I do not add more information, but all this stuff is new and obscure to me (and I am sorry if I am talking nonsense in the report). I'll gladly come back with as much information as I am guided to provide.
I suspect this is the same bug as #43309. Can you try the commit in comment #5 and see if that kernel boots for you?
Compiled, installed and booted. It came up like a charm! Seems that the linked commit does its magic!
Out of curiosity, will it be merged in 3.5-rc2?
Thanks a lot,
Thanks very much for testing.
Yes, this regression is hitting quite a few users so it will likely be merged for -rc2.
Thank you for the prompt feedback and for such an outstanding job on Linux
*** This bug has been marked as a duplicate of bug 43309 ***