public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let LOG_BUF_SHIFT default to 17
Date: Tue, 29 Jan 2008 09:36:07 +0200	[thread overview]
Message-ID: <20080129073607.GO8767@does.not.exist> (raw)
In-Reply-To: <p73fxwh6sx7.fsf@bingen.suse.de>

On Tue, Jan 29, 2008 at 07:35:00AM +0100, Andi Kleen wrote:
> Adrian Bunk <bunk@kernel.org> writes:
> 
> > 16 kB is often no longer enough for a normal boot of an UP system.
> 
> Better would be to just disable by default/remove noisy messages
> to make the kernel boot output shorter.
> 
> I think we got a lot of IMHO useless messages in there.

Nearly 25% of the messages in my dmesg come from ACPI.

Plus many other messages that cover these generic resources stuff (e.g. 
BIOS map or ioport/iomem reservations).

All of these tend to be of great help when debugging driver regressions, 
since diff'ing the dmesg's often is enough for determining whether it's 
a driver problem or a PCI/ACPI/whatever problem.

> -Andi

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-01-29  7:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 22:12 [2.6 patch] let LOG_BUF_SHIFT default to 17 Adrian Bunk
2008-01-28 22:37 ` Randy Dunlap
2008-01-29  6:35 ` Andi Kleen
2008-01-29  7:36   ` Adrian Bunk [this message]
2008-02-01 16:20 ` Ingo Molnar
2008-02-11 22:42   ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2008-02-17  8:17 Adrian Bunk

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=20080129073607.GO8767@does.not.exist \
    --to=bunk@kernel.org \
    --cc=andi@firstfloor.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