From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: increased verbosity in dmesg
Date: Sat, 16 Aug 2003 04:38:59 -0400 [thread overview]
Message-ID: <200308160438.59489.gene.heskett@verizon.net> (raw)
Greetings;
The recently increased verbosity in the dmesg file is causeing the
"ring buffer" to overflow, and I am not now seeing the first few
pages of the reboot in the dmesg file.
I understand this 'ring' buffer has been expanded to about 16k but
that was way back in 2.1 days when that occured according to the
Documentation.
Is there any quick and dirty way to increase this to at least 32k, or
maybe even to 64k? With half a gig of memory, this shouldn't be a
problem should it?
I've done some grepping, but it appears I'm not grepping for the right
var name, so I'm coming up blank and need some help.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
next reply other threads:[~2003-08-16 8:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 8:38 Gene Heskett [this message]
2003-08-16 10:48 ` increased verbosity in dmesg Martin Schlemmer
2003-08-16 12:51 ` Arkadiusz Miskiewicz
2003-08-16 15:07 ` Gene Heskett
2003-08-26 0:17 ` parport_pc Oops with 2.6.0-test3 Christian Kujau
2003-08-26 8:38 ` Andrew Morton
2003-08-26 23:03 ` Christian
2003-08-28 2:41 ` Christian Kujau
2003-08-16 11:02 ` increased verbosity in dmesg Felipe Alfaro Solana
2003-08-16 15:36 ` Gene Heskett
2003-08-16 15:45 ` Felipe Alfaro Solana
2003-08-16 16:01 ` Gene Heskett
2003-08-16 16:24 ` Felipe Alfaro Solana
2003-08-16 17:41 ` Randy.Dunlap
2003-08-16 17:57 ` Gene Heskett
2003-08-16 17:18 ` Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308160438.59489.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).