Re: Early kernel messages are overflowing the static log buffer

[Mike Travis]

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.

Tejun Heo wrote:
> Hello,
>
> On Wed, Dec 22, 2010 at 02:09:46PM +0100, Ingo Molnar wrote:
> > > [    0.000000] pcpu-alloc: [000] 0000 0001 0002 0003 0004 0005 0006 0007 1024 1025 1026 1027 1028 1029 1030 1031
> > >
> > > What I'm asking is which of these would be most acceptable to
> > > either remove or replace with some sort of message reduction?
> > The pcpu alloc messages look entirely superfluous and zappable - make them 
> > KERN_DEBUG perhaps (and Cc: Tejun)?
>
> 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.

Thanks,
Mike

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/