Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-31 Thread David Miller
From: Andrew Lunn Date: Thu, 31 Aug 2017 19:41:41 +0200 > Please could you add > > fbbeefdd2104 ("net: fec: Allow reception of frames bigger than 1522 bytes") > > to stable. Queued up, thanks.

Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-31 Thread Andrew Lunn
> > I did fix an issue recently with that. See > > > > commit fbbeefdd21049fcf9437c809da3828b210577f36 > > Author: Andrew Lunn > > Date: Sun Jul 30 19:36:05 2017 +0200 > > > > net: fec: Allow reception of frames bigger than 1522 bytes > > > > The FEC Receive Control Register has a 14 bit

Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-31 Thread Tim Harvey
On Wed, Aug 30, 2017 at 6:46 PM, Andrew Lunn wrote: >> >/* Report late collisions as a frame error. */ >> > if (status & (BD_ENET_RX_NO | BD_ENET_RX_CL)) >> > ndev->stats.rx_frame_errors++; >> > >> > I don't see anywhe

Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-31 Thread Maxim Uvarov
check with ping -s 1500 that packets passed to cpu. mv88e6xxx add additional dsa tag before the frame so small packets can pass and big rejected. also ethtool -S dsaethdevX shows more details stats for Marvell chips. or opposite, lower mtu on cpu to 1400 and check that ping works. So from descrip

Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-30 Thread Andrew Lunn
> >/* Report late collisions as a frame error. */ > > if (status & (BD_ENET_RX_NO | BD_ENET_RX_CL)) > > ndev->stats.rx_frame_errors++; > > > > I don't see anywhere else frame errors are counted, but it would be > > good

Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-30 Thread Ilia Mirkin
On Wed, Aug 30, 2017 at 8:22 PM, Tim Harvey wrote: > On Wed, Aug 30, 2017 at 3:06 PM, Andrew Lunn wrote: >> On Wed, Aug 30, 2017 at 12:53:56PM -0700, Tim Harvey wrote: >>> Greetings, >>> >>> I'm seeing RX frame errors when using the mv88e6xxx DSA driver on >>> 4.13-rc7. The board I'm using is a G

Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-30 Thread Tim Harvey
On Wed, Aug 30, 2017 at 3:06 PM, Andrew Lunn wrote: > On Wed, Aug 30, 2017 at 12:53:56PM -0700, Tim Harvey wrote: >> Greetings, >> >> I'm seeing RX frame errors when using the mv88e6xxx DSA driver on >> 4.13-rc7. The board I'm using is a GW5904 [1] which has an IMX6 FEC >> MAC (eth0) connected via

Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-30 Thread Andrew Lunn
On Wed, Aug 30, 2017 at 12:53:56PM -0700, Tim Harvey wrote: > Greetings, > > I'm seeing RX frame errors when using the mv88e6xxx DSA driver on > 4.13-rc7. The board I'm using is a GW5904 [1] which has an IMX6 FEC > MAC (eth0) connected via RGMII to a MV88E6176 with its downstream > P0/P1/P2/P3 to

DSA mv88e6xxx RX frame errors and TCP/IP RX failure

2017-08-30 Thread Tim Harvey
Greetings, I'm seeing RX frame errors when using the mv88e6xxx DSA driver on 4.13-rc7. The board I'm using is a GW5904 [1] which has an IMX6 FEC MAC (eth0) connected via RGMII to a MV88E6176 with its downstream P0/P1/P2/P3 to front panel RJ45's (lan1-lan4). What I see is the following: - bring up