From: Gene Heskett <gene.heskett@verizon.net>
To: Martin Schlemmer <azarah@gentoo.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: increased verbosity in dmesg
Date: Sat, 16 Aug 2003 11:07:21 -0400 [thread overview]
Message-ID: <200308161107.21430.gene.heskett@verizon.net> (raw)
In-Reply-To: <1061030883.13257.253.camel@workshop.saharacpt.lan>
On Saturday 16 August 2003 06:48, Martin Schlemmer wrote:
>On Sat, 2003-08-16 at 10:38, Gene Heskett wrote:
>> 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.
>>
>>
>> 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
>
>Works here.
Doesn't here. Example:
[root@coyote root]# dmesg -s 30000 >/tmp/dmesg;ls -l /tmp/dmesg
-rw-r--r-- 1 root root 15496 Aug 16 10:57 /tmp/dmesg
And actually starts up in the middle of the usb stuffs because of the
size limitation.
Here is a head of the file itself after this last boot.
: registered new driver usbdevfs
usb.c: registered new driver hub
host/usb-uhci.c: $Revision: 1.275 $ time 13:51:40 Aug 15 2003
host/usb-uhci.c: High bandwidth mode enabled
host/usb-uhci.c: USB UHCI at I/O 0xdc00, IRQ 9
host/usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
etc, etc
Besides, used that way its a read option, and I'm asking about the
size of the ring being used during the boot for message storage
before any drives are mounted in writable modes. Its many kilobytes
insufficient, and because of pointer wrap, being overwritten before
the syslog is up and running, and the file 'dmesg' itself is actually
written to non-volatile storage.
Adjusting this is not an 'after boot' operation as above, but a
src-code setting buried in the kernel code someplace. I have NDI how
interlocked it is with everything else, which is why I was hopeing
someone could point me and pull the trigger.
--
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 prev parent reply other threads:[~2003-08-16 15:07 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
2003-08-16 15:07 ` Gene Heskett [this message]
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=200308161107.21430.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=azarah@gentoo.org \
--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).