Date: Mon, 5 Dec 2016 21:43:03 +0800 From: Ben Woods <woodsb02@gmail.com> To: Eric McCorkle <eric@metricspace.net> Cc: freebsd-hackers@freebsd.org Subject: Re: CFT EFI Boot Refactoring Message-ID: <CAOc73CCgFsPO6DOsM=jx4T04h=8DnTtH%2B0KOzOa-qT9nb_3Pog@mail.gmail.com> In-Reply-To: <ae806c20-4cf7-4c6b-d18a-6e7a4d21bee9@metricspace.net> References: <d3aad5ef-2d6c-3d79-0fe8-91ee086ed2f8@metricspace.net> <CAOc73CAV5tXa%2BG%2BHfDS5DX-pytwg4XZ7PUSKw4haQ3=0Z=HO%2BQ@mail.gmail.com> <c1ed3afc-fe28-a1e4-743e-4750bf200400@metricspace.net> <CAOc73CBo9apCsHkL41izakpizVzgH4QOoyX2o9CkNt3%2BOMt2GQ@mail.gmail.com> <675cb468-f599-a31b-a82c-c0f892136cfc@metricspace.net> <CAOc73CD69QzYCpYbW5ONd11fnMc9fKnLowX0NdE2fPTr7a4CTQ@mail.gmail.com> <ae806c20-4cf7-4c6b-d18a-6e7a4d21bee9@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 December 2016 at 10:59, Eric McCorkle <eric@metricspace.net> wrote:
> You don't have a UFS filesystem anywhere, so we can rule that out. It
> might be tsoome's bug, and it might just be that the bug is sporadic,
> which would explain why I'm not seeing it on my setup with a dosfs.
>
> The only other obvious commonality between you and tsoome that doesn't
> overlap my setup is multiple ZFS datasets, or ZFS data vdevs (mirrors,
> stripes, etc) spread across multiple disks (my setup only has a log and
> a cache on the ssd).
>
>
> Here's what I'll do. I'll create an "extra_logging" branch off of
> efize_new in my github repo, wherein I'll add a bunch of extra logging
> into the detection process. It ought to be enough to print out device
> paths and filesystem drivers just before it tries them.
Ok, I have tested with the extra_logging branch, and can report that the
text on the screen at the time of the hang was:
>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: FS BackendProbing all handles for ZFS
Done
Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85bff18
Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85bfc18
Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85bf998
Probing all filesystems
Probing dosfs
_
Following that, I tried a combination of the old (unmodified) BOOTX64.EFI
with the new (modified) files in /boot/.
This produced the following output on the screen before it also hung:
>> FreeBSD EFI boot block
Loader path: /boot/loader.efi
Initializing modules: ZFS UFS
Probing 10 block devices............* done
ZFS found the following pools: zroot
UFS found no paritions
Consoles: EFI console
Probing all handles for ZFS
Done
Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85c9718
Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85c9418
Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85c9198
Probing all filesystems
Probing dosfs
_
Hope this is helpful for debugging this issue. Note that once again I did
NOT run any command to update my freebsd-boot partition (such as gpart
bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada1). Is this required?
Regards,
Ben
--
From: Benjamin Woods
woodsb02@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOc73CCgFsPO6DOsM=jx4T04h=8DnTtH%2B0KOzOa-qT9nb_3Pog>