[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM4PR0401MB2260310769B1983FAE5D7814FF010@AM4PR0401MB2260.eurprd04.prod.outlook.com>
Date: Mon, 10 Apr 2017 01:42:21 +0000
From: Andy Duan <fugang.duan@....com>
To: Tim Harvey <tharvey@...eworks.com>, netdev <netdev@...r.kernel.org>
CC: Fabio Estevam <fabio.estevam@....com>,
Lucas Stach <l.stach@...gutronix.de>,
Koen Vandeputte <koen.vandeputte@...ntric.com>
Subject: RE: IMX6 FEC connection drops occasionally with 'MDIO read timeout'
From: Tim Harvey <tharvey@...eworks.com> Sent: Friday, April 07, 2017 10:47 PM
>To: netdev <netdev@...r.kernel.org>
>Cc: Fabio Estevam <fabio.estevam@....com>; Lucas Stach
><l.stach@...gutronix.de>; Andy Duan <fugang.duan@....com>; Koen
>Vandeputte <koen.vandeputte@...ntric.com>
>Subject: IMX6 FEC connection drops occasionally with 'MDIO read timeout'
>
>Greetings,
>
>I've had a couple of users report that they are getting occasional link drops
>when using IMX6 FEC on our boards which are using a Marvell
>88E1510 PHY:
>
>[ 9348.474418] fec 2188000.ethernet eth0: MDIO read timeout [ 9350.478804]
>fec 2188000.ethernet eth0: Link is Down
>
>If they bring the interface back up it works fine.
>
>The most recent version of Linux they have tested and seen this on is
>v4.9 with CONFIG_MARVELL_PHY=y
>
>Has anyone else run into this or know what the issue could be? Should there
>be any retries at the MDIO level or above?
>
>Regards,
>
>Tim
Pls keep ipg clock always on and try it.
In general, MDIO timeout maybe caused by ipg clock off and mii interrupt lost.
Regards,
Andy
Powered by blists - more mailing lists