> Hi all.
>
> I found a bug in the sysklogd package version 1.4. When it encounters a
> zero
> byte in the kernel logging output, the text parser enters a busy loop.
That finally explains the "klogd eats 100% cpu time" reports with ~2.2.10:
We (I and Andrea) fixed several bugs in the kernel code, but none of them
explained why klogd entered a busy loop.
-- Manfred - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/