From: "wlacey" <wlacey@goldenhindresearch.com>
To: linux-mips@linux-mips.org
Subject: dead RTL8139D eth
Date: Wed, 25 Feb 2004 17:50:56 [thread overview]
Message-ID: <20040225175056.17002.qmail@server212.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]
I'm currently bringing up a 2.4.28 based kernel on a tx4925 equipped board attempting to use an NFS'ed root filesystem.
The problem is I never see the initial RPC requests from the target to the host machine. The target knows via boot options it's ip address and the address of the nfs host.
The attempt at transfer fails, I never see reception of _any_ message on the host and the interface statistics never reflect that any packet has even been attempted to be sent. i.e. tx bytes/packes are always zero.
Some output follows...
RPC: rpc_execute flgs 0
start_xmit() max(len:42 ETH_ZLEN:60) 60
Post xmit stats tx_bytes:0 tx_packets:0 tx_dropped:0
Post xmit stats rx_bytes:0 rx_packets:0 rx_dropped:0
start_xmit() max(len:42 ETH_ZLEN:60) 60
Post xmit stats tx_bytes:0 tx_packets:0 tx_dropped:0
Post xmit stats rx_bytes:0 rx_packets:0 rx_dropped:0
start_xmit() max(len:42 ETH_ZLEN:60) 60
Post xmit stats tx_bytes:0 tx_packets:0 tx_dropped:0
Post xmit stats rx_bytes:0 rx_packets:0 rx_dropped:0
start_xmit() max(len:42 ETH_ZLEN:60) 60
Post xmit stats tx_bytes:0 tx_packets:0 tx_dropped:0
Post xmit stats rx_bytes:0 rx_packets:0 rx_dropped:0
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 0d 0040 media 10.
io address:00001000 inl:8014baac
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 00002000. (queue head)
eth0: Tx descriptor 1 is 00002000.
eth0: Tx descriptor 2 is 00002000.
eth0: Tx descriptor 3 is 00002000.
eth0: Setting 100mbps full-duplex based on auto-negotiated partner ability 45e1.
What am I doing wrong?
Warrick Lacey
[-- Attachment #2: Type: text/html, Size: 1800 bytes --]
reply other threads:[~2004-02-25 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040225175056.17002.qmail@server212.com \
--to=wlacey@goldenhindresearch.com \
--cc=linux-mips@linux-mips.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