From: Arno Wagner <wagner@tik.ee.ethz.ch>
To: Diego Calleja Garc?a <diegocg@teleline.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: 2.6.0-test3: dmesg buffer still too small
Date: Sun, 24 Aug 2003 03:05:39 +0200 [thread overview]
Message-ID: <20030824010539.GA5682@tik.ee.ethz.ch> (raw)
In-Reply-To: <20030823224255.34fee3a0.diegocg@teleline.es>
On Sat, Aug 23, 2003 at 10:42:55PM +0200, Diego Calleja Garc?a wrote:
> El Sat, 23 Aug 2003 17:13:36 +0200 Arno Wagner <wagner@tik.ee.ethz.ch> escribi?:
>
> > b) Add a configuration option to set the buffer size
> > in kernel configuration.
> >
> (15) Kernel log buffer size (16 => 64KB, 17 => 128KB
>
>
> Under "general setup" at least in -test3/4
Not displayed by "make menuconfig" and "make config"
unfortunately.
I found the config variable CONFIG_LOG_BUF_SHIFT
on .config. So this is actually a problem with the config
tools and not the available config variables...
What did you use that displayed the option? Or is there
some other option that hides the choice of log
buffer? I have a stock 2.4.6-test3 from kernel.org
Arno
--
Arno Wagner, Communication Systems Group, ETH Zuerich, wagner@tik.ee.ethz.ch
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
For every complex problem there is an answer that is clear, simple,
and wrong. -- H L Mencken
next prev parent reply other threads:[~2003-08-24 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 15:13 BUG: 2.6.0-test3: dmesg buffer still too small Arno Wagner
2003-08-23 20:42 ` Diego Calleja García
2003-08-24 1:05 ` Arno Wagner [this message]
2003-08-24 1:12 ` Diego Calleja García
2003-08-24 1:33 ` Arno Wagner
-- strict thread matches above, loose matches on Subject: below --
2003-08-24 2:11 Felipe Alfaro Solana
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=20030824010539.GA5682@tik.ee.ethz.ch \
--to=wagner@tik.ee.ethz.ch \
--cc=diegocg@teleline.es \
--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