public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mike Travis <travis@sgi.com>
Cc: Tejun Heo <tj@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Rientjes <rientjes@google.com>, Len Brown <lenb@kernel.org>,
	Jack Steiner <steiner@sgi.com>, Lori Gilbertson <loriann@sgi.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Early kernel messages are overflowing the static log buffer
Date: Wed, 22 Dec 2010 22:21:12 +0100	[thread overview]
Message-ID: <20101222212112.GC3139@elte.hu> (raw)
In-Reply-To: <4D1249ED.9040008@sgi.com>


* Mike Travis <travis@sgi.com> wrote:

> Thanks.
> 
> I have a patchset almost ready for submission.  We have a giant
> system (6 racks with some huge amount of nodes) for a few more
> days, and the buffer still overflowed with my changes.  So I'm
> making one more tweak to cut down the amount of characters generated
> without losing information.

Also feel free to make judgement calls to cut information - people _think_ they need 
all that boot time noise but it's rarely useful. Memory layout is - but a lot of 
other details are not. So dont try to preserve things at any cost.

> This doesn't really help the log buffer overflow problem as KERN_DEBUG
> messages still end up in the buffer.  The pr_debug() macro does compile
> out the messages if the system does not have KERNEL debug set, though
> distros also have this set as a default.

Make the whole printout dependent on a percpu-debug boot parameter? (and default the 
switch to off?)

Thanks,

	Ingo

      parent reply	other threads:[~2010-12-22 21:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 23:58 Early kernel messages are overflowing the static log buffer Mike Travis
2010-12-22 13:09 ` Ingo Molnar
2010-12-22 13:17   ` Tejun Heo
2010-12-22 13:22     ` [PATCH] percpu: print out alloc information with KERN_DEBUG instead of KERN_INFO Tejun Heo
2010-12-22 18:56     ` Early kernel messages are overflowing the static log buffer Mike Travis
2010-12-22 19:03       ` Mike Travis
2010-12-22 21:21       ` Ingo Molnar [this message]

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=20101222212112.GC3139@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=loriann@sgi.com \
    --cc=rientjes@google.com \
    --cc=steiner@sgi.com \
    --cc=tj@kernel.org \
    --cc=travis@sgi.com \
    /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