From: Joshua Newton <jpnewton@speakeasy.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Incredible weirdness with eepro100?
Date: 19 Jun 2002 12:39:03 -0400 [thread overview]
Message-ID: <1024504745.4149.12.camel@claymore.corona> (raw)
In-Reply-To: <Pine.LNX.4.21.0206191129040.19899-100000@mammut.nsc.liu.se>
Well, the fix is sadly simple: switching to a spare 3c905C-TX seems to
have eliminated the problem. Copying the contents of claymore:/pack (a
directory with lots of big RPMs and tarballs and other miscellany) to
rapier:/scratch is super-fast and error-free. This directory includes a
few files (such as the Chaos SoundFont) that killed the transfer
yesterday.
Once I receive my new chassis, I'll move rapier's guts to it and start
testing with FreeBSD 4.6 to try to determine whether the problem is
linked to this particular /hardware/ configuration, or if it's something
in the Linux kernel and/or drivers. I'll also swap around network cards
to try and determine if this is some sort of strange interaction between
the 3c59x and e100/eepro100 drivers.
--
"However, Science People like to believe in laws, even when such laws
can be circumvented by their own Science. They become most displeased
if you suggest it would be more accurate to speak of the Generally
Good Idea of Gravity or the Three Useful Guidelines of
Thermodynamics."
-- James Alan Gardner, /Ascending/
next parent reply other threads:[~2002-06-19 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0206191129040.19899-100000@mammut.nsc.liu.se>
2002-06-19 16:39 ` Joshua Newton [this message]
2002-06-18 17:20 Joshua Newton
2002-06-19 13:55 ` Sylvain Le Briero
2002-06-19 14:03 ` Dave Gilbert (Home)
2002-06-19 13:55 ` Sylvain Le Briero
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=1024504745.4149.12.camel@claymore.corona \
--to=jpnewton@speakeasy.net \
--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®