mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Lang <david.lang@digitalinsight.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Disable scheduler debugging
Date: Sun, 6 Jun 2004 15:57:12 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.60.0406061554370.11624@dlang.diginsite.com> (raw)
In-Reply-To: <40C3452B.5010500@pobox.com>

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.
>
neither of these are nearly as bad as the crypto code, it takes a HUGE 
kernel log to get any info from before that if you enable all the 
encryption modes.

David Lang


-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

      parent reply	other threads:[~2004-06-06 23:01 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
2004-06-06 22:57     ` David Lang [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=Pine.LNX.4.60.0406061554370.11624@dlang.diginsite.com \
    --to=david.lang@digitalinsight.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®