On Mon, 18 Jan 2016 12:04:38 +0000 Steven Hartland <ste...@multiplay.co.uk> wrote:
> On 18/01/2016 11:34, Andrew Turner wrote: > > On Mon, 18 Jan 2016 09:10:33 +0100 > > Dimitry Andric <d...@freebsd.org> wrote: > > > >> On 18 Jan 2016, at 07:20, O. Hartmann <ohart...@zedat.fu-berlin.de> > >> wrote: > >>> Building NanoBSD images booting off from USB Flash drives and > >>> having two GPT partitions, booting is stuck in the UEFI loader, > >>> presenting me with something like: > >>> > >>> [...] > >>> Probing 6 block devices.....++. done > >>> > >>> ZFS found no pools > >>> UFS found 2 partitions > >>> > >>> And further nothing happens. A RESET is only possible by a > >>> hardreset - it seems the system is crashed/stuck/frozen or > >>> something similar. > >>> > >>> The last images working run r293654. The issue occurs with > >>> r294248. > >>> > >>> Any suggestions possible? Did I miss something? > >> Looks to me like fallout from the recent modularisation in r294060, > >> and/or ZFS support in r294068. Steven, any clue? > >> > >> -Dimitry > >> > > I found the same issue while working on nanobsd. I'm not sure it's > > due to the recent ZFS changes as I reverted them, but found boot1 > > still failed to load loader.efi. > > > Can you update to > r294265 and test with EFI_DEBUG defined e.g. > make buildenv -DEFI_DEBUG > cd sys/boot/efi/boot1 > make clean > make > > Then install the new boot1.efifat to your efi partition. > > Hopefully this will give some more information on what the problem > may be. the issue was we were caching reads from the first filesystem we looked at. I've committed the fix in r294291 to force the code to re-read on each filesystem it looks at. Andrew _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
