upgrade to 15.0 p9: booting freezes with "EFI framebuffer information"

rwv37

rwv37

I posted this yesterday as bug #295463 on Bugzilla, but am now posting here too just in hopes of getting more eyeballs on it (my main server is effectively dead due to this issue). Details can be found in the bug report, but the tl/dr is that after upgrading 15.0-RELEASE from p8 to p9, the machine freezes during the booting process after reporting "EFI framebuffer information", looking very similar (to my largely ignorant eyes) as a previous bug that was resolved in at least 12, 13, and 14 regarding use (or lack thereof) of "the efi_copy_finish function from amd64_tramp".

Again, details can be found in the bug report on Bugzilla. Any help would be greatly appreciated. Thanks in advance.
 
epower53 said:
Do you have a bectl snapshot you can fall back on?
Click to expand...

I... don't think so? Not entirely sure. I don't think I've ever heard of bectl before. Quick look seems like it's something that makes zfs snapshots somehow directly accessible during the boot process? I do have zfs snapshots, but if there's something that would have had to have been specifically done earlier to make them usable in this way now, then no, I almost certainly don't.
 
Are you using pkgbase or did you go the safe route and stick with freebsd-update? If it's the latter, then you should have automatically created boot environments from running freebsd-update. The freebsd bootloader has option 8, which will let you choose to boot into a different boot environment. May as well press 8 and see if there's anything there...

Edit: just read your bug report. You're using freebsd-update, which is good! You already have a boot environment created (assuming you installed on ZFS). Just boot into the latest BE using the boot loader option 8 and you should be back in business.
 
Hmmm, no luck. Or maybe some luck but not sufficient luck :p

I can get into the "Boot Environments" menu, and I do have a whole bunch of snapshots listed there. I selected the p8 snapshot from yesterday, and hit return. Same issue occurred.

I'm not sure if the advisories for the p7 to p8 update (which was pretty recent) said to reboot or not, so I guess it's possible that the problem actually started in p7. I'm a little reluctant to try booting into p7, as I don't yet confidently understand exactly what this "Boot Environments" thing entails, and I'm a bit worried that maybe something else that I changed in the meantime will be missing from the snapshot. I'm going to get some lunch and investigate further before proceeding.
 
You must log in or register to reply here.
Back
Top