[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20101222212112.GC3139@elte.hu>
Date: Wed, 22 Dec 2010 22:21:12 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Mike Travis <travis@....com>
Cc: Tejun Heo <tj@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
David Rientjes <rientjes@...gle.com>,
Len Brown <lenb@...nel.org>, Jack Steiner <steiner@....com>,
Lori Gilbertson <loriann@....com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Early kernel messages are overflowing the static log buffer
* Mike Travis <travis@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists