Date: Sat, 29 Sep 2018 23:06:12 -0600 From: Warner Losh <imp@bsdimp.com> To: Yuri <yuri@rawbw.com> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: UEFI Loader problems in CURRENT Message-ID: <CANCZdfoyqJGz5u7n6CfLx1iYMjdjq9za9M=WT2UzprgRf5bkoA@mail.gmail.com> In-Reply-To: <CANCZdfqirb%2BQ7X209BPNOswN7%2BbveY-z816VsTDYW6uKfrTh4g@mail.gmail.com> References: <8e1102e9-4327-2268-6370-f81231ba0d1a@rawbw.com> <CANCZdfqirb%2BQ7X209BPNOswN7%2BbveY-z816VsTDYW6uKfrTh4g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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@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@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoyqJGz5u7n6CfLx1iYMjdjq9za9M=WT2UzprgRf5bkoA>