linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jurriaan <thunder7@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: cutting down on boot messages
Date: Fri, 25 Jul 2003 21:57:52 +0200	[thread overview]
Message-ID: <20030725195752.GA8107@middle.of.nowhere> (raw)

If I boot my system, there are copious messages. 

For example:

md: Autodetecting RAID arrays.
md: autorun ...
md: considering hdc6 ...
md:  adding hdc6 ...
md: hdc5 has different UUID to hdc6
md: hdc3 has different UUID to hdc6
md: hdc1 has different UUID to hdc6
md:  adding hda6 ...
md: hda5 has different UUID to hdc6
md: hda3 has different UUID to hdc6
md: hda1 has different UUID to hdc6
md: hdi2 has different UUID to hdc6
md: hdi1 has different UUID to hdc6
md: hde2 has different UUID to hdc6
md: hde1 has different UUID to hdc6
md: created md5
md: bind<hda6>
md: bind<hdc6>
md: running: <hdc6><hda6>
md5: setting max_sectors to 128, segment boundary to 32767
raid1: raid set md5 active with 2 out of 2 mirrors

Now these messages are often uninteresting - but sometimes they are.
So just deleting them, or requiring a recompile or reboot is not good
enough.
Also, I noted that these messages were almost always grouped together.

Suppose these messages were removed from the normal output, but instead
stored in a buffer in the kernel.

Then, you could do

dmesg.raid

to get at the raid-messages,

and 

dmesg.raid --clear 

to clear the buffer.

The same goes for other groups of messages, like the whole APIC/IRQ
routing block, ide messages, usb messages etc.

Would this keep the interesting information, but cut down on the amount
of messages? I'm now at 22k of dmesg, including raid, usb, apic etc, for
a single CPU system.

I'd be interested in everyone's opinion on this!

Jurriaan
-- 
REAL LIFE MANAGEMENT 'DILBERT QUOTATIONS':
11: One day my Boss asked me to submit a status report to him concerning a
    project I was working on. I asked him if tomorrow would be soon
    enough. He said "If I wanted it tomorrow, I would have waited until
    tomorrow to ask for it!" (New business manager, Hallmark Greeting
    Cards.)
Debian (Unstable) GNU/Linux 2.6.0-test1-ac2 4112 bogomips load av: 1.00 1.00 1.00

             reply	other threads:[~2003-07-25 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 19:57 Jurriaan [this message]
2003-07-25 20:04 ` Mike Fedyk
2003-07-25 21:09   ` Krzysztof Halasa
2003-07-25 21:43 ` Kurt Wall

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=20030725195752.GA8107@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: cutting down on boot messages' \
    /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

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).