lkml.org 
[lkml]   [2004]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH] Disable scheduler debugging
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:03    [W:0.041 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site