Date: Thu, 9 Aug 2018 11:29:04 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Johannes Lundberg <johalun0@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Early kernel boot log? Message-ID: <20180809082904.GI1884@kib.kiev.ua> In-Reply-To: <CAECmPwuJELN%2BL05z1a36DZd5FKCC=kRNS7swCjuqdA2uGPMpRA@mail.gmail.com> References: <CAECmPwuJELN%2BL05z1a36DZd5FKCC=kRNS7swCjuqdA2uGPMpRA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 09, 2018 at 08:54:31AM +0100, Johannes Lundberg wrote: > Hi > > So I believe the reason I'm not seeing and printf output in dmesg is that > it is too early in some functions. > For example > machdep.s > getmemsize() > add_efi_map_entries() > etc > > However, these functions do contain debug printf statements so if they're > logging to somewhere, where/how can I see this? > > I also tried booting in bhyve too see if I could get any output via serial > console but nothing there either. Disable efi console, only leaving comconsole around, then set debug.late_console=0 in loader. > > printfs in cpu_startup() does give me output in dmesg. > > Cheers > _______________________________________________ > 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?20180809082904.GI1884>