linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
To: <linuxppc-dev@ozlabs.org>
Subject: Xilinx network trouble
Date: Thu, 17 Apr 2008 12:04:12 +0200	[thread overview]
Message-ID: <03fc01c8a072$67280110$ad289e86@LPSC0173W> (raw)

Our network guru is out on vacation, so I'll ask here...
I now have a working Xilinx ML405 board... except the network is flaky to 
say the least.

I have tried both with the Emac Lite and the LLTemac IPs.

They both work during the DHCP state of the kernel boot, my target board 
gets its IP and network parameters alright from the host DHCP server.

The Emac Lite can ping both ways, but with 500ms and 30% packet loss when 
pinging from the host PC and 300ms and 70% packet loss the other way. And it 
goes in hiccups: 30s or so with no pings, and then 30s or so with 90% 
success... RX/TX LEDs also are dark when there's nothing going on.

When using the LLTemac, ping just doesn't work.

ifconfig shows no drops and no collisions in both cases.

I'm no network specialist so I don't know what kind of tools I can use for 
further diagnosis.

Here are some of the relevant kernel options I've set for both 
configurations:

$ egrep "EMAC|NET|XILINX|NFS" .config | egrep -v "^#|^$"
CONFIG_XILINX_ML405=y
CONFIG_XILINX_MLxxx=y
CONFIG_XILINX_VIRTEX_4_FX=y
CONFIG_XILINX_VIRTEX=y
CONFIG_XILINX_EMBED_CONFIG=y
CONFIG_NET=y
CONFIG_INET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_XILINX_SYSACE=y
CONFIG_XILINX_DRIVERS=y
CONFIG_NEED_XILINX_IPIF=y
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_XILINX_EMACLITE=y
CONFIG_XILINX_GPIO=y
CONFIG_XILINX_HWICAP=y
CONFIG_XILINX_IIC=y
CONFIG_XILINX_EDK=y
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_ROOT_NFS=y
CONFIG_NFS_COMMON=y

or:

CONFIG_XILINX_ML405=y
CONFIG_XILINX_MLxxx=y
CONFIG_XILINX_VIRTEX_4_FX=y
CONFIG_XILINX_VIRTEX=y
CONFIG_XILINX_EMBED_CONFIG=y
CONFIG_NET=y
CONFIG_INET=y
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
CONFIG_XILINX_SYSACE=y
CONFIG_XILINX_DRIVERS=y
CONFIG_NEED_XILINX_LLDMA=y
CONFIG_NETDEVICES=y
CONFIG_NETDEV_1000=y
CONFIG_XILINX_LLTEMAC=y
CONFIG_XILINX_LLTEMAC_MARVELL_88E1111_GMII=y
CONFIG_XILINX_GPIO=y
CONFIG_XILINX_HWICAP=y
CONFIG_XILINX_IIC=y
CONFIG_XILINX_EDK=y
CONFIG_NETWORK_FILESYSTEMS=y
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_ROOT_NFS=y
CONFIG_NFS_COMMON=y

Thanks for any hint.
-- 
Guillaume Dargaud
http://www.gdargaud.net/

             reply	other threads:[~2008-04-17 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 10:04 Guillaume Dargaud [this message]
2008-04-17 15:56 ` Xilinx network trouble Rick Moleres
2008-04-18 14:40   ` Xilinx network trouble (mostly solved) Guillaume Dargaud
2008-04-18 16:14     ` Rick Moleres
2008-04-21 16:16       ` Guillaume Dargaud
2008-04-21 16:50         ` Stephen Neuendorffer

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='03fc01c8a072$67280110$ad289e86@LPSC0173W' \
    --to=dargaud@lpsc.in2p3.fr \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).