From: Gashaw Teshome <gasht@neopets.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.4.2 & eepro100
Date: Tue, 27 Feb 2001 18:44:48 -0800 [thread overview]
Message-ID: <3A9C6620.F380491@neopets.com> (raw)
I recently compiled a fresh download of a 2.4.2 kernel to test a server
at work. The machine is a dual P-III, 512 MB RAM on an Intel L440GX+
motherboard with a built in eepro100 network interface. Almost
immediately after boot up, the kernel started reporting:
Feb 23 19:40:23 www136 kernel: NET: 486 messages suppressed.
Feb 23 19:40:29 www136 kernel: NET: 858 messages suppressed.
Feb 23 19:40:33 www136 kernel: NET: 879 messages suppressed.
Feb 23 19:40:38 www136 kernel: NET: 983 messages suppressed.
Feb 23 19:40:43 www136 kernel: NET: 1296 messages suppressed.
Feb 23 19:40:49 www136 kernel: NET: 1780 messages suppressed.
Feb 23 19:40:53 www136 kernel: NET: 1378 messages suppressed.
Feb 23 19:40:58 www136 kernel: NET: 246 messages suppressed.
Feb 23 19:41:04 www136 kernel: NET: 173 messages suppressed.
Feb 23 19:41:09 www136 kernel: NET: 32 messages suppressed.
Feb 23 19:42:32 www136 kernel: NET: 37 messages suppressed.
At the same time, our bandwidth graph (rrdtool) showed almost zero
network traffic. Also, load on the test machine went to 30! After the
errors went away, bandwidth returned to normal and load went down
considerably.
This cycle (error message, extremely high load, zero bandwidth) repeated
about every half hour and lasted for about 1 1/2 minutes. I eventually
took the machine down and rebooted it with its original 2.2 kernel.
There were no more error messages or bandwidth drops after that.
I have heard mentioned that there are some issues with the eepro100
driver in 2.4.x. Could that be the cause of this strange behaviour?
Any help would be appreciated.
Gash Teshome
reply other threads:[~2001-02-28 2:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A9C6620.F380491@neopets.com \
--to=gasht@neopets.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 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.