Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Mar 1999 11:32:45 +1030
From:      Greg Lehey <grog@lemis.com>
To:        Karl Pielorz <kpielorz@caladan.tdx.co.uk>, Tom Torrance at home <tom@tomqnx.com>
Cc:        questions@FreeBSD.ORG
Subject:   Re: DMESG anomaly
Message-ID:  <19990302113245.N441@lemis.com>
In-Reply-To: <Pine.BSF.4.05.9903020028010.40130-100000@caladan.tdx.co.uk>; from Karl Pielorz on Tue, Mar 02, 1999 at 12:31:04AM %2B0000
References:  <m10Hb3U-000I1kC@TomQNX.tomqnx.com> <Pine.BSF.4.05.9903020028010.40130-100000@caladan.tdx.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday,  2 March 1999 at  0:31:04 +0000, Karl Pielorz wrote:
>
> On Mon, 1 Mar 1999, Tom Torrance at home wrote:
>
>> Does anyone have a clue why dmesg only gives me a truncated
>> response (top chopped off) under RELEASE-3.1?
>> It did the same thing under RELENG_3 on the same machine.
>>
>> Please do a group reply...
>
> If you have a machine that has a lot of hardware in it, or spews out a lot
> of kernel output during/after boot - the dmesg output can overflow it's
> buffer... There might be a setting for this when you compile the kernel -
> I'm not sure... :(

Yes, there is:

  options		"MSGBUF_SIZE=32768"	# big msgbuf

This is what I have in my kernel config file.  You'll need it if you
want to get all of a verbose boot, for example.

Greg
--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990302113245.N441>