Bug#308580: (no subject)

2007-05-27 Thread Martin Schulze
Ari Pollak wrote: Martin Schulze wrote: You can disable printk() in the kernel? WTF? What's the log message when klogd is starting? Does /proc/kmsg exist? CONFIG_PRINTK=y Uff! Yes, you can disable printk, and that had been the default somewhere around 2.6.12 or 2.6.11 when doing

Bug#308580: (no subject)

2007-05-27 Thread Ari Pollak
Martin Schulze wrote: Yes, you can disable printk, and that had been the default somewhere around 2.6.12 or 2.6.11 when doing a make oldconfig. I have not tried it since then. Do you have a spare machine and some desire to test this and find out what goes bezerk? I have the latter but am

Bug#308580: (no subject)

2007-05-26 Thread Martin Schulze
Ari Pollak wrote: ok, so I figured out that this only happens when printk is disabled in the kernel. Still, klogd shouldn't hog the CPU when that happens. You can disable printk() in the kernel? WTF? What's the log message when klogd is starting? Does /proc/kmsg exist? Regards,

Bug#308580: (no subject)

2007-05-26 Thread Ari Pollak
Martin Schulze wrote: You can disable printk() in the kernel? WTF? What's the log message when klogd is starting? Does /proc/kmsg exist? CONFIG_PRINTK=y Yes, you can disable printk, and that had been the default somewhere around 2.6.12 or 2.6.11 when doing a make oldconfig. I have not

Bug#308580: (no subject)

2005-06-19 Thread Ari Pollak
ok, so I figured out that this only happens when printk is disabled in the kernel. Still, klogd shouldn't hog the CPU when that happens. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]