Date: Mon, 18 Jan 2016 14:08:58 -0500 From: Ed Maste <emaste@freebsd.org> To: Dimitry Andric <dim@freebsd.org> Cc: "O. Hartmann" <ohartman@zedat.fu-berlin.de>, Steven Hartland <smh@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: r294248: boot stuck: EFI loader doesn't proceed Message-ID: <CAPyFy2D1aeoB7x4NXao9hg=jj2c%2B-07zidaEwMAd-jdj6g7=HQ@mail.gmail.com> In-Reply-To: <596CBFC9-275C-445F-9D2B-23B90DB9966A@FreeBSD.org> References: <20160118072000.4a03a4d2@freyja.zeit4.iv.bundesimmobilien.de> <596CBFC9-275C-445F-9D2B-23B90DB9966A@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 January 2016 at 03:10, Dimitry Andric <dim@freebsd.org> wrote: > On 18 Jan 2016, at 07:20, O. Hartmann <ohartman@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? In QEMU boot1 failed for me with "Failed start image provided by UFS", and I can confirm that it's fixed by reverting those two commits.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2D1aeoB7x4NXao9hg=jj2c%2B-07zidaEwMAd-jdj6g7=HQ>