Hello!
On 05.10.2020 0:24, Pavel Machek wrote:
It seems
commit fb3a780e7a76cf8efb055f8322ec039923cee41f
Author: Yuusuke Ashizuka <ashid...@fujitsu.com>
Date: Thu Aug 20 18:43:07 2020 +0900
ravb: Fixed to be able to unload modules
causes problems in at least -cip-rt kernels. (I'd have to verify it is
present in -cip and plain -stable). Symptoms are like this:
[ 2.798301] [drm] Cannot find any crtc or sizes
[ 2.805866] hctosys: unable to open rtc device (rtc0)
[ 2.811937] libphy: ravb_mii: probed
[ 2.821001] RTL8211E Gigabit Ethernet e6800000.ethernet-ffffffff:00:
attached PHY driver [RTL8211E Gigabit Ethernet]
(mii_bus:phy_addr=e6800000.ethernet-ffffffff:00, irq=190)
[ 2.838052] RTL8211E Gigabit Ethernet e6800000.ethernet-ffffffff:00:
Master/Slave resolution failed, maybe conflicting manual settings?
[ 12.841484] Waiting up to 110 more seconds for network.
[ 22.853482] Waiting up to 100 more seconds for network.
[ 32.865482] Waiting up to 90 more seconds for network.
[ 42.877482] Waiting up to 80 more seconds for network.
[ 52.889482] Waiting up to 70 more seconds for network.
[ 62.901482] Waiting up to 60 more seconds for network.
[ 72.913482] Waiting up to 50 more seconds for network.
[ 82.925482] Waiting up to 40 more seconds for network.
[ 92.937482] Waiting up to 30 more seconds for network.
[ 102.949482] Waiting up to 20 more seconds for network.
[ 112.961482] Waiting up to 10 more seconds for network.
[ 122.861490] Sending DHCP requests ...... timed out!
[ 209.890289] IP-Config: Retrying forever (NFS root)...
[ 209.895535] libphy: ravb_mii: probed
[ 209.899386] mdio_bus e6800000.ethernet-ffffffff: MDIO device at address 0 is
missing.
[ 209.910604] ravb e6800000.ethernet eth0: failed to connect PHY
[ 209.916705] IP-Config: Failed to open eth0
[ 219.925483] Waiting up to 110 more seconds for network.
[ 229.937481] Waiting up to 100 more seconds for network.
[ 239.949481] Waiting up to 90 more seconds for network.
[ 249.961481] Waiting up to 80 more seconds for network.
Full log is available at
https://lava.ciplatform.org/scheduler/job/56398 .
Reverting the above patch fixes the problems.
Geert has already reverted that patch:
https://patchwork.ozlabs.org/project/netdev/patch/20200922072931.2148-1-geert+rene...@glider.be/
If you have any ideas what could be going on there, let me know.
Unfortunately, I'm unfamiliar with the Realtek PHY driver...
Best regards,
Pavel
MBR, Sergei
