From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B8C45C433E0 for ; Sat, 11 Jul 2020 16:23:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9CF6C207DD for ; Sat, 11 Jul 2020 16:23:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728559AbgGKQXy (ORCPT ); Sat, 11 Jul 2020 12:23:54 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:58598 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728441AbgGKQXx (ORCPT ); Sat, 11 Jul 2020 12:23:53 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1juII1-004dcq-1V; Sat, 11 Jul 2020 18:23:49 +0200 Date: Sat, 11 Jul 2020 18:23:49 +0200 From: Andrew Lunn To: Martin Rowe Cc: netdev@vger.kernel.org, davem@davemloft.net, vivien.didelot@gmail.com, linux@armlinux.org.uk Subject: Re: bug: net: dsa: mv88e6xxx: unable to tx or rx with Clearfog GT 8K (with git bisect) Message-ID: <20200711162349.GL1014141@lunn.ch> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Sat, Jul 11, 2020 at 01:50:21PM +0000, Martin Rowe wrote: > Hello, > > I hope this is the right forum. > > I have been troubleshooting an issue with my Clearfog GT 8Ks where I > am unable to tx or rx on the switch interface, which uses the > mv88e6xxx driver. Based on git bisect, I believe it is related to > commit 34b5e6a33c1a8e466c3a73fd437f66fb16cb83ea from around the > 5.7-rc2 era. Hi Martin Thanks for the bug report. > Symptoms: > The interface used to work, then it stopped and I didn't immediately > notice because of life. Now the network never comes fully up. dmesg > indicates no issues bringing the device up. Links are brought up and > down with cable connects and disconnects. Negotiation seems to be > working. But the interface rx counter never increases. While the tx > counters do increase, tcpdumps on the other end of the cables never > see any traffic. Basically, it doesn't look like any traffic is going > out or in. So i'm guessing it is the connection between the CPU and the switch. Could you confirm this? Create a bridge, add two ports of the switch to the bridge, and then see if packets can pass between switch ports. If it is the connection between the CPU and the switch, i would then be thinking about the comphy and the firmware. We have seen issues where the firmware is too old. That is not something i've debugged myself, so i don't know where the version information is, or what version is required. Andrew