Re: dmesg seems broken

On 09/29/2014 10:31, Chris H wrote:
>> On Sat, Sep 27, 2014 at 7:22 PM, Chris H <bsd-lists_at_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_at_gmail.com                                  ballbery_at_sinenomine.net
>> unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
>> _______________________________________________
>> freebsd-current_at_freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>>
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> 

Try adding the sysctl to your loader.conf so it is set earlier

I don't think the size was reduced, you may just have a lot of messages.

-- 
Allan Jude