Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751478AbdH3WGe (ORCPT ); Wed, 30 Aug 2017 18:06:34 -0400 Received: from vps0.lunn.ch ([178.209.37.122]:45831 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750995AbdH3WGd (ORCPT ); Wed, 30 Aug 2017 18:06:33 -0400 Date: Thu, 31 Aug 2017 00:06:31 +0200 From: Andrew Lunn To: Tim Harvey Cc: netdev , Vivien Didelot , "linux-kernel@vger.kernel.org" Subject: Re: DSA mv88e6xxx RX frame errors and TCP/IP RX failure Message-ID: <20170830220631.GM22289@lunn.ch> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 716 Lines: 20 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 front panel RJ45's (lan1-lan4). Hi Tim Can you confirm the counter is this one: /* 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 to prove we are looking in the right place. Andrew