arm64/renesas test failing for v4.19.148-cip35-rt15 (-rt64)


Pavel Machek
 

Hi!

I got test failure when I submitted -rt branch for testing.

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/197703780

This seems to be "real" failure:

[ 2.791351] asoc-audio-graph-card sound: ASoC: no DMI vendor name!
[ 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.

With no network, it is easy to understand that tests would fail.

x86_siemens, OTOH, seems to be infrastructure error
(bootloader-interrupt timed out after 599 seconds).

Let me investigate it some more.

Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html


Pavel Machek
 

Hi!

I got test failure when I submitted -rt branch for testing.

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/197703780

This seems to be "real" failure:
I re-ran the test with same sources, and failure is still there.

I tried rt+v4.19.147-cip35 -- e8bcfc1349886ef3cf6625a0bc9cd25ddf80112c
-- fails, too.

Let me try commit 1d9c4c7e291d5f49ab07402ef739f98fac6e7adb (tag:
v4.19.144-cip34). ... that one works.

To be sure, let's try older rt commit:
f15040b9d853b9cfbcdd4707d9be2593b42b000b ( v4.19.142-cip33-rt14 /
-rt63). That one works ok.

-rt63-rebase and -rt64-rebase trees have same commits on top.. in
fact, they seem to have same commits. That probably means nothing
changed in -rt. But it looks like there's commit in -stable, touching
relevant area.

commit fb3a780e7a76cf8efb055f8322ec039923cee41f
Author: Yuusuke Ashizuka <ashiduka@fujitsu.com>
Date: Thu Aug 20 18:43:07 2020 +0900

ravb: Fixed to be able to unload modules

Let me investigate some more.

With no network, it is easy to understand that tests would fail.

x86_siemens, OTOH, seems to be infrastructure error
(bootloader-interrupt timed out after 599 seconds).
This one went away when I resubmitted same kernel... so lets ignore it.

Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html