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,
Joey
--
Every use of Linux is a proper use of Linux. -- Jon 'maddog' Hall
Please always Cc to me when replying to me on the lists.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
