From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: zwane@fsmlabs.com, mingo@elte.hu, ak@suse.de, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Disable scheduler debugging
Date: Sun, 6 Jun 2004 14:55:02 -0700 [thread overview]
Message-ID: <20040606145502.4021b3bc.rddunlap@osdl.org> (raw)
In-Reply-To: <40C392BB.3020406@pobox.com>
On Sun, 06 Jun 2004 17:55:07 -0400 Jeff Garzik wrote:
| Zwane Mwaikambo wrote:
| > On Sun, 6 Jun 2004, Jeff Garzik wrote:
| >
| >
| >>Unfortunately there are just, flat-out, way too many kernel messages at
| >>boot-up. Making them KERN_DEBUG doesn't solve the fact that SMP boxes
| >>often overflow the printk buffer before you boot up to a useful userland
| >>that can record the dmesg.
| >>
| >>The IO-APIC code is a _major_ offender in this area, but the CPU code is
| >>right up there as well.
| >
| >
| > How about the configurable log buffer size patch? I think Andrew still has
| > that amongst his wares.
|
| It's in mainline. That's no excuse for the voluminous logs, though...
| I'm a "1-2 lines per module" type of person :)
It's mainline, both CONFIG and command-line settable.
I'm a "there's always some case where more info is needed"
type of person. But it won't happen on the next boot....
especially if the log size is increased. :(
--
~Randy
next prev parent reply other threads:[~2004-06-06 22:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-06 1:32 Andi Kleen
2004-06-06 5:53 ` Ingo Molnar
2004-06-06 16:24 ` Jeff Garzik
2004-06-06 21:46 ` Zwane Mwaikambo
2004-06-06 21:55 ` Jeff Garzik
2004-06-06 21:55 ` Randy.Dunlap [this message]
2004-06-06 22:57 ` David Lang
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=20040606145502.4021b3bc.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=zwane@fsmlabs.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
all inboxes | Powered by JetHome®