From: "Kevin P. Fleming" <kevin@labsysgrp.com>
To: <linux-kernel@vger.kernel.org>
Subject: 2.4.7-pre7 natsemi network driver random pauses
Date: Thu, 19 Jul 2001 09:19:47 -0700 [thread overview]
Message-ID: <00f101c1106e$a119e3c0$6baaa8c0@kevin> (raw)
I upgraded two machines here from 2.4.7-pre6 to 2.4.7-pre7 yesterday
afternoon.
The first machine I upgraded, my workstation, is a 1GHz Athlon on a VIA
KT133 (not A) motherboard using a NetGear FA312TX network card. This machine
has always run Linux just fine. After this upgrade, telnetting to my other
Linux machine (not yet upgraded) and doing long directory listings (or tar
tzvf linux-2.4.0.tar) exhibits random (and long) pauses in the output.
Switching back to 2.4.7-pre6 makes the problem disappear. Note that at this
time only the _client_ end of this connection had been upgraded to -pre7.
I then upgraded my server as well, which is a 700 MHz Coppermine Celeron on
an SIS 630 motherboard, also using a NetGear FA312TX network card. Now this
machine exhibits the same symptoms, even when the telnet client is on a
Windows machine.
So, it appears that one of two things happened:
a) the natsemi driver had changes merged between -pre6 and -pre7 (not listed
in the changelogs) that had negative effects on my systems
b) something else in the kernel caused irq/softirq/whatever random latency
to appear
Any ideas where I should start looking?
next reply other threads:[~2001-07-19 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 16:19 Kevin P. Fleming [this message]
2001-07-19 16:37 ` Wilfried Weissmann
2001-07-19 16:48 ` Andrew Morton
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='00f101c1106e$a119e3c0$6baaa8c0@kevin' \
--to=kevin@labsysgrp.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®