Bug 233211 - 11.2-RELEASE freezes Gigabyte motherboard
Summary: 11.2-RELEASE freezes Gigabyte motherboard
Status: In Progress
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 11.2-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: Rebecca Cran
URL:
Keywords: crash, easy, install, standards
Depends on:
Blocks:
 
Reported: 2018-11-13 22:15 UTC by Rodrigo N. Hernandez
Modified: 2018-11-24 17:00 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rodrigo N. Hernandez freebsd_triage 2018-11-13 22:15:15 UTC
OVERVIEW:
FreeBSD-11.2-RELEASE-amd64-memstick.img causes computer to freeze until rearranging installation media MBR and partition alignment on Gygabyte motherboard GA-G41M-ES2L

STEPS TO REPRODUCE:
Using various USB sticks with various different BIOS configurations (USB 1.0/2.0 Enable/Disable | Legacy USB Support Enable/Disable etc), tested with 6 different vendor/sizes USB sticks with same result: Computer freezes right after BIOS memory check at initial stages. Same USB sticks works if loaded with different content (e.g. GRUB from other OSes).

STEPS TO FIX THE ISSUE:
It seems that realigning the partitions to MiB boundaries fixed the freezing issue. The original FreeBSD-11.2-RELEASE-amd64-memstick has the EFI partition starting at sector 1, right after MBR data.

The following steps resulted in a fix for the situation:
- Backing up MBR, EFI and BOOT partitions from actual USB stick loaded with the image.
- Wipe USB stick with zeros
- Restore MBR from backup
- Delete actual partitions as pointed in MBR using fdisk on linux
- Recreate the EFI and BOOT partitions using linux fdisk with exact same total sector size as in the original image and same partition ID types
- Restoring EFI and BOOT partition data from backup to the newly created ones

After this procedure the EFI partition starts at sector 2048 and no more at sector 1. Now aligned to MiB as this is a standard in recent linux fdisk program

CONSIDERATIONS:
Although I’m not an expert in the subject what I think is (and I may be wrong on these):
- The EFI partition starting at sector 1 seems like an exotic alignment (or not really aligned to expected usual page sizes)
- Using usual/recommended partition alignment can avoid compatibility issues by avoiding uncommon situations (not tested at product development cycle, e.g. tested only with expected page sizes or even hardware being unable to load very different page sizes from BIOS)
- Sector 1 is expected to be used by GPT in GPT scheme, keeping that space free of use for other purposes seems to be a good call, for compatibility reasons.
Comment 1 Kyle Evans freebsd_committer 2018-11-13 22:25:02 UTC
Tossing it over to bcran@, who is doing things with our ESP creation/usage in general -- https://reviews.freebsd.org/D17947 touches how the release images are generated already, this could probably get worked into if it seems reasonable.
Comment 2 Rebecca Cran freebsd_committer 2018-11-13 22:26:38 UTC
This wouldn't surprise me: I had a motherboard a few years ago that hung at the Intel AHCI/RAID optrom if there was a certain pattern on the disk that Linux had written.

The latest BIOS for the GA-G41M-ES2L is from 2010/06/21 so it's a relatively old board in terms of potential bugs/issues around booting GPT etc.
Comment 3 Rodrigo N. Hernandez freebsd_triage 2018-11-14 01:07:13 UTC
FreeBSD-11.2-RELEASE-amd64-memstick.img is MBR only, no GPT involved, what’s perfectly acceptable for either legacy BIOS or UEFI hardware to function correctly in the case of the boot media. The important aspect is the fact that partitions alignment _should_ respect physical sector size/logical sector size exponential ratio in modern approach, to avoid issues. For example as depicted in ATA8-ACS: “As larger sectors occur, partition alignment becomes an important issue that affects applications that check if the first partition starts on sector 63 (e.g., on a 512-byte sector device, all the partitions should start on an LBA that is aligned with the start of a physical sector on the media, on a 1 024-byte sector device, the partitions should start on an even numbered sector and end on an odd numbered sector, and on a 4 096-byte sector device, the partitions should start on an LBA where the low order three bits are zero).”