public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jon Burgess" <Jon_Burgess@eur.3com.com>
To: David Rees <dbr@spoke.nols.com>, newsreader@mediaone.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: klogd is acting strange with 2.4
Date: Tue, 30 Jan 2001 17:22:05 +0000	[thread overview]
Message-ID: <802569E4.005F6E19.00@notesmta.eur.3com.com> (raw)



>> 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?
>>

> 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
> s a message from the 3c59x ethernet driver.

I've seen someone else report that this occurs when klogd reads a NULL
character. In his case the line in the 3c59x.c driver which prints out the
'product code' was responsible for this.

In the 2.4.1 patch this printk has been added to 3c59x.c:-

+    printk(KERN_INFO "  product code '%c%c' rev %02x.%d date %02d-"
+            "%02d-%02d\n", eeprom[6]&0xff, eeprom[6]>>8, eeprom[0x14],
+            step, (eeprom[4]>>5) & 15, eeprom[4] & 31, eeprom[4]>>9);

Could you try commenting out these lines and see if it fixes the problem?

     Jon


-
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 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30 17:22 Jon Burgess [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30 14:30 klogd is acting strange with 2.4 newsreader
2001-01-30 16:53 ` David Rees
2001-01-30 17:22   ` 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=802569E4.005F6E19.00@notesmta.eur.3com.com \
    --to=jon_burgess@eur.3com.com \
    --cc=dbr@spoke.nols.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=newsreader@mediaone.net \
    /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