From: Mike Fedyk <mfedyk@matchmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Increasing dmesg buffer size?
Date: Mon, 1 Oct 2001 16:50:53 -0700 [thread overview]
Message-ID: <20011001165053.A4836@mikef-linux.matchmail.com> (raw)
In-Reply-To: <3BB90039.E551000C@home.com>
In-Reply-To: <3BB90039.E551000C@home.com>
On Mon, Oct 01, 2001 at 06:46:01PM -0500, Jordan Breeding wrote:
> What kernel parameter do I need to modify in the source to allow a
> larger dmesg buffer? I have a lot of boot messages and I currently
> loose about 10-20 lines immediately and they can not even be seen in
> /var/log/dmesg because that file gets dumped after those lines are
> already gone. Thanks to anyone who can help.
>
Does dmesg wrap around before klogd can grab the info? Check
/var/log/kern.log (in debian, your filename may vary...) to see...
Mike
next prev parent reply other threads:[~2001-10-01 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 23:46 Increasing dmesg buffer size? Jordan Breeding
2001-10-01 23:48 ` Randy.Dunlap
2001-10-01 23:50 ` Mike Fedyk [this message]
2001-10-01 23:55 ` James Simmons
2001-10-02 1:14 ` Tim Moore
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=20011001165053.A4836@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.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