From: Andrew Lunn <andrew@lunn.ch>
To: Fabio Estevam <festevam@gmail.com>
Cc: Steve Glendinning <steve.glendinning@shawell.net>,
UNGLinuxDriver@microchip.com, netdev <netdev@vger.kernel.org>
Subject: Re: smsc95xx warning after a 'reboot' command
Date: Wed, 2 Mar 2022 23:12:54 +0100 [thread overview]
Message-ID: <Yh/r5hkui6MrV4W6@lunn.ch> (raw)
In-Reply-To: <CAOMZO5ALfFDQjtbQwRiZjAhQnihBNFpmKfLh2t97tJBRQOLbNQ@mail.gmail.com>
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
next prev parent reply other threads:[~2022-03-02 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 21:57 smsc95xx warning after a 'reboot' command Fabio Estevam
2022-03-02 22:12 ` Andrew Lunn [this message]
2022-03-02 23:14 ` Fabio Estevam
2022-03-02 23:50 ` Andrew Lunn
2022-03-03 0:40 ` Fabio Estevam
2022-03-03 2:32 ` Andrew Lunn
2022-03-03 12:56 ` Fabio Estevam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yh/r5hkui6MrV4W6@lunn.ch \
--to=andrew@lunn.ch \
--cc=UNGLinuxDriver@microchip.com \
--cc=festevam@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steve.glendinning@shawell.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox