[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yh/r5hkui6MrV4W6@lunn.ch>
Date: Wed, 2 Mar 2022 23:12:54 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Fabio Estevam <festevam@...il.com>
Cc: Steve Glendinning <steve.glendinning@...well.net>,
UNGLinuxDriver@...rochip.com, netdev <netdev@...r.kernel.org>
Subject: Re: smsc95xx warning after a 'reboot' command
On Wed, Mar 02, 2022 at 06:57:06PM -0300, Fabio Estevam wrote:
> Hi,
>
> On a imx8mm iotgateway board from Compulab running 5.10 or 5.17-rc the
> following warning is observed after a 'reboot' command:
Just to make sure i'm interpreting this correctly, you are doing a
reboot with the first 20 seconds of the machine starting?
> [ 23.077179] ci_hdrc ci_hdrc.1: remove, state 1
> [ 23.081674] usb usb2: USB disconnect, device number 1
> [ 23.086740] usb 2-1: USB disconnect, device number 2
> [ 23.088393] smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
> [ 23.091718] usb 2-1.1: USB disconnect, device number 3
> [ 23.094090] smsc95xx 2-1.1:1.0 eth1: unregister 'smsc95xx'
> usb-ci_hdrc.1-1.1, smsc95xx USB 2.0 Ethernet
> [ 23.098869] smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
> [ 23.098877] smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
So it looks like the PHY state machine has not been told to stop using
the PHY. That suggests smsc95xx_disconnect_phy() has not been
called. Could you confirm this by putting a printk() in there.
Andrew
Powered by blists - more mailing lists