From: Pavel Machek <pavel@denx.de>
To: Chris.Paterson2@renesas.com, cip-dev@lists.cip-project.org
Subject: Prompt timeouts on ipc227e board -- randomness related?
Date: Sat, 25 Sep 2021 22:06:25 +0200 [thread overview]
Message-ID: <20210925200625.GA19637@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1775 bytes --]
Hi!
It is not first time I see this failure:
https://lava.ciplatform.org/scheduler/job/444336
[[0;32m OK [0m] Started Login Service.
[[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host keys (7s / no limit)[K[[0;1;31m*[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host keys (8s / no limit)[K[[0;31m*[0;1;31m*[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host keys (9s / no limit)[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (2 of 2) A start job is running for…evices-eth0.device (8s / 1min 30s)[ 19.855328] systemd[1]: apt-daily-upgrade.timer: Adding 3min 2.027476s random time.
[ 19.864207] systemd[1]: apt-daily.timer: Adding 1h 54min 15.794344s random time.
[ 21.406490] systemd[1]: apt-daily-upgrade.timer: Adding 55min 47.041488s random time.
[ 21.415357] systemd[1]: apt-daily.timer: Adding 11h 48min 4.457495s random time.
[ 22.049807] systemd[1]: apt-daily-upgrade.timer: Adding 3min 54.125406s random time.
[ 22.058500] systemd[1]: apt-daily.timer: Adding 8h 34min 47.388595s random time.
[ 22.511646] systemd[1]: apt-daily-upgrade.timer: Adding 25min 13.015405s random time.
[ 22.520510] systemd[1]: apt-daily.timer: Adding 11h 58min 24.212170s random time.
[K[[0;32m OK [0m] Started Regenerate sshd host keys.
wait for prompt timed out
end: 2.3.4.1 login-action (duration 00:00:24) [common]
case: login-action
case_id: 9417066
definition: lava
duration: 23.98
Any idea what is going on there? Is it just a test problem, or do we
have kernel regression that only happens sometimes?
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.Paterson2@renesas.com, cip-dev@lists.cip-project.org
Subject: [cip-dev] Prompt timeouts on ipc227e board -- randomness related?
Date: Sat, 25 Sep 2021 22:06:25 +0200 [thread overview]
Message-ID: <20210925200625.GA19637@duo.ucw.cz> (raw)
Message-ID: <20210925200625.2HihaxZzNEv0N_V-ZIegYgYVAMtuFAPkeXMEksxGkRg@z> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1775 bytes --]
Hi!
It is not first time I see this failure:
https://lava.ciplatform.org/scheduler/job/444336
[[0;32m OK [0m] Started Login Service.
[[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host keys (7s / no limit)[K[[0;1;31m*[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host keys (8s / no limit)[K[[0;31m*[0;1;31m*[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host keys (9s / no limit)[K[ [0;31m*[0;1;31m*[0m[0;31m* [0m] (2 of 2) A start job is running for…evices-eth0.device (8s / 1min 30s)[ 19.855328] systemd[1]: apt-daily-upgrade.timer: Adding 3min 2.027476s random time.
[ 19.864207] systemd[1]: apt-daily.timer: Adding 1h 54min 15.794344s random time.
[ 21.406490] systemd[1]: apt-daily-upgrade.timer: Adding 55min 47.041488s random time.
[ 21.415357] systemd[1]: apt-daily.timer: Adding 11h 48min 4.457495s random time.
[ 22.049807] systemd[1]: apt-daily-upgrade.timer: Adding 3min 54.125406s random time.
[ 22.058500] systemd[1]: apt-daily.timer: Adding 8h 34min 47.388595s random time.
[ 22.511646] systemd[1]: apt-daily-upgrade.timer: Adding 25min 13.015405s random time.
[ 22.520510] systemd[1]: apt-daily.timer: Adding 11h 58min 24.212170s random time.
[K[[0;32m OK [0m] Started Regenerate sshd host keys.
wait for prompt timed out
end: 2.3.4.1 login-action (duration 00:00:24) [common]
case: login-action
case_id: 9417066
definition: lava
duration: 23.98
Any idea what is going on there? Is it just a test problem, or do we
have kernel regression that only happens sometimes?
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 (#6749): https://lists.cip-project.org/g/cip-dev/message/6749
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]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2021-09-25 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 20:06 Pavel Machek [this message]
2021-09-25 20:06 ` [cip-dev] Prompt timeouts on ipc227e board -- randomness related? 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
2021-10-05 17:47 ` [cip-dev] " 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=20210925200625.GA19637@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
/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