From: Padraig Brady <Padraig@AnteFacto.com>
To: Chris Hanson <cph@zurich.ai.mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1-pre10 -> 2.4.1 klogd at 100% CPU ; 2.4.0 OK
Date: Wed, 31 Jan 2001 18:00:09 +0000 [thread overview]
Message-ID: <3A7852A9.1060600@AnteFacto.com> (raw)
In-Reply-To: <E14O1Qe-00021Z-00@qiwi.ai.mit.edu>
Chris Hanson wrote:
> Date: Wed, 31 Jan 2001 17:48:50 +0000
> From: Padraig Brady <Padraig@AnteFacto.com>
>
> Are you using the 3c59x driver?
>
> Yes.
Can we sort this out once and for all? There are a few emails
everyday relating to this bug.
The following patch posted by "Troels Walsted Hansen" <troels@thule.no>
on Jan 11th fixes this. The problem is that when 2 consequtive
NULLs are sent to klogd it goes into a busy loop. Andrew Mortons
3c59x driver does this, but also on Jan 11th he replied that he had
fixed it. I'm using 2.4ac4 with no problems, so I presume some
of these patches have been lost along the way?
--- sysklogd-1.4.orig/klogd.c Mon Sep 18 09:34:11 2000
+++ sysklogd-1.4/klogd.c Thu Jan 11 09:26:10 2001
@@ -739,6 +758,13 @@
break; /* full line_buff or end of input buffer */
}
+ if( *ptr == '\0' ) /* zero byte */
+ {
+ ptr++; /* skip zero byte */
+ space -= 1;
+ len -= 1;
+ break;
+ }
if( *ptr == '\n' ) /* newline */
{
ptr++; /* skip newline */
-
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/
next parent reply other threads:[~2001-01-31 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E14O1Qe-00021Z-00@qiwi.ai.mit.edu>
2001-01-31 18:00 ` Padraig Brady [this message]
2001-01-31 18:33 ` 2.4.1-pre10 -> 2.4.1 klogd at 100% CPU ; 2.4.0 OK Chris Hanson
2001-02-01 6:06 ` David Rees
2001-01-31 17:45 Chris Hanson
-- strict thread matches above, loose matches on Subject: below --
2001-01-30 10:16 David Rees
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A7852A9.1060600@AnteFacto.com \
--to=padraig@antefacto.com \
--cc=cph@zurich.ai.mit.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.