From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: David Ford <david@linux.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c
Date: Sat, 27 Jan 2001 02:14:00 -0800 [thread overview]
Message-ID: <200101271014.f0RAE0G04370@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <cs.lists.linux-kernel/3A72804A.E6052E1B@linux.com>
On Sat, 27 Jan 2001 08:01:14 +0000, David Ford <david@linux.com> wrote:
> Does Linus or anyone object to raising the ksmg buffer from 16K to 32K?
> 4/5 systems I have now overflow the buffer during boot before init is
> even launched.
Hmm, are you sure? man dmesg:
[...]
-sbufsize
use a buffer of bufsize to query the kernel ring
buffer. This is 8196 by default (this matches the
default kernel syslog buffer size in 2.0.33 and
2.1.103). If you have set the kernel buffer to
larger than the default then this option can be
used to view the entire buffer.
So try dmesg -s 16384. That's good enough for me on a 4-way SMP
box with lots of SCSI on-board (and trust me, SMP generates a *huge*
amount of kernel logging).
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2001-01-27 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cs.lists.linux-kernel/3A72804A.E6052E1B@linux.com>
2001-01-27 10:14 ` Ion Badulescu [this message]
2001-01-27 11:45 ` [PATCH/REQ] Increase kmsg buffer from 16K to 32K, kernel/printk.c David Ford
2001-02-01 1:26 Chris Adams
-- strict thread matches above, loose matches on Subject: below --
2001-01-27 8:01 David Ford
2001-01-31 17:06 ` Alan Cox
2001-01-31 17:19 ` Maciej W. Rozycki
2001-01-31 23:12 ` David Ford
2001-01-31 17:21 ` Gabor Lenart
2001-01-31 20:46 ` Rik van Riel
2001-01-31 20:58 ` Mark Hahn
2001-02-03 19:41 ` Paul Gortmaker
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=200101271014.f0RAE0G04370@moisil.dev.hydraweb.com \
--to=ionut@moisil.cs.columbia.edu \
--cc=david@linux.com \
--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