From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: 8139too cannot receive pkts in 2.4.19-rc3
Date: Sun, 28 Jul 2002 23:54:57 -0700 [thread overview]
Message-ID: <3D44E6C1.6090002@candelatech.com> (raw)
I just upgraded a SpaceWalker SV-50 machine with a builtin Realtek
nic. The NIC can no longer receive pkts it seems. It can transmit
fine, as witnessed by other machines on the network.
lspci says the realtek is:
RTL-8139/8139C (rev 10)
The NIC is plugged into a 10bt hub.
The messages in /var/log/messages look like:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Setting half-duplex based on auto-negotiated partner ability 0000
I tested in on a 100bt-FD switch, and it failed there too, though it
did have a message in the log about negotiating 100bt-FD.
This works in stock RH 7.3 kernel.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next reply other threads:[~2002-07-29 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 6:54 Ben Greear [this message]
2002-08-15 5:50 ` 8139too cannot receive pkts in 2.4.19-rc3 Scott Bronson
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=3D44E6C1.6090002@candelatech.com \
--to=greearb@candelatech.com \
--cc=jgarzik@mandrakesoft.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.