dmesg seems broken

[Adam McDougall]

On 09/27/2014 19:29, 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?
> Odd. I'm only using GENERIC modified to not contain any
> hardware I'm not using. I've made zero changes to alter
> buffer(s).
> As I also mentioned; this too was the case from GENERIC
> that came on the install media.
> 
> 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-stable at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>>
> 
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> 

Increase kern.msgbufsize in /boot/loader.conf or MSGBUF_SIZE in your
kernel config.  Were you booting with -v or did the standard dmesg
content just grow too large?