From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: Martin Schlemmer <azarah@gentoo.org>, gene.heskett@verizon.net
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: increased verbosity in dmesg
Date: Sat, 16 Aug 2003 14:51:44 +0200 [thread overview]
Message-ID: <200308161451.44398.arekm@pld-linux.org> (raw)
In-Reply-To: <1061030883.13257.253.camel@workshop.saharacpt.lan>
> > 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?
>
> # dmesg -s 30000
Hmm, that would mean that bufer in kernel is different than 16kb which is not
true on UP x86 machines:
if defined(CONFIG_MULTIQUAD) || defined(CONFIG_IA64)
#define LOG_BUF_LEN (65536)
#elif defined(CONFIG_ARCH_S390)
#define LOG_BUF_LEN (131072)
#elif defined(CONFIG_SMP)
#define LOG_BUF_LEN (32768)
#else
#define LOG_BUF_LEN (16384) /* This must be a power of two
*/
#endif
USB messages are filling whole buffer for me on my UP x86 machine so I don't
see any messages before usb after fresh boot :(
Maybe this value should be increased in kernel to 32768 on UP, too?
> Works here.
--
Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology
arekm@sse.pl AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PLD/Linux
next prev parent reply other threads:[~2003-08-16 12:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 8:38 increased verbosity in dmesg Gene Heskett
2003-08-16 10:48 ` Martin Schlemmer
2003-08-16 12:51 ` Arkadiusz Miskiewicz [this message]
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=200308161451.44398.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=azarah@gentoo.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.