Well, i found something in my logs:
This really is weird :)
Shawn.
Alan Cox wrote:
> > Well, strangely, it stopped as it started?
> > 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 though
> Well, strangely, it stopped as it started?
> 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?
Yep. So something else happened in this case. I don't know what b
Well, strangely, it stopped as it started?
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 10
> 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
Ok, I rebooted the system, then syslogd was using 100% cpu?
it seems like perhaps reiserfs is causing this problem??
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
5 matches
Mail list logo
