Date: Mon, 29 Sep 2014 14:25:56 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: dmesg seems broken Message-ID: <5429A434.5040008@freebsd.org> In-Reply-To: <13dd6d3eab3735353f5309a223dc1799.authenticated@ultimatedns.net> References: <fd2e300a969481d394963d459536b5ba.authenticated@ultimatedns.net> <CAKFCL4Wr3OygqhkXPpb=VJdKZgfWSVARzpmumwcx-8J6bNDXQA@mail.gmail.com> <f1a6c55c641e1d559559b28735251e50.authenticated@ultimatedns.net> <54298AEB.9070700@freebsd.org> <13dd6d3eab3735353f5309a223dc1799.authenticated@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014-09-29 14:22, Chris H wrote: >> On 09/29/2014 10:31, Chris H wrote: >>>> 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" >>>> >>> >>> _______________________________________________ >>> 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" >>> >> >> Try adding the sysctl to your loader.conf so it is set earlier > Thank you for the reply, Allan. > I bumped kern.msgbufsize quite a bit within loader.conf. That's how I > discovered that that tunable worked. But then needed to eek it down, > until I found the actual top of the output -- had to bounce the box > quite a few times. :P > >> >> I don't think the size was reduced, you may just have a lot of messages. > ODD. Because running RELENG_8, or 11-CURRENT on the same hardware, and yes, > with BOOT_VERBOSE && VERBOSE_LOADING. I received the entire buffer. > > Thanks again, Allan. > > --Chris > >> >> -- >> Allan Jude Do you actually see a difference in the size of kern.msgbufsize between RELENG_8 and the RELENG_9 box that is exhibiting issues? -- Allan Jude
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5429A434.5040008>