Date: Sat, 9 Dec 2017 12:58:45 -0700 From: Warner Losh <imp@bsdimp.com> To: Ed Schouten <ed@nuxi.nl> Cc: "O. Hartmann" <ohartmann@walstatt.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: r326734: serial console fails: boot stuck at: Consoles: internal video/keyboard Message-ID: <CANCZdfqsLZggCfet_AX4q-iECH%2BmM3DNr9Zj8S-QkXU%2Bj9NY%2Bg@mail.gmail.com> In-Reply-To: <CABh_MKnFWbLfLXRH19gk2A382ZCOY3wiu=gcQ8ixm4NiAXHRsw@mail.gmail.com> References: <20171209194129.53977a63@thor.intern.walstatt.dynvpn.de> <CABh_MKnFWbLfLXRH19gk2A382ZCOY3wiu=gcQ8ixm4NiAXHRsw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 9, 2017 at 12:04 PM, Ed Schouten <ed@nuxi.nl> wrote: > 2017-12-09 19:41 GMT+01:00 O. Hartmann <ohartmann@walstatt.org>: > > r326734 fails to boot, > > r324234 works fine. > > > > What the heck has changed? > > Could you please try to bisect SVN revisions to figure out which exact > commit causes the problem? > I'd start with r326550. And are your sure it didn't boot / got stuck there, versus the output went someplace crazy because I broke reading in some obscure boot file accidentally :) Also, UEFI or BIOS boot? Any of ZFS, GELI or GPT vs MBR in play? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqsLZggCfet_AX4q-iECH%2BmM3DNr9Zj8S-QkXU%2Bj9NY%2Bg>