Scott,
 I am not so sure about your PHY, but if you access to PHY while packet
transmission through MDIO bus, the packet might be corrupted. Do you
have "phy_interrupt" in the /proc/interrupts? What is your dmesg around
the eTSEC look like (there is phy driver info surrounded).

Regards
Dai

-----Original Message-----
From: Scott Coulter [mailto:scott.coulter@cyclone.com]
Sent: Friday, February 20, 2009 3:00 PM
To: Haruki Dai-R35557; linuxppc-dev@ozlabs.org
Cc: Gala Kumar-B11780
Subject: RE: Gianfar tx-babbling-errors
=20
=20
=20
=20
Dai,
=20

quoted

 Is this your own board? If so, what PHY chip are you using? Are you
using the PHY driver?
 If the generic PHY driver is used and polling the MDIO periodically

for

quoted

the link check, you may truncate the packet. I hope this is not the
case.

=20
Yes this is our own board.  Both the 8568E and 8572E processors each
expose two TSECs.  The 4 TSECs are each connected to a separate
interface of a  Broadcom 5464 Quad PHY in RGMII mode.  I am pretty

sure

that there is no interrupt connected (I'll have to check with the
hardware engineer) and I know that I didn't configure one in the DTS
file.  My kernel is configured to use the Broadcomm 54xx driver, but

I'm

not sure if it polls when no interrupt is configured.
=20
Thanks,
Scott
___________________________________________________________________
=20
  Scott N. Coulter
  Senior Software Engineer
=20
  Cyclone Microsystems
  370 James Street              Phone:  203.786.5536 ext. 118
  New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
  U.S.A.                        Web:    http://www.cyclone.com
___________________________________________________________________
=20

quoted

-----Original Message-----
From: Haruki Dai-R35557 [mailto:Dai.Haruki@freescale.com]
Sent: February 20, 2009 2:16PM
To: Scott Coulter; linuxppc-dev@ozlabs.org
Cc: Gala Kumar-B11780
Subject: RE: Gianfar tx-babbling-errors

Hi Scott,


Regards
Dai

quoted

-----Original Message-----
From: linuxppc-dev-bounces+dai.haruki=3Dfreescale.com@ozlabs.org
=

[mailto:linuxppc-dev-bounces+dai.haruki=3Dfreescale.com@ozlabs.org]
On

quoted

Behalf Of

quoted

Scott Coulter
Sent: Wednesday, February 18, 2009 10:16 AM
To: linuxppc-dev@ozlabs.org
Subject: Gianfar tx-babbling-errors


Hi all,

As a simple stress test for my board with an MPC8572E and an

MPC8568E

quoted

on

quoted

it, I setup both processors to boot linux 2.6.27.6 with an NFS

root

quoted

and

quoted

then perform repeated native compiles of a linux kernel over NFS.

After

quoted

running for 4 days straight or so with between 250-300 build

cycles

quoted

per

quoted

processor, I stopped the builds and ran ethtool to look for any

odd

quoted

quoted

statistics.  Both processors reported non-zero values for
tx-babbling-errors.  Both processors reported around 1300
tx-babbling-errors out of about 80,000,000 Tx packets.  Should I

be

quoted

quoted

concerned about the tx-babbling-errors?  What conditions would

cause

quoted

quoted

these errors to be reported?

Thanks,
Scott

___________________________________________________________________

quoted

quoted

  Scott N. Coulter
  Senior Software Engineer

  Cyclone Microsystems
  370 James Street              Phone:  203.786.5536 ext. 118
  New Haven, CT 06513-3051      Email:  scott.coulter@cyclone.com
  U.S.A.                        Web:    http://www.cyclone.com

___________________________________________________________________

quoted

quoted

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev

=20