From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.3 RT8139too NIC problems
Date: Thu, 19 Feb 2004 16:47:08 -0000 [thread overview]
Message-ID: <4034E88C.24740.4C5D4B6@localhost> (raw)
Hello all,
Due to traffic restraints, I am not on the lkml - please CC replies.
Yesterday I built 2.6.3. Clean build, and system runs nice.
I have two NIC's in the box, both rt8139.
But I noticed I am getting this in syslogs:
Linux233 kernel: NETDEV WATCHDOG: eth1: transmit timed out
Linux233 kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000
Linux233 kernel: nfs: server 486Linux not responding, still trying
Linux233 kernel: nfs: server 486Linux not responding, still trying
Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux OK
Linux233 kernel: nfs: server 486Linux not responding, still trying
Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Linux233 kernel: nfs: server 486Linux OK
This happens about once every 3 hours.
>From my config file:
# CONFIG_8139CP is not set
CONFIG_8139TOO=y
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_8139_RXBUF_IDX= is not set
No other NIC drivers are used.
I am also stuck as to what the new RXBUF_IDX is for. It appears the
new build needs it, as I cannot remove.
These cards have worked fine under all 2.4.x and 2.6.1/2.6.2 kernels.
Ideas?
TIA,
Nick
--
"I am not Spock", said Leonard Nimoy.
"And it is highly illogical of humans to assume so."
next reply other threads:[~2004-02-19 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 16:47 Nick Warne [this message]
2004-02-19 17:11 ` 2.6.3 RT8139too NIC problems Paul Mundt
2004-02-19 17:17 ` Nick Warne
2004-02-19 22:48 ` Jeff Garzik
2004-02-20 16:42 ` Nick Warne
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 20:04 Nick Warne
2004-02-21 14:59 Nick Warne
[not found] ` <14539106.1077630890@42.150.104.212.access.eclipse.net.uk>
2004-02-24 18:23 ` Nick Warne
2004-02-24 20:36 Nick Warne
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=4034E88C.24740.4C5D4B6@localhost \
--to=nick@ukfsn.org \
--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.