Bug 214261 - [uefi] boostrap hangs
Summary: [uefi] boostrap hangs
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 11.0-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2016-11-06 08:26 UTC by emz
Modified: 2020-09-14 15:38 UTC (History)
2 users (show)

See Also:

hangup screen (37.86 KB, image/jpeg)
2016-11-06 08:26 UTC, emz
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description emz 2016-11-06 08:26:33 UTC
Created attachment 176675 [details]
hangup screen

FreeBSD 11.0-RELEASE-p2, generic kernel, Supermicro server (X9SCL-F MB) with a recent BIOS (v2.2). See the attached screen for details. 100% reproducible. Boots fine from GPT/MBR. Isn't affected by the hw.vga.textmode.

Furthermore, I cannot make it boot automatically, see my message in the stable@ for details - https://lists.freebsd.org/pipermail/freebsd-stable/2016-August/085280.html:

"Recently I've installed FreeBSD 10.3 as an experiment to get the 
UEFI-enabled system, on one of mine Supermicro servers. The installer 
worked just fine, but after insttallation I got myself a problem: it 
cannot boot. If I select to boot the old way, froma disk, BIOS says 
there's no valid boot device, and I guess i'ts as intended. When I 
select to boot to the UEFI shell, I got a listing of valid boot deviced 
identificators, and then an error:


'f??('is not recognized as an internal or external command, operable 
program or batch file

Exit status code: Invalid parameter


and the booting process bails to the shell itself.

When I enter





FreeBSD boots just fine, but I would rather see it boots automatically."

as the final attempt to resolve this I've upgraded the installed system to 11.0-p2 (nothing changed) and upgraded it's BIOS from 2.0b to 2.2 (got this hangup problem). I'm not entirely sure who's problem is that, but FreeBSD totally lacks any documentation about installing UEFI loaders, so at least this is worth attention. Still both problems can be caused by the FreeBSD UEFI support.

Workaround: change to the legacy GPT/MBR bootstrap scheme.
Comment 1 Kyle Evans freebsd_committer 2018-04-22 00:59:39 UTC

Can you please see if this is still an issue with the latest 11.1-STABLE snapshots? A lot of bootloader improvements have been made since this PR was created.