Date: Sat, 3 Dec 2016 21:59:00 -0500 From: Eric McCorkle <eric@metricspace.net> To: Ben Woods <woodsb02@gmail.com> Cc: freebsd-hackers@FreeBSD.org Subject: Re: CFT EFI Boot Refactoring Message-ID: <ae806c20-4cf7-4c6b-d18a-6e7a4d21bee9@metricspace.net> In-Reply-To: <CAOc73CD69QzYCpYbW5ONd11fnMc9fKnLowX0NdE2fPTr7a4CTQ@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --arQd7PRswDidkEC78EiEHoTv6NEWfSimg Content-Type: multipart/mixed; boundary="Pi0td10lcdGV92dIcHJvWDKh4mWPcrDfu"; protected-headers="v1" From: Eric McCorkle <eric@metricspace.net> To: Ben Woods <woodsb02@gmail.com> Cc: freebsd-hackers@FreeBSD.org Message-ID: <ae806c20-4cf7-4c6b-d18a-6e7a4d21bee9@metricspace.net> Subject: Re: CFT EFI Boot Refactoring References: <d3aad5ef-2d6c-3d79-0fe8-91ee086ed2f8@metricspace.net> <CAOc73CAV5tXa+G+HfDS5DX-pytwg4XZ7PUSKw4haQ3=0Z=HO+Q@mail.gmail.com> <c1ed3afc-fe28-a1e4-743e-4750bf200400@metricspace.net> <CAOc73CBo9apCsHkL41izakpizVzgH4QOoyX2o9CkNt3+OMt2GQ@mail.gmail.com> <675cb468-f599-a31b-a82c-c0f892136cfc@metricspace.net> <CAOc73CD69QzYCpYbW5ONd11fnMc9fKnLowX0NdE2fPTr7a4CTQ@mail.gmail.com> In-Reply-To: <CAOc73CD69QzYCpYbW5ONd11fnMc9fKnLowX0NdE2fPTr7a4CTQ@mail.gmail.com> --Pi0td10lcdGV92dIcHJvWDKh4mWPcrDfu Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable (Re-adding -hackers, to document the diagnosis) You're freezing at the same point as where tsoome saw it freeze. Basically, what's happening at that point in the code is it's probing all device handles, trying to attach filesystem drivers. Hanging here means that it's crashing somewhere in that process. The boot loader is going to hit every single partition and try all the filesystem drivers until one works. It will bail on the ESP, since that will have an EFI_SIMPLE_FILESYSTEM_PROTOCOL driver courtesy of the EFI firmware. Here's the diagnostic information I have so far: * My setup is a positive example (works): two disks, disk 1 has ESP and freebsd-zfs, disk 2 has a partition that's held both an msdosfs and a UFS (it was originally a swap partition that I've been creating various filesystems on to test the boot process), a zfs intent log, and a zfs l2arc cache. All ZFS stuff is part of the same pool, which holds the root fs. * Your setup is a negative example (fails). * tsoome's setup is also a negative example: "The VM has 4 disks, illumos mirror zfs on first 2, third has fbsd, 4th (for this test) has EFI system partition, and zfs and ufs partitions, zfs partition has bootfs with /boot directory." 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. On 12/03/2016 21:06, Ben Woods wrote: > Hi Eric, >=20 > That is correct. Each drive has an EFI partition, which uses msdosfs. M= y > FreeBSD drive does not have a UFS partition, as I solely use ZFS on roo= t. >=20 > One thing to note is that in the process of testing your efize_new, I > did not touch my freebsd-boot partition, and I am not even sure if it i= s > being used by the loader. My /boot lives in my ZFS zroot partition, and= > freebsd-boot is not mounted in anyway. Could this have an impact on the= > testing? >=20 > Regards, > Ben >=20 > -- > From: Benjamin Woods > woodsb02@gmail.com <mailto:woodsb02@gmail.com> >=20 > On 4 December 2016 at 06:06, Eric McCorkle <eric@metricspace.net > <mailto:eric@metricspace.net>> wrote: >=20 > So, you have no UFS partitions, but you do have an MSDOSFS partitio= n on > each drive? >=20 > If so, that lends support to tsoome's suspicion that it may be a bu= g > he's working on. >=20 --Pi0td10lcdGV92dIcHJvWDKh4mWPcrDfu-- --arQd7PRswDidkEC78EiEHoTv6NEWfSimg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iF4EARYIAAYFAlhDhnQACgkQVsKIQKqABI3z/wEA4e19ke22SBFsjW9/MfQiPqjK 603q38nV9BwYw3jcHNwA/0yIXrqQvxflkqbWa38VOzHMcL+Gsu8p+Zo/IID2bcsB =GjBu -----END PGP SIGNATURE----- --arQd7PRswDidkEC78EiEHoTv6NEWfSimg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ae806c20-4cf7-4c6b-d18a-6e7a4d21bee9>