From: Mike Travis <travis@sgi.com>
To: Tejun Heo <tj@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, "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 11:03:28 -0800 [thread overview]
Message-ID: <4D124B80.9040401@sgi.com> (raw)
In-Reply-To: <4D1249ED.9040008@sgi.com>
...
>> Yeap, with percpu allocator now mostly stable, I don't think the
>> message needs to be KERN_INFO anymore. I'll change it to KERN_DEBUG.
>>
>> Thanks.
>>
>
> 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.
Btw, I meant to add that the my patchset allocates the log buffer right
after boot mem is setup. So this output does not affect the overflow
problem, though it is nice to clean up the console output whenever we can.
next prev parent reply other threads:[~2010-12-22 19:03 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 [this message]
2010-12-22 21:21 ` Ingo Molnar
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=4D124B80.9040401@sgi.com \
--to=travis@sgi.com \
--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=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=steiner@sgi.com \
--cc=tj@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