From: Urban Widmark <urban@teststation.com>
To: David Schmitt <david@heureka.co.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ISSUE: DFE530-TX REV-A3-1 times out on transmit
Date: Mon, 27 Aug 2001 21:02:29 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.10.10108272025400.25944-100000@ada.teststation.com> (raw)
In-Reply-To: <20010827102740.A9557@www.heureka.co.at>
On Mon, 27 Aug 2001, David Schmitt wrote:
> > Reloading the module is to the hardware about the same as the watchdog
> > reset.
>
> Good news: Under 2.2.19, reloading the module indeed reset the card,
> so that it worked again.
Interesting ...
> > Rebooting obviously triggers something else too ... perhaps the BIOS talks
> > some sense to the card.
>
> As mentioned above, it seems like the 2.2.19 version does the Right
> Thing (but doesn't recover autmatically).
The 2.2.19 version doesn't do anything on timeout (except print a message
that it is resetting, which it isn't :). The driver has a few changes
during the 2.4 series:
2.4.3 was patched to actually reset things on tx_timeout, but that also
changed the startup sequence.
2.4.6 got changes to reload certain things from eeprom when the driver is
loaded (fix a problem with booting from win98 that does a power down).
2.4.7 changes to the transmit code to use "singlecopy" for unaligned
buffers.
2.4.8-acX fixed a bug in the startup code from 2.4.3
Testing the 2.4.2 and 2.4.3 drivers could give something (should work to
simply copy the drivers/net/via-rhine.c from the different versions into a
2.4.9 source tree).
> but doing one or two parallel ping -f other.machine locks the NIC for
> good.
Good (that you have a reliable way to trigger this). For about how long do
you need to run this?
> The network where the DFE530TX (and the other.machine) are attached
> contains some 20-30 Windows PCs and some Novell Servers which all seem
> quite braodcast-happy. The network itself is (mostly) unswitched and
> 10Mbit halfduplex, so I guess this really is connected to the
> collisions.
Depending on the sort of access you have, you could test unplugging
everyone else and repeat the 'ping -f' test.
I don't have the hardware to test now, but when time permits ...
/Urban
next prev parent reply other threads:[~2001-08-27 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 14:24 ISSUE: DFE530-TX REV-A3-1 times out on transmit David Schmitt
2001-08-25 17:05 ` Urban Widmark
2001-08-27 8:27 ` David Schmitt
2001-08-27 9:13 ` David Schmitt
2001-08-27 19:02 ` Urban Widmark [this message]
2001-08-28 13:45 ` David Schmitt
2001-08-28 19:46 ` Urban Widmark
2001-08-29 6:42 ` Dennis Bjorklund
2001-08-29 12:48 ` David Schmitt
2001-08-29 18:45 ` Urban Widmark
2001-08-31 12:18 ` David Schmitt
2001-08-28 7:26 ` Dennis Bjorklund
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=Pine.LNX.4.10.10108272025400.25944-100000@ada.teststation.com \
--to=urban@teststation.com \
--cc=david@heureka.co.at \
--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;
as well as URLs for NNTP newsgroup(s).