From: David Rees <dbr@spoke.nols.com>
To: linux-kernel@vger.kernel.org
Subject: Re: klogd is acting strange with 2.4
Date: Tue, 30 Jan 2001 08:53:59 -0800 [thread overview]
Message-ID: <20010130085359.A817@spoke.nols.com> (raw)
In-Reply-To: <20010130093035.A31970@dragon.universe>
In-Reply-To: <20010130093035.A31970@dragon.universe>; from newsreader@mediaone.net on Tue, Jan 30, 2001 at 09:30:36AM -0500
On Tue, Jan 30, 2001 at 09:30:36AM -0500, newsreader@mediaone.net wrote:
> celeron 433 intel i810. 320MB ram.
>
> Before 2.2.18. Now I've tested with both
> 2.4.1-pre12 and 2.4.1. 2.4 kernel klogd is
> always using 99% cpu. What gives?
>
> I've three other less powerful boxes running
> 2.4.x kernels and none of them behave
> like this. This server isn't taking any
> more hits than it usually does.
>
> What more information I should post here?
> I've two apache servers, pgsql and sendmail
> and some other processes running on this
> server.
Can you try 2.4.0? Are you using the 3c59x ethernet driver? I've got the
same problem on one of my machines, (see message with subject "2.4.1-pre10
-> 2.4.1 klogd at 100% CPU ; 2.4.0 OK") and the last thing that is logged
is a message from the 3c59x ethernet driver.
I'm doing a bit more digging to see what changed in the driver between
revisions. /proc/pci lists my 3c905B as this:
3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 48)
-Dave
-
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 prev parent reply other threads:[~2001-01-30 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 14:30 klogd is acting strange with 2.4 newsreader
2001-01-30 16:53 ` David Rees [this message]
2001-01-30 17:22 ` David Rees
-- strict thread matches above, loose matches on Subject: below --
2001-01-30 17:22 Jon Burgess
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=20010130085359.A817@spoke.nols.com \
--to=dbr@spoke.nols.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox