From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: Marvell phy errata origins? Date: Tue, 25 Sep 2018 17:39:16 +0200 Message-ID: <20180925153916.GD1676@lunn.ch> References: <59691a35-a89c-f9ca-c7b0-73134a737f4c@cisco.com> <20170418140450.GB13724@lunn.ch> <84bfdc12-800c-2f63-3eff-416cf560e18c@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florian Fainelli , Andy Fleming , Harini Katakam , "netdev@vger.kernel.org" , HEMANT RAMDASI , "Julius Hemanth Pitti -X (jpitti - MONTA VISTA SOFTWARE INC at Cisco)" , "GokulChand Casheekar (gcasheek)" To: Daniel Walker Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:45218 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729438AbeIYVrY (ORCPT ); Tue, 25 Sep 2018 17:47:24 -0400 Content-Disposition: inline In-Reply-To: <84bfdc12-800c-2f63-3eff-416cf560e18c@cisco.com> Sender: netdev-owner@vger.kernel.org List-ID: > I hope this this thread isn't too old to bring back to life. So it seems > that Harini found that m88e1111 did not need this errata, and Cisco > previously found that Harini's patch fixed m88e1112, we included it > internally for that reason > > Now I'm getting reports that this errata fixes issues we're seeing on > m88e1111. We see an interrupt storm without the errata, despite the errata > not being defined in the datasheet. Is everybody actually using interrupts? It could be in one system phylib is polling. When you get an interrupt storm, which interrupt bit is not cleared by reading the ievent register? Andrew