All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Paterson" <chris.paterson2@renesas.com>
To: Pavel Machek <pavel@denx.de>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Cc: "Bhola, Bikram" <Bikram_Bhola@mentor.com>
Subject: Re: [cip-dev] Siemens board failed to boot testing 5.10
Date: Thu, 28 Jan 2021 10:31:27 +0000	[thread overview]
Message-ID: <OSAPR01MB2385C955D107D632983E7112B7BA9@OSAPR01MB2385.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20210126115431.GA28355@amd>

[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]

Hello,

> From: Pavel Machek <pavel@denx.de>
> Sent: 26 January 2021 11:55
>
> Hi!
>
> > >> Something went wrong on siemens board... I'll try to resubmit the job.
> > >>
> > >> https://lava.ciplatform.org/scheduler/job/148648#L266
> > >
> > > It still fails. https://lava.ciplatform.org/scheduler/job/148674. I'll
> > > retry one more time, but this looks like permanent problem.
> > >
> >
> > Do you mean the board does not come up with any job, or just with 5.10?
> > Doesn't it react at all (dead hw)?
>
> I don't believe it is dead hw.
>
> > And where is this one located? We have IPC227E at Mentor and at Denx
> now.

It seems a bit random as to which tests fail.
We have three boards and most of the time they pass the 5.10 tests, but sometimes they fail.

With all three of our IPC227E boards we randomly have issues getting the serial connection to work, or sometimes another issue prevents booting.
Even our healthchecks randomly fail.
So obviously there is still some work to do to get testing on these boards to be reliable.

You can see the status of the latest tests on these devices here:
https://lava.ciplatform.org/scheduler/device_type/x86-simatic-ipc227e?dt_length=100

So in short
- There isn't an issue caused by a specific Kernel version
- We need to work out why the IPC227E boards aren't "stable" in our LAVA environment

Kind regards, Chris

>
> I'm sorry, I don't know much about test infrastructure.
>
> 5.10.11-rc2 tests passed okay, but I'm not sure if it has any
> implications.
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-
> 5.10.y
>
> Best regards,
>                                                               Pavel
> --
> DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6149): https://lists.cip-project.org/g/cip-dev/message/6149
Mute This Topic: https://lists.cip-project.org/mt/80114267/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


      reply	other threads:[~2021-01-28 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 20:17 [cip-dev] Siemens board failed to boot testing 5.10 Pavel Machek
2021-01-25 20:44 ` Pavel Machek
2021-01-26 11:06   ` Jan Kiszka
2021-01-26 11:54     ` Pavel Machek
2021-01-28 10:31       ` Chris Paterson [this message]

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=OSAPR01MB2385C955D107D632983E7112B7BA9@OSAPR01MB2385.jpnprd01.prod.outlook.com \
    --to=chris.paterson2@renesas.com \
    --cc=Bikram_Bhola@mentor.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=pavel@denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.