Hi,

After staring at the logs, I noticed that duplicate MAC addresses were
used on the
two zynqmp-zcu102. I believe this is the cause of the intermittent
TFTP termination
problem.

So I made those machines use a unique MAC address. Now this problem has been
resolved.

Sorry for the inconvenience.

Best regards,
Hiraku Toyooka

On Wed, Mar 24, 2021 at 9:12 PM Hiraku Toyooka
<hiraku.toyooka@cybertrust.co.jp> wrote:

Hi,

I found that the TFTP transfer of the kernel was terminated in all
failure cases.
So this is at least not a kernel failure.

For example, https://lava.ciplatform.org/scheduler/job/191862
TFTP from server 192.168.11.5; our IP address is 192.168.11.9
Filename '192436/tftp-deploy-4hdvrfd6/kernel/Image'.
Load address: 0x80000
Loading: *#################################################################
...<snip>...
##################################T T
TFTP server died; starting again

I will continue to investigate the TFTP issue.

Best regards,
Hiraku Toyooka

On Wed, Mar 24, 2021 at 12:22 PM Hiraku Toyooka
<hiraku.toyooka@cybertrust.co.jp> wrote:

Hello Pavel-san,

I'm sorry to give you trouble.
It looks "Infrastructure error" and happens intermittently even in 5.10.
I will investigate the cause.

Failure case: https://lava.ciplatform.org/scheduler/job/191862
Success case(Resubimit): https://lava.ciplatform.org/scheduler/job/192183

For a while, if the same error occurs again, is it possible to
resubmit of the LAVA Job manually (or ignore errors)?

Best regards,
Hiraku Toyooka

On Wed, Mar 24, 2021 at 7:55 AM Pavel Machek <pavel@denx.de> wrote:

Hi!

I'm preparing new 4.19-rt release, and I see tests failing on zynqmp.

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

But they fail on old release, too, and IIRC 4.19 simply does not
support zynqmp.

So I believe this is not a kernel failure. If I'm wrong, let me know.

Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

--
Hiraku Toyooka
Cybertrust Japan Co., Ltd.

--
Hiraku Toyooka
Cybertrust Japan Co., Ltd.

--
Hiraku Toyooka
Cybertrust Japan Co., Ltd.