LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Laurent Lagrange" <lagrange@fr.oleane.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: 82xx fcc_enet problem between Linux 2.4 and 2.6
Date: Thu, 31 Aug 2006 19:46:27 +0200	[thread overview]
Message-ID: <002101c6cd25$6945e470$5201a8c0@GEG2400> (raw)
In-Reply-To: 


Hello,

I work on several custom 82xx boards with Linux 2.4 and 2.6.

I have ported Linux 2.6.9 on different boards and I noticed
that I have tx carrier errors on my FCC ports. Almost one
error per xmit.

I reinstalled Linux 2.4.18 on these boards and I have NO ERROR.

The errors arise with PHY configured in 100M full duplex (or autoneg).
The FCC has the same duplex as PHY.

I found on web another mail concerning a problem on PQ2FADS Linux2.6.8
when mounting a NFS. The writer has also noticed that he has
tx carrier errors but the mail focused on mount and not FCC.

> # ifconfig
> eth0      Link encap:Ethernet  HWaddr 08:00:17:40:00:03
>           inet addr:192.168.0.5  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:122 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:114 errors:0 dropped:0 overruns:0 carrier:114
>           collisions:0 txqueuelen:1000
>           RX bytes:20747 (20.2 kb)  TX bytes:14320 (13.9 kb)
>           Base address:0x8500

I think this is not a phy or hardware problem but rather a FCC configuration
mismatch in fcc_enet.c.

Thanks for any tips
Laurent

             reply	other threads:[~2006-08-31 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 17:46 Laurent Lagrange [this message]
2006-09-01 11:43 ` 82xx fcc_enet problem between Linux 2.4 and 2.6 Bastos Fernandez Alexandre
2006-09-01 14:26   ` Laurent Lagrange

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='002101c6cd25$6945e470$5201a8c0@GEG2400' \
    --to=lagrange@fr.oleane.com \
    --cc=linuxppc-embedded@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