public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: "Bhola, Bikram" <Bikram_Bhola@mentor.com>,
	Pavel Machek <pavel@denx.de>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: Prompt timeouts on ipc227e board -- randomness related?
Date: Tue, 5 Oct 2021 19:47:25 +0200	[thread overview]
Message-ID: <20211005174725.GA15330@duo.ucw.cz> (raw)
In-Reply-To: <OSZPR01MB68770F80AE64400871800F6EB7AF9@OSZPR01MB6877.jpnprd01.prod.outlook.com>

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

Hi!

> > We investigated the failure job and looks like before getting login prompt job
> > timeout is happening . In the job definition  file - job timeout is mentioned
> > 15mins and  sometimes due to slow network issue, it takes more time while
> > downloading, untar  and deploying image. So we are seeing timeout during
> > login prompt or in some cases in earlier stages also.  The work in progress to
> > double up the network bandwidth within a few weeks, which will reduce the
> > occurrence of this type of issues.
> 
> Thank you for your investigation.
> I've have increased the timeout as you have suggested:
> https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/merge_requests/49
> 
> One additional thing I've noticed, the default x86 character delay during boot is 500ms, which seems a long time inbetween each character sent to the platform
> https://lava.ciplatform.org/scheduler/device/x86-simatic-ipc227e-01/devicedict#defline5
> 
> Has a lower value for boot_character_delay ever been tried?>

Thank you, but that board seems to still have problems:

https://lava.ciplatform.org/scheduler/job/458108


expect-shell-connection: Wait for prompt ['root@ebsy-isar:~#'] (timeout 00:10:00)
Waiting using forced prompt support (timeout 00:05:00)
end: 2.3.5 expect-shell-connection (duration 00:00:00) [common]
start: 2.3.6 export-device-env (timeout 00:01:00) [common]
Sending with 500 millisecond of delay
export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/458108/extract-nfsrootfs-5xpf3q6i'
root@ebsy-isar:~# export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/458108/extract-nfsrootfs-5xpf3q6i'
export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/458108/extract -nfsrootfs-5xpf3q6i'
Sending with 500 millisecond of delay
export NFS_SERVER_IP='134.86.254.28'
export-device-env timed out after 60 seconds
end: 2.3.6 export-device-env (duration 00:01:00) [common]
case: export-device-env
case_id: 9715377
definition: lava

(Of course, I can't rule out kernel problem at the moment, but failing
at setting environment variable would be strange.)

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: "Pavel Machek" <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: "Bhola, Bikram" <Bikram_Bhola@mentor.com>,
	Pavel Machek <pavel@denx.de>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [cip-dev] Prompt timeouts on ipc227e board -- randomness related?
Date: Tue, 5 Oct 2021 19:47:25 +0200	[thread overview]
Message-ID: <20211005174725.GA15330@duo.ucw.cz> (raw)
Message-ID: <20211005174725.xT0_5GFiXCldxxNKHTHSmbAAxFWrRVby84MpVn8uWhY@z> (raw)
In-Reply-To: <OSZPR01MB68770F80AE64400871800F6EB7AF9@OSZPR01MB6877.jpnprd01.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 2274 bytes --]

Hi!

> > We investigated the failure job and looks like before getting login prompt job
> > timeout is happening . In the job definition  file - job timeout is mentioned
> > 15mins and  sometimes due to slow network issue, it takes more time while
> > downloading, untar  and deploying image. So we are seeing timeout during
> > login prompt or in some cases in earlier stages also.  The work in progress to
> > double up the network bandwidth within a few weeks, which will reduce the
> > occurrence of this type of issues.
> 
> Thank you for your investigation.
> I've have increased the timeout as you have suggested:
> https://gitlab.com/cip-project/cip-testing/linux-cip-ci/-/merge_requests/49
> 
> One additional thing I've noticed, the default x86 character delay during boot is 500ms, which seems a long time inbetween each character sent to the platform
> https://lava.ciplatform.org/scheduler/device/x86-simatic-ipc227e-01/devicedict#defline5
> 
> Has a lower value for boot_character_delay ever been tried?>

Thank you, but that board seems to still have problems:

https://lava.ciplatform.org/scheduler/job/458108


expect-shell-connection: Wait for prompt ['root@ebsy-isar:~#'] (timeout 00:10:00)
Waiting using forced prompt support (timeout 00:05:00)
end: 2.3.5 expect-shell-connection (duration 00:00:00) [common]
start: 2.3.6 export-device-env (timeout 00:01:00) [common]
Sending with 500 millisecond of delay
export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/458108/extract-nfsrootfs-5xpf3q6i'
root@ebsy-isar:~# export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/458108/extract-nfsrootfs-5xpf3q6i'
export NFS_ROOTFS='/var/lib/lava/dispatcher/tmp/458108/extract -nfsrootfs-5xpf3q6i'
Sending with 500 millisecond of delay
export NFS_SERVER_IP='134.86.254.28'
export-device-env timed out after 60 seconds
end: 2.3.6 export-device-env (duration 00:01:00) [common]
case: export-device-env
case_id: 9715377
definition: lava

(Of course, I can't rule out kernel problem at the moment, but failing
at setting environment variable would be strange.)

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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

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


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


  parent reply	other threads:[~2021-10-05 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25 20:06 Prompt timeouts on ipc227e board -- randomness related? Pavel Machek
2021-09-25 20:06 ` [cip-dev] " Pavel Machek
2021-09-28 10:08 ` Chris Paterson
2021-09-28 10:08   ` [cip-dev] " Chris Paterson
     [not found]   ` <a34a0fcb84f449ef83e2843bec5a6d02@SVR-IES-MBX-03.mgc.mentorg.com>
2021-10-05 13:41     ` Chris Paterson
2021-10-05 13:41       ` [cip-dev] " Chris Paterson
2021-10-05 17:47       ` Pavel Machek [this message]
2021-10-05 17:47         ` Pavel Machek

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=20211005174725.GA15330@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=Bikram_Bhola@mentor.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    /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