public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josh Fryman <fryman@cc.gatech.edu>
To: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
Cc: Ion Badulescu <ionut@cs.columbia.edu>,
	Andrey Savochkin <saw@saw.sw.com.sg>,
	linux-kernel@vger.kernel.org
Subject: Re: eepro100 driver update for 2.4
Date: Fri, 08 Dec 2000 17:47:23 -0500	[thread overview]
Message-ID: <3A3164FB.EA5957B7@cc.gatech.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0012081254360.26353-100000@age.cs.columbia.edu> <3A3162A0.825FA107@Hell.WH8.TU-Dresden.De>

> * put cable in *
>
> eth0: card reports no RX buffers.
> eth0: card reports no resources.
> eth0: card reports no RX buffers.
> eth0: card reports no resources.

you know, this might be entirely unrelated, but i had the exact same type of
problem with a brand new machine running a not-so-brand new EE100 nic.   i
couldn't figure out what was wrong, since it was a literal replacement with an
earlier machine with the same general setup (except it was a pentium-90, this
was a celeron-500-something) ... and in the p-90, that network card never gave
a hiccup.

the only way i could get it to stop was to change the network infrastructure.
this card was connected to a cisco catalyst 1000 24-port 10T switch and 2-port
100T switch.  i stuck a generic repeater off one of the 100T ports, jacked the
ee100 into the repeater, and the problem *went away*.

i thought it was just an anomaly.

if it will help, i can get the info from that machine and post it to this
thread.

cheers,

josh fryman


-
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:[~2000-12-08 23:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-17  9:23 eepro100 driver update for 2.4 Andrey Savochkin
2000-11-30 18:41 ` Udo A. Steinberg
2000-12-01  9:51   ` Andrey Savochkin
2000-12-01 12:55     ` Udo A. Steinberg
2000-12-01 21:45     ` Ion Badulescu
2000-12-04 13:16       ` Andrey Savochkin
2000-12-05 19:13         ` Ion Badulescu
2000-12-05 21:37           ` Udo A. Steinberg
2000-12-06 12:23           ` Andrey Savochkin
2000-12-08 19:44             ` Ion Badulescu
2000-12-08 20:25               ` Udo A. Steinberg
2000-12-08 20:57                 ` Ion Badulescu
2000-12-08 22:37                   ` Udo A. Steinberg
2000-12-08 22:47                     ` Josh Fryman [this message]
2000-12-10 23:34                 ` Anton Altaparmakov
2000-12-11  0:09                   ` Udo A. Steinberg
2000-12-11  3:16                     ` Ion Badulescu
2000-12-11  3:29                       ` Udo A. Steinberg
2000-12-11  8:19                     ` Anton Altaparmakov

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=3A3164FB.EA5957B7@cc.gatech.edu \
    --to=fryman@cc.gatech.edu \
    --cc=ionut@cs.columbia.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saw@saw.sw.com.sg \
    --cc=sorisor@Hell.WH8.TU-Dresden.De \
    /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