From: "Hiraku Toyooka" <hiraku.toyooka@cybertrust.co.jp>
To: cip-dev@lists.cip-project.org
Cc: pavel@denx.de, Chris.Paterson2@renesas.com,
nobuhiro1.iwamatsu@toshiba.co.jp, masashi.kudo@cybertrust.co.jp,
yoshihiro.okada@cybertrust.co.jp
Subject: Re: [cip-dev] 4.19-rt tests on zynqmp
Date: Wed, 24 Mar 2021 21:12:18 +0900 [thread overview]
Message-ID: <CADPJy8WAk_09zkOgmBK6Ufw5BRM_NkGCReOEy9LEhCJfVtiKiw@mail.gmail.com> (raw)
In-Reply-To: <166F29397571E962.16188@lists.cip-project.org>
[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]
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.
[-- Attachment #2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6325): https://lists.cip-project.org/g/cip-dev/message/6325
Mute This Topic: https://lists.cip-project.org/mt/81564242/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2021-03-24 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 22:54 [cip-dev] 4.19-rt tests on zynqmp Pavel Machek
2021-03-24 3:21 ` Hiraku Toyooka
[not found] ` <166F29397571E962.16188@lists.cip-project.org>
2021-03-24 12:12 ` Hiraku Toyooka [this message]
[not found] ` <166F462C2FF9F4F0.22720@lists.cip-project.org>
2021-04-16 16:11 ` Hiraku Toyooka
2021-04-19 6:48 ` Chris Paterson
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=CADPJy8WAk_09zkOgmBK6Ufw5BRM_NkGCReOEy9LEhCJfVtiKiw@mail.gmail.com \
--to=hiraku.toyooka@cybertrust.co.jp \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=masashi.kudo@cybertrust.co.jp \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@denx.de \
--cc=yoshihiro.okada@cybertrust.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).