Gianfar tx-babbling-errors

[Scott Coulter]

Dai,

>  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
> the link check, you may truncate the packet. I hope this is not the
> case.

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.

Thanks,
Scott
___________________________________________________________________

  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 at cyclone.com
  U.S.A.                        Web:    http://www.cyclone.com
___________________________________________________________________

> -----Original Message-----
> From: Haruki Dai-R35557 [mailto:Dai.Haruki at freescale.com]
> Sent: February 20, 2009 2:16PM
> To: Scott Coulter; linuxppc-dev at ozlabs.org
> Cc: Gala Kumar-B11780
> Subject: RE: Gianfar tx-babbling-errors
> 
> Hi Scott,
> 
> 
> Regards
> Dai
> 
> > -----Original Message-----
> > From: linuxppc-dev-bounces+dai.haruki=freescale.com at ozlabs.org
> > [mailto:linuxppc-dev-bounces+dai.haruki=freescale.com at ozlabs.org] On
> Behalf Of
> > Scott Coulter
> > Sent: Wednesday, February 18, 2009 10:16 AM
> > To: linuxppc-dev at ozlabs.org
> > Subject: Gianfar tx-babbling-errors
> >
> >
> > Hi all,
> >
> > As a simple stress test for my board with an MPC8572E and an
MPC8568E
> on
> > it, I setup both processors to boot linux 2.6.27.6 with an NFS root
> and
> > then perform repeated native compiles of a linux kernel over NFS.
> After
> > running for 4 days straight or so with between 250-300 build cycles
> per
> > processor, I stopped the builds and ran ethtool to look for any odd
> > 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
> > concerned about the tx-babbling-errors?  What conditions would cause
> > these errors to be reported?
> >
> > Thanks,
> > Scott
> >
> >
> >
> >
> >
> > ___________________________________________________________________
> >
> >   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 at cyclone.com
> >   U.S.A.                        Web:    http://www.cyclone.com
> > ___________________________________________________________________
> >
> > _______________________________________________
> > Linuxppc-dev mailing list
> > Linuxppc-dev at ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-dev