If the hung/crash is after printout of bootorder, and the fix (at least in some cases) is about setting the boot device (with linux tools, but I’d assume the efi bootmanager setup would do the same), it means, we do get bad value from efi boot manager variables, and if the fbsd installer and/or boot program update does not include the variable setup, we can not rely on those values in loader. Or, we should have foolproof way to check the values - if we can trust them. Rgds, Toomas > On 30 Sep 2018, at 08:06, Warner Losh <imp_at_bsdimp.com> wrote: > > Having had a few hours to think about things, I'm starting to think that > the loader may be crashing w/o any clue or traceback. I'll look into this > being a possibility. In the past, this has happened because of an untested > error condition and/or assuming pointers were non-NULL. It would be super > swell if there were a cheap to obtain box that exhibits this problem. > > Warner > >> On Sat, Sep 29, 2018 at 6:14 PM Warner Losh <imp_at_bsdimp.com> wrote: >> >> Sadly both of these bugs are thin on detail beyond it doesn't work. Makes >> it hard to even look into it. >> >> Warner >> >>> On Sat, Sep 29, 2018, 6:00 PM Yuri <yuri_at_rawbw.com> wrote: >>> >>> See: >>> >>> * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230090 >>> >>> * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219957 >>> >>> >>> Yuri >>> >>> >>> _______________________________________________ >>> freebsd-current_at_freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org >>> " >>> >> > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Sun Sep 30 2018 - 06:09:40 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:18 UTC