From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 RT8139too NIC problems
Date: Thu, 19 Feb 2004 20:04:27 -0000 [thread overview]
Message-ID: <403516CB.22343.57A7D52@localhost> (raw)
> So, corrected (and as the kernel was built):
>
> # 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=2
OK, I think there _is_ a problem here. I was suspecting my NFS setup
maybe causing the NIC (eth0) to timeout and get reset, as I mount
files from an old 486 -> 2.6.3 box.
But after messing about a bit, I checked the logs on my 2.4.24 box
via SSH (AND eth1). It hung as issued #> pico /var/log/messages for
about 3 seconds.. then came to life. So...
... in the logs on 2.6.3 box straight after:
Feb 19 19:33:13 Linux233 kernel: NETDEV WATCHDOG: eth1: transmit
timed out
Feb 19 19:33:13 Linux233 kernel: eth1: link up, 10Mbps, half-duplex,
lpa 0x0000
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 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 20:04 Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 20:36 2.6.3 RT8139too NIC problems 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-19 16:47 Nick Warne
2004-02-19 17:11 ` Paul Mundt
2004-02-19 17:17 ` Nick Warne
2004-02-19 22:48 ` Jeff Garzik
2004-02-20 16:42 ` 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=403516CB.22343.57A7D52@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.