Date: Mon, 29 Sep 2014 07:31:24 -0700 (PDT) From: "Chris H" <bsd-lists@bsdforge.com> To: "Brandon Allbery" <allbery.b@gmail.com> Cc: freebsd current <freebsd-current@freebsd.org>, freebsd stable <freebsd-stable@freebsd.org>, freebsd amd64 <freebsd-amd64@freebsd.org> Subject: Re: dmesg seems broken Message-ID: <f1a6c55c641e1d559559b28735251e50.authenticated@ultimatedns.net> In-Reply-To: <CAKFCL4Wr3OygqhkXPpb=VJdKZgfWSVARzpmumwcx-8J6bNDXQA@mail.gmail.com> References: <fd2e300a969481d394963d459536b5ba.authenticated@ultimatedns.net> <CAKFCL4Wr3OygqhkXPpb=VJdKZgfWSVARzpmumwcx-8J6bNDXQA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sat, Sep 27, 2014 at 7:22 PM, Chris H <bsd-lists@bsdforge.com> wrote: > >> Where can I get that information? Where was it sent? Why am I >> not allowed to view it? >> > > Sounds to me like the kernel ring buffer is now too small for all the early > boot messages? OK more investigation indicates that bumping kern.msgbufsize will return the missing bits. Maybe this is what you were trying to tell me. ;) Anyway. Anyone know why was this tunable reduced? I don't experience this on RELENG_8, or 11-CURRENT. FWIW I have loader.conf(5) set to boot verbose. But still didn't get the info expected. :( Thanks for the reply, Brandon. --Chris > > -- > brandon s allbery kf8nh sine nomine associates > allbery.b@gmail.com ballbery@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://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?f1a6c55c641e1d559559b28735251e50.authenticated>