Re: [PATCH] klogd busy loop on zero byte (output from 3c59x driver)

On Thu, Jan 11, 2001 at 11:03:31PM +1100, Andrew Morton wrote: > > Yep. %02x%02x it now is. > > The code in question was snitched from pcmcia-cs's 3c575_cb.c, and > I assume David would have heard if it was busting klogd. Maybe > there's a klogd version problem, or maybe your NIC's EEPROM is h

RE: [PATCH] klogd busy loop on zero byte (output from 3c59x driver)

> Yep. %02x%02x it now is. I suppose it might be worthwhile to search the kernel sources for other instances of printk("%c"), there's no telling when all distributions will be up to date with new sysklogd releases... > The code in question was snitched from pcmcia-cs's 3c575_cb.c, and > I assum

Re: [PATCH] klogd busy loop on zero byte (output from 3c59x driver)

Troels Walsted Hansen wrote: > > 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. I > came upon it when the 3c59x driver from kernel 2.4.0 started outputting two > zero bytes for the

Re: [PATCH] klogd busy loop on zero byte (output from 3c59x driver)

Zitiere Troels Walsted Hansen <[EMAIL PROTECTED]>: > 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