From: Chris Hanson <cph@zurich.ai.mit.edu>
To: dbr@spoke.nols.com
Cc: linux-kernel@vger.kernel.org
Subject: 2.4.1-pre10 -> 2.4.1 klogd at 100% CPU ; 2.4.0 OK
Date: Wed, 31 Jan 2001 12:45:39 -0500 [thread overview]
Message-ID: <E14O1K7-0006To-00@aarau.ai.mit.edu> (raw)
I've been trying different 2.4.1-pre kernels trying to find one
that doesn't end up with klogd pegging the CPU. 2.4.0 is OK, but
2.4.1-pre10 to 2.4.1 all leave klogd sitting at 100% CPU.
The machine in question is a Gateway E-3200, a basic PIII-500
running RH 7.0 with all the latest updates as well as the
recommended updates documented in the Changes file. The kernel is
compiled with kgcc (egcs-1.1.2).
I'm seeing exactly the same problem with 2.4.1 on a laptop (HP
OmniBook 6000, 700 MHz PIII) running Debian 2.2, patched to have
modutils 2.4.1 and linux-utils 2.10q. The kernel was compiled with
gcc 2.95.2. Again, 2.4.0 worked fine.
BTW, in my case, stopping and restarting klogd makes the problem go
away. But every time I suspend/resume the machine, it comes back.
On the other hand, a desktop machine (ASUS P2B-LS, 600 MHz PIII)
running Debian woody and Linux 2.4.1 is _not_ having this problem.
-
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 reply other threads:[~2001-01-31 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 17:45 Chris Hanson [this message]
[not found] <E14O1Qe-00021Z-00@qiwi.ai.mit.edu>
2001-01-31 18:00 ` Padraig Brady
2001-01-31 18:33 ` Chris Hanson
2001-02-01 6:06 ` David Rees
-- 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=E14O1K7-0006To-00@aarau.ai.mit.edu \
--to=cph@zurich.ai.mit.edu \
--cc=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
all inboxes | Powered by JetHome®