mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Rees <dbr@spoke.nols.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.1-pre10 -> 2.4.1 klogd at 100% CPU ; 2.4.0 OK
Date: Tue, 30 Jan 2001 02:16:58 -0800	[thread overview]
Message-ID: <20010130021657.A15324@spoke.nols.com> (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).

Below is the output from various files to hopefully give some hits as to 
what may be the problem:

> sh scripts/ver_linux
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux shooter.ebetinc.com 2.4.0-c1 #1 Tue Jan 30 02:08:19 PST 2001 i686 
unknown
Kernel modules         2.4.1
Gnu C                  2.96
Gnu Make               3.79.1
Binutils               2.10.0.33
Linux C Library        > libc.2.2
Dynamic linker         ldd (GNU libc) 2.2
Procps                 2.0.7
Mount                  2.10m
Net-tools              1.56
Console-tools          0.3.3
Sh-utils               2.0
Modules Loaded         


.config is at http://spoke.nols.com/~drees/config.txt
cpuinfo is at http://spoke.nols.com/~drees/cpuinfo.txt
dmesg is at   http://spoke.nols.com/~drees/dmesg.txt

Thanks,
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/

             reply	other threads:[~2001-01-30 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30 10:16 David Rees [this message]
2001-01-31 17:45 Chris Hanson
     [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

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=20010130021657.A15324@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

all inboxes | Powered by JetHome®