I don't know what caused it to go loopy but then it just stopped. Im using:
syslogd -ver
syslogd 1.4-0
klogd -v
klogd 1.4-0
I thought this only affected older versions?
Shawn.
Alan Cox wrote:
> > Ok, I rebooted the system, then syslogd was using 100% cpu?
> > it seems like perhaps reiserfs is causing this problem??
>
> Typically it means your syslogd (klogd actually) is too old and has a bug that
> a 0 length printk causes it to spin.
-
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/