Date: Mon, 18 Jan 2016 22:46:18 +0000 From: Steven Hartland <steven@multiplay.co.uk> To: Ed Maste <emaste@freebsd.org>, Andrew Turner <andrew@fubar.geek.nz> Cc: Dimitry Andric <dim@freebsd.org>, "O. Hartmann" <ohartman@zedat.fu-berlin.de>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: r294248: boot stuck: EFI loader doesn't proceed Message-ID: <569D6B3A.5090508@multiplay.co.uk> In-Reply-To: <CAPyFy2DwoBjkkZunohKbsLJedfv_qxBL=2m4UGXPumEZ4JXEZA@mail.gmail.com> References: <20160118072000.4a03a4d2@freyja.zeit4.iv.bundesimmobilien.de> <596CBFC9-275C-445F-9D2B-23B90DB9966A@FreeBSD.org> <20160118113411.2a4d3079@zapp> <569CD4D6.50404@freebsd.org> <20160118202642.4f52614b@zapp> <CAPyFy2DwoBjkkZunohKbsLJedfv_qxBL=2m4UGXPumEZ4JXEZA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18/01/2016 21:57, Ed Maste wrote: > On 18 January 2016 at 15:26, Andrew Turner <andrew@fubar.geek.nz> wrote: >> 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. > Thanks Andrew - my QEMU boot failure is not reproducible on a build > from a clean tree with this change included. I still think there are issues in there, specifically the lookup call in try_load, which calls fsread should be getting bad results. I believe the code here https://reviews.freebsd.org/D4989 fixes that as well as eliminating fsstat and all the duplicated code. Regards Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?569D6B3A.5090508>