> # echo -n "2-1" > /sys/bus/usb/drivers/usb/unbind
> usb 2-1.1: USB disconnect, device number 3
> smsc95xx 2-1.1:1.0 eth1: unregister 'smsc95xx' usb-ci_hdrc.1-1.1,
> smsc95xx USB 2.0 Ethernet
> smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
> smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
> *********** smsc95xx_unbind: calling phy_disconnect
> smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
> libphy: *********** phy_disconnect: 1
> libphy: *********** phy_disconnect: 2
> *************** phy_stop
> smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
> smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
> smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
> smsc95xx 2-1.1:1.0 eth1: Failed to read reg index 0x00000114: -19
> smsc95xx 2-1.1:1.0 eth1: Error reading MII_ACCESS
> smsc95xx 2-1.1:1.0 eth1: __smsc95xx_mdio_read: MII is busy
> *********** smsc95xx_stop
> smsc95xx 2-1.1:1.0 eth1: hardware isn't capable of remote wakeup
> usb 2-1.4: USB disconnect, device number 4
>
> Maybe the -19 errors should be ignored?
But why does it return ENODEV? It seems to me, ignoring it is papering
over the cracks. Why cannot we access to the PHY?
Andrew
