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
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
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,
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
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]
5 matches
Mail list logo