Bug 230501 - EFI loader fails with "panic: free: guard1 fail" when booting
Summary: EFI loader fails with "panic: free: guard1 fail" when booting
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 11.2-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-10 11:53 UTC by Ka Ho Ng
Modified: 2019-05-23 08:30 UTC (History)
7 users (show)

See Also:


Attachments
Photo taken during booting (206.89 KB, image/jpeg)
2018-08-10 11:53 UTC, Ka Ho Ng
no flags Details
output of dmidecode (26.98 KB, text/plain)
2018-08-10 11:54 UTC, Ka Ho Ng
no flags Details
Photo taken during booting into FreeBSD12-alpha3 memstick (220.27 KB, image/jpeg)
2018-08-26 17:29 UTC, Ka Ho Ng
no flags Details
"panic: free: guard1 fail" on Lenovo Thinkpad X230i (485.68 KB, image/png)
2019-03-02 15:37 UTC, Stéphane Rochoy
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ka Ho Ng 2018-08-10 11:53:23 UTC
Created attachment 196056 [details]
Photo taken during booting
Comment 1 Ka Ho Ng 2018-08-10 11:54:33 UTC
Created attachment 196057 [details]
output of dmidecode
Comment 2 Kyle Evans freebsd_committer 2018-08-10 22:34:11 UTC
Hi,

I see this is with 11.2- can you please try booting one of the head snapshots and see if this is still reproducible there? A number of improvements went into the loader.efi that hadn't necessarily stabilized in time for 11.2.

Thanks,

Kyle Evans
Comment 3 Doug Kirk 2018-08-25 02:38:35 UTC
I have also hit this issue with FreeBSD12-ALPHA3, booting the installer from the memstick image. SHA256 checksum verified ok.

Computer is an unjailed Chromebox with UEFI BIOS, Intel Celeron 2955U, specs here: https://www.cnet.com/products/asus-chromebox/specs/ . Difference to specs is memory upgraded to 8GB.
Comment 4 Ka Ho Ng 2018-08-26 17:27:36 UTC
(In reply to Kyle Evans from comment #2)

Unfortunately trying to boot into FreeBSD12-ALPHA3 memstick (with loader.efi instead) still throw out free guard violation.
Comment 5 Ka Ho Ng 2018-08-26 17:29:30 UTC
Created attachment 196574 [details]
Photo taken during booting into FreeBSD12-alpha3 memstick
Comment 6 Stéphane Rochoy 2019-03-02 15:31:38 UTC
Same problem when trying to boot 12.0/amd64 (from USB) on Lenovo Thinkpad X230i.
Comment 7 Stéphane Rochoy 2019-03-02 15:37:28 UTC
Created attachment 202504 [details]
"panic: free: guard1 fail" on Lenovo Thinkpad X230i
Comment 8 Andrew Smith 2019-04-02 02:20:16 UTC
I ran into this as well on a few machines that had CloudReady's distribution of Chrome OS when attempting to install FreeBSD 12.0-RELEASE.

"panic: free: guard1 fail @ 0x59121580 from unknown:0"

I was able to get around this issue by zeroing the disk from a Linux recovery image before installing FreeBSD. There were quite a number of partitions (mid-20s?) present when I examined it with gdisk.
Comment 9 Michael 2019-05-21 22:00:23 UTC
I'm unable to boot from USB on an Acer C720 flashed with UEFI-only firmware:

Shell> fs0:
FS0:\efi\boot\> bootx64.efi
Consoles: EFI console
panic: free: guard1 fail @ 0x728f0d60 from unknown:0
--> Press a key on the console to reboot <--
Comment 10 Michael 2019-05-22 00:04:04 UTC
I don't understand what was going wrong, but here is a description of the workaround I found for anyone else in a similar situation.

The "memstick" image for FreeBSD 13 are able to boot on an Acer C720 with mrchromebook's UEFI firmware whereas the FreeBSD 12 memstick image is not. Both contain 2 partitions. The first is an EFI partition, and the second is the installation media. It's possible to overwrite the contents of the FreeBSD 13 image's 2nd partition with the FreeBSD 12 image's 2nd partition, and then use that to install FreeBSD 12.
Comment 11 Ka Ho Ng 2019-05-23 08:30:00 UTC
(In reply to Andrew Smith from comment #8)
I confirm that this works for me, although I currently have no idea
what's inside an seemingly empty
drive that was used as a data drive with Linux filesystems on it can
upset the UEFI booting process...