Date   

[isar-cip-core][PATCH 1/9] ci: Select large runner

Jan Kiszka
 

From: Jan Kiszka <jan.kiszka@siemens.com>

Needed since we now have multiple options, and the smaller one is not
even compatible with Isar.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.gitlab-ci.yml | 2 ++
1 file changed, 2 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 9d9ced0..823160f 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -24,6 +24,8 @@ default:

.build_base:
stage: build
+ tags:
+ - large
variables:
base_yaml: "kas-cip.yml:kas/board/${target}.yml"
script:
--
2.26.2


[isar-cip-core][PATCH 4/9] Update Isar revision

Jan Kiszka
 

From: Jan Kiszka <jan.kiszka@siemens.com>

Move to latest master. The only patch we have still applied, could be
replaced by an upstream mechanism now, but that can come separately.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
kas-cip.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kas-cip.yml b/kas-cip.yml
index 9514083..8fb9004 100644
--- a/kas-cip.yml
+++ b/kas-cip.yml
@@ -22,7 +22,7 @@ repos:

isar:
url: https://github.com/ilbers/isar.git
- refspec: cd1327a47a7b00df98eded582aaf5b1ebdd45628
+ refspec: 03124cca669f50b682336a0bdf4ede5a4238e144
layers:
meta:
patches:
--
2.26.2


[isar-cip-core][PATCH 3/9] swupdate: Do not add .ini file to SRC_URI if SWUPDATE_BOOTLOADER is not set

Jan Kiszka
 

From: Jan Kiszka <jan.kiszka@siemens.com>

This prevents false warning during the parsing stage when swupdate is
not used, thus SWUPDATE_BOOTLOADER is not configured.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
recipes-core/swupdate/swupdate.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-core/swupdate/swupdate.bb b/recipes-core/swupdate/swupdate.bb
index 4984a63..8bef9ab 100644
--- a/recipes-core/swupdate/swupdate.bb
+++ b/recipes-core/swupdate/swupdate.bb
@@ -30,7 +30,7 @@ inherit dpkg
inherit swupdate-config

SWUPDATE_ROUND_ROBIN_HANDLER_CONFIG ?= "swupdate.handler.${SWUPDATE_BOOTLOADER}.ini"
-SRC_URI += "file://${SWUPDATE_ROUND_ROBIN_HANDLER_CONFIG}"
+SRC_URI += "${@('file://' + d.getVar('SWUPDATE_ROUND_ROBIN_HANDLER_CONFIG')) if d.getVar('SWUPDATE_BOOTLOADER') else ''}"
KFEATURES += "luahandler"

S = "${WORKDIR}/git"
--
2.26.2


[isar-cip-core][PATCH 2/9] Update to kas 2.5

Jan Kiszka
 

From: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.gitlab-ci.yml | 2 +-
README.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 823160f..2a9ae22 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,4 @@
-image: ghcr.io/siemens/kas/kas-isar:2.3.3
+image: ghcr.io/siemens/kas/kas-isar:2.5

variables:
GIT_STRATEGY: clone
diff --git a/README.md b/README.md
index f038db3..32812a2 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ from scratch.

Install `kas-container` from the [kas project](https://github.com/siemens/kas):

- wget https://raw.githubusercontent.com/siemens/kas/2.3.3/kas-container
+ wget https://raw.githubusercontent.com/siemens/kas/2.5/kas-container
chmod a+x kas-container

Furthermore, install docker and make sure you have required permissions to
--
2.26.2


[isar-cip-core][PATCH 0/9] Varions Updates: bullseye, kernel, kas, isar

Jan Kiszka
 

See patches for Details.

Jan


CC: Quirin Gylstorff <quirin.gylstorff@siemens.com>

Jan Kiszka (9):
ci: Select large runner
Update to kas 2.5
swupdate: Do not add .ini file to SRC_URI if SWUPDATE_BOOTLOADER is
not set
Update Isar revision
conf: Drop no longer needed DISTRO_APT_SOURCES settings
Add bullseye image option
ci: Add bullseye targets
linux-cip: Update to latest releases
wic: Address y2038 warnings of latest Isar

.gitlab-ci.yml | 39 ++++++++++++++++++-
README.md | 2 +-
...ore-buster.conf => cip-core-bullseye.conf} | 6 +--
conf/distro/cip-core-buster.conf | 2 -
conf/distro/cip-core-stretch.conf | 2 -
kas-cip.yml | 2 +-
kas/opt/bullseye.yml | 15 +++++++
recipes-core/swupdate/swupdate.bb | 2 +-
...bb => linux-cip-rt_4.19.195-cip52-rt20.bb} | 2 +-
....bb => linux-cip-rt_4.4.262-cip55-rt34.bb} | 2 +-
...9-cip53.bb => linux-cip_4.19.195-cip52.bb} | 2 +-
...65-cip41.bb => linux-cip_4.4.272-cip58.bb} | 2 +-
wic/bbb.wks | 2 +-
wic/simatic-ipc227e.wks | 2 +-
wic/swupdate-partition.inc | 4 +-
15 files changed, 66 insertions(+), 20 deletions(-)
copy conf/distro/{cip-core-buster.conf => cip-core-bullseye.conf} (64%)
create mode 100644 kas/opt/bullseye.yml
rename recipes-kernel/linux/{linux-cip-rt_4.19.160-cip39-rt17.bb => linux-cip-rt_4.19.195-cip52-rt20.bb} (68%)
rename recipes-kernel/linux/{linux-cip-rt_4.4.244-cip51-rt32.bb => linux-cip-rt_4.4.262-cip55-rt34.bb} (68%)
rename recipes-kernel/linux/{linux-cip_4.4.249-cip53.bb => linux-cip_4.19.195-cip52.bb} (68%)
rename recipes-kernel/linux/{linux-cip_4.19.165-cip41.bb => linux-cip_4.4.272-cip58.bb} (68%)

--
2.26.2


Re: isar-cip-core unhappy with our current runners

Michael Adler
 

Hi Jan,

Shouldn't we add tags to our .gitlab-ci.yml then? The group runners
cannot be individually selected for a repo, thus isar-cip-core will pick
from both, I think.
yes, absolutely!

This is already the case for the kernel CI pipelines, e.g. https://gitlab.com/cip-project/cip-testing/linux-cip-pipelines/raw/master/linux-cip-pipeline.yml

Kind Regards,
Michael

--
Michael Adler

Siemens AG
T RDA IOT SES-DE
Otto-Hahn-Ring 6
81739 München, Deutschland

Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Roland Busch, Vorsitzender; Klaus Helmrich, Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin-Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322


Re: isar-cip-core unhappy with our current runners

Jan Kiszka
 

On 07.07.21 08:14, Michael Adler wrote:
Hi Jan,

maybe someone has a clue: isar-cip-core does not build anymore with the
current runners, see e.g.
yes, I might have a clue: I upgraded the runners to v14 two weeks ago [1]. I have downgraded our runners back to v13
[2]. Please let me know if that does the trick. Then either we found a regression in the v14 runner (which might
already be fixed by now) or we need to adjust the configuration (I have a feeling that the privileged flag is not
propagated correctly).
Yes, looks better again:
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/1404904190

I'm also not sure, given that we have two group runners available now,
if they differ and if isar-cip-core will use the right one. Maybe
additional tags are needed?
I think it was the correct runner. We have a large (tag 'large') and small (tag 'small') runner: The large runner allows
privileged, the small one doesn't (anymore).
Shouldn't we add tags to our .gitlab-ci.yml then? The group runners
cannot be individually selected for a repo, thus isar-cip-core will pick
from both, I think.

Jan

Kind Regards,
Michael

[1] https://gitlab.com/cip-project/cip-testing/gitlab-cloud-ci/-/commit/7920a9105743c96db548c06faac28243d7cd9c96
[2] https://gitlab.com/cip-project/cip-testing/gitlab-cloud-ci/-/commit/6e9b58da1a557be4ca602822ad4b8f23f172a2d3
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


Re: isar-cip-core unhappy with our current runners

Michael Adler
 

Hi Jan,

maybe someone has a clue: isar-cip-core does not build anymore with the
current runners, see e.g.
yes, I might have a clue: I upgraded the runners to v14 two weeks ago [1]. I have downgraded our runners back to v13
[2]. Please let me know if that does the trick. Then either we found a regression in the v14 runner (which might
already be fixed by now) or we need to adjust the configuration (I have a feeling that the privileged flag is not
propagated correctly).

I'm also not sure, given that we have two group runners available now,
if they differ and if isar-cip-core will use the right one. Maybe
additional tags are needed?
I think it was the correct runner. We have a large (tag 'large') and small (tag 'small') runner: The large runner allows
privileged, the small one doesn't (anymore).

Kind Regards,
Michael

[1] https://gitlab.com/cip-project/cip-testing/gitlab-cloud-ci/-/commit/7920a9105743c96db548c06faac28243d7cd9c96
[2] https://gitlab.com/cip-project/cip-testing/gitlab-cloud-ci/-/commit/6e9b58da1a557be4ca602822ad4b8f23f172a2d3

--
Michael Adler

Siemens AG
T RDA IOT SES-DE
Otto-Hahn-Ring 6
81739 München, Deutschland

Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Roland Busch, Vorsitzender; Klaus Helmrich, Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin-Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322


isar-cip-core unhappy with our current runners

Jan Kiszka
 

Hi all,

maybe someone has a clue: isar-cip-core does not build anymore with the
current runners, see e.g.
https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/1401975741:

"update-binfmts: warning: unable to open /proc/sys/fs/binfmt_misc/status
for writing: Permission denied"

I'm also not sure, given that we have two group runners available now,
if they differ and if isar-cip-core will use the right one. Maybe
additional tags are needed?

Did anything change recently?

Jan

--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux


4.4-rt situation

Pavel Machek
 

Hi!

I tried to release 4.4-cip-rt at the end of May, but suitable versions
were not available, and I got nasty-looking rejects when trying to
sort things out.

We decided to (try to) coordinate -cip releases with -rt releases, so
we should get 4.4-cip-rt soon after 4.4-rt is released.

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


Re: cannot push to cip-kernel-sec repository

Masami Ichikawa
 

Hi, Iwamatsu-san

2021年7月2日(金) 8:18 <nobuhiro1.iwamatsu@toshiba.co.jp>:

Hi,

We needed Maintainer role to push master.
So, I update your role from Developer to Maintainer.
Could you re-push to maseter?
Thank you! I could push without any errors.

Best regards,
Nobuhiro

-----Original Message-----
From: Masami Ichikawa [mailto:masami.ichikawa@miraclelinux.com]
Sent: Thursday, July 1, 2021 6:26 PM
To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT) <nobuhiro1.iwamatsu@toshiba.co.jp>
Cc: masashi.kudo@cybertrust.co.jp
Subject: Re: [cip-dev] cannot push to cip-kernel-sec repository

Hi, Iwamatsu-san

Would you mind taking a look it, please?

2021年6月28日(月) 16:53 市川正美 via lists.cip-project.org
<masami.ichikawa=miraclelinux.com@lists.cip-project.org>:

Hi, Iwamatsu-san

When I push commit to the cip-kernel-sec repository, I get the following error.

masami@debian:~/cip/cip-kernel-sec$ git push -u origin master
Enumerating objects: 1557, done.
Counting objects: 100% (1557/1557), done.
Delta compression using up to 2 threads
Compressing objects: 100% (811/811), done.
Writing objects: 100% (811/811), 186.14 KiB | 6.89 MiB/s, done.
Total 811 (delta 742), reused 0 (delta 0)
remote: Resolving deltas: 100% (742/742), completed with 741 local objects.
remote: GitLab: You are not allowed to push code to protected branches
on this project.
To gitlab.com:cip-project/cip-kernel/cip-kernel-sec.git
! [remote rejected] master -> master (pre-receive hook declined)

It looks like I don't have permission to push the master branch.
Would you mind giving me permission to push, please?

Regards,

--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com


Regards,
--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com

Regards,
--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com


Re: cannot push to cip-kernel-sec repository

Nobuhiro Iwamatsu
 

Hi,

We needed Maintainer role to push master.
So, I update your role from Developer to Maintainer.
Could you re-push to maseter?

Best regards,
Nobuhiro

-----Original Message-----
From: Masami Ichikawa [mailto:masami.ichikawa@miraclelinux.com]
Sent: Thursday, July 1, 2021 6:26 PM
To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT) <nobuhiro1.iwamatsu@toshiba.co.jp>
Cc: masashi.kudo@cybertrust.co.jp
Subject: Re: [cip-dev] cannot push to cip-kernel-sec repository

Hi, Iwamatsu-san

Would you mind taking a look it, please?

2021年6月28日(月) 16:53 市川正美 via lists.cip-project.org
<masami.ichikawa=miraclelinux.com@lists.cip-project.org>:

Hi, Iwamatsu-san

When I push commit to the cip-kernel-sec repository, I get the following error.

masami@debian:~/cip/cip-kernel-sec$ git push -u origin master
Enumerating objects: 1557, done.
Counting objects: 100% (1557/1557), done.
Delta compression using up to 2 threads
Compressing objects: 100% (811/811), done.
Writing objects: 100% (811/811), 186.14 KiB | 6.89 MiB/s, done.
Total 811 (delta 742), reused 0 (delta 0)
remote: Resolving deltas: 100% (742/742), completed with 741 local objects.
remote: GitLab: You are not allowed to push code to protected branches
on this project.
To gitlab.com:cip-project/cip-kernel/cip-kernel-sec.git
! [remote rejected] master -> master (pre-receive hook declined)

It looks like I don't have permission to push the master branch.
Would you mind giving me permission to push, please?

Regards,

--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com


Regards,
--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com


Re: cannot push to cip-kernel-sec repository

Masami Ichikawa
 

Hi, Iwamatsu-san

Would you mind taking a look it, please?

2021年6月28日(月) 16:53 市川正美 via lists.cip-project.org
<masami.ichikawa=miraclelinux.com@lists.cip-project.org>:

Hi, Iwamatsu-san

When I push commit to the cip-kernel-sec repository, I get the following error.

masami@debian:~/cip/cip-kernel-sec$ git push -u origin master
Enumerating objects: 1557, done.
Counting objects: 100% (1557/1557), done.
Delta compression using up to 2 threads
Compressing objects: 100% (811/811), done.
Writing objects: 100% (811/811), 186.14 KiB | 6.89 MiB/s, done.
Total 811 (delta 742), reused 0 (delta 0)
remote: Resolving deltas: 100% (742/742), completed with 741 local objects.
remote: GitLab: You are not allowed to push code to protected branches
on this project.
To gitlab.com:cip-project/cip-kernel/cip-kernel-sec.git
! [remote rejected] master -> master (pre-receive hook declined)

It looks like I don't have permission to push the master branch.
Would you mind giving me permission to push, please?

Regards,

--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com


Regards,
--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com


CIP IRC weekly meeting today on libera.chat

masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
 

Hi all,

 

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

 

Please note that we already moved from Freenode to libera.chat, and our channel is the following:

              irc:irc.libera.chat:6667/cip

 

*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting from the first week of Apr. according to TSC meeting*

https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&month=7&day=1&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

 

USWest USEast  UK         DE         TW        JP

02:00     05:00     10:00     11:00     17:00     18:00

 

 

Last meeting minutes:

https://irclogs.baserock.org/meetings/cip/2021/06/cip.2021-06-24-09.00.log.html

 

* Action item

  1. Combine root filesystem with kselftest binary - iwamatsu

  2. Do some experiment to lower burdens on CI - patersonc

  3. Monitor the status of CVE-2021-3444 and CVE-2021-20292 (3/25) - Kernel Team

  4. Update Testing table below with 5.10 info - patersonc

https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/centalisedtesting/cioverview

 

 

* Kernel maintenance updates

* Kernel testing

* AOB

 

The meeting will take 30 min, although it can be extended to an hour if it makes sense and those involved in the topics can stay. Otherwise, the topic will be taken offline or in the next meeting.

 

Best regards,

--

M. Kudo

Cybertrust Japan Co., Ltd.


cannot push to cip-kernel-sec repository

Masami Ichikawa
 

Hi, Iwamatsu-san

When I push commit to the cip-kernel-sec repository, I get the following error.

masami@debian:~/cip/cip-kernel-sec$ git push -u origin master
Enumerating objects: 1557, done.
Counting objects: 100% (1557/1557), done.
Delta compression using up to 2 threads
Compressing objects: 100% (811/811), done.
Writing objects: 100% (811/811), 186.14 KiB | 6.89 MiB/s, done.
Total 811 (delta 742), reused 0 (delta 0)
remote: Resolving deltas: 100% (742/742), completed with 741 local objects.
remote: GitLab: You are not allowed to push code to protected branches
on this project.
To gitlab.com:cip-project/cip-kernel/cip-kernel-sec.git
! [remote rejected] master -> master (pre-receive hook declined)

It looks like I don't have permission to push the master branch.
Would you mind giving me permission to push, please?

Regards,

--
Masami Ichikawa
Cybertrust Japan Co., Ltd.

Email :masami.ichikawa@cybertrust.co.jp
:masami.ichikawa@miraclelinux.com


New security issues

Pavel Machek
 

Hi!

My notes are below. On IRC, I wrongly assumed that "CAN BCM" refers to
some kind of driver. Unfortunately, it is generic code, and it is used
by some of our configs. This is in early stages, it is not even fixed
in Linus' tree at the moment AFAICS.

Best regards,
Pavel

* 2021-06-23

CVE-2021-33624 -- speculative execution on BPF. Fun.

CVE-2021-3609 -- CAN BCM local priviledge
escalation. net/can/bcm.c. local to root. Fun!

CVE-2021-3612 -- drivers/input/joydev.c .

* 2021-06-24

CVE-2021-3600 -- More eBPF issues. 4.19+, hopefully.

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


CVE-2021-3444 and CVE-2021-20292

Pavel Machek
 

Hi!

We have outstanding action item about these two, but at this point I
believe we should simply start monitoring these:

CVE-2021-3444 -- this is about BPF handling. It does not look like
easy backport, and BPF has ton of other issues (especially with
respect to speculative execution), and my recommendation would be to
avoid BPF. My impression is that BPF is not really focus of CIP
project (we may want to ask members if anyone is using it?).

CVE-2021-20292 -- this is basically non issue. First, DRM is not
exactly our focus, but more importantly, this is only issue if
attacker already has root.

quoting: https://bugzilla.redhat.com/show_bug.cgi?id=1939686

There is a flaw reported in ... DRM subsystem. .... An attacker with a
local account with a root privilege, can leverage this vulnerability
to escalate privileges and execute code in the context of the kernel.

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


Re: lab-cip-cybertrust will be temporarily offline

Hiraku Toyooka
 

Hi!

I finally finished physical location change of the lab and zcu102-01 is
online now.

Thank you very much for getting the testing done before going offline.
And I'm sorry for the delay in the restart.

Next, I will online zcu102-02 and bbb-03 tomorrow.

Best regards,
Hiraku Toyooka

On Mon, Jun 21, 2021 at 4:09 PM Chris Paterson
<chris.paterson2@renesas.com> wrote:

Hello Toyooka-san,

From: Hiraku Toyooka <hiraku.toyooka@cybertrust.co.jp>
Sent: 21 June 2021 07:43

Hi.

The lab-cip-cybertrust will be temporarily offline on June 25th due to physical
location change. I'm sorry for the inconvenience.
Thank you for the heads-up.

@nobuhiro1.iwamatsu@toshiba.co.jp, will this cause any issues for the next v4.19-cip release (Friday)?
Can we get the testing done early?

Kind regards, Chris


The schedule is as follows:

June 24th (Thu.) 10:00- (UTC)
- zcu102-02 and bbb-03 will be changed to offline.
- zcu102-01 will be still online.

June 25th (Fri.) 01:00- (UTC)
- zcu102-01 will be changed to offline.
- lab-cip-cybertrust will be changed to offline.

June 25th (Fri.) -10:00 (UTC)
- lab-cip-cybertrust will be changed to online.
- zcu102-01 will be changed to online first.
- zcu102-02 and bbb-03 will be changed to online following zcu102-01
(within a day).

Best regards,
--
Hiraku Toyooka
Cybertrust Japan Co., Ltd.


--
Hiraku Toyooka
Cybertrust Japan Co., Ltd.


cip/linux-4.19.y-cip-rt ltp-ipc: 10 runs, 1 regressions (v4.19.195-cip52-rt20) #kernelci

kernelci.org bot <bot@...>
 

cip/linux-4.19.y-cip-rt ltp-ipc: 10 runs, 1 regressions (v4.19.195-cip52-rt20)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+------------------------------+------------
rk3399-gru-kevin | arm64 | lab-collabora | gcc-8 | defconfig+CON...OMIZE_BASE=y | 1

Details: https://kernelci.org/test/job/cip/branch/linux-4.19.y-cip-rt/kernel/v4.19.195-cip52-rt20/plan/ltp-ipc/

Test: ltp-ipc
Tree: cip
Branch: linux-4.19.y-cip-rt
Describe: v4.19.195-cip52-rt20
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: 7f732dada94956f37e51436f20562ae815aa3bf7

Test suite revisions:
ltp-tests
URL: https://github.com/linux-test-project/ltp.git
SHA: 9dcbf4e96a41ac69842e705d4dea51fc8e7b0860


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
-----------------+-------+---------------+----------+------------------------------+------------
rk3399-gru-kevin | arm64 | lab-collabora | gcc-8 | defconfig+CON...OMIZE_BASE=y | 1

Details: https://kernelci.org/test/plan/id/60d5b99b326f4727b5413268

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: defconfig+CONFIG_RANDOMIZE_BASE=y
Compiler: gcc-8 (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm64/defconfig+CONFIG_RANDOMIZE_BASE=y/gcc-8/lab-collabora/ltp-ipc-rk3399-gru-kevin.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm64/defconfig+CONFIG_RANDOMIZE_BASE=y/gcc-8/lab-collabora/ltp-ipc-rk3399-gru-kevin.html
Rootfs: http://storage.kernelci.org/images/rootfs/debian/buster-ltp/20210520.0/arm64/initrd.cpio.gz


* ltp-ipc.login: https://kernelci.org/test/case/id/60d5b99b326f4727b5413269
new failure (last pass: v4.19.182-cip45-rt19)


cip/linux-4.19.y-cip-rt baseline: 212 runs, 15 regressions (v4.19.195-cip52-rt20) #kernelci

kernelci.org bot <bot@...>
 

cip/linux-4.19.y-cip-rt baseline: 212 runs, 15 regressions (v4.19.195-cip52-rt20)

Regressions Summary
-------------------

platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
qemu_arm-versatilepb | arm | lab-baylibre | gcc-8 | versatile_defconfig | 1
qemu_arm-versatilepb | arm | lab-broonie | gcc-8 | versatile_defconfig | 1
qemu_arm-versatilepb | arm | lab-cip | gcc-8 | versatile_defconfig | 1
qemu_arm-versatilepb | arm | lab-collabora | gcc-8 | versatile_defconfig | 1
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defconfig | 3
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defc...CONFIG_SMP=n | 4
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defc...G_ARM_LPAE=y | 3
tegra124-nyan-big | arm | lab-collabora | gcc-8 | tegra_defconfig | 1

Details: https://kernelci.org/test/job/cip/branch/linux-4.19.y-cip-rt/kernel/v4.19.195-cip52-rt20/plan/baseline/

Test: baseline
Tree: cip
Branch: linux-4.19.y-cip-rt
Describe: v4.19.195-cip52-rt20
URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
SHA: 7f732dada94956f37e51436f20562ae815aa3bf7


Test Regressions
----------------


platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
qemu_arm-versatilepb | arm | lab-baylibre | gcc-8 | versatile_defconfig | 1

Details: https://kernelci.org/test/plan/id/60d5b5ba7f11036c4d41329b

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: versatile_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-baylibre/baseline-qemu_arm-versatilepb.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-baylibre/baseline-qemu_arm-versatilepb.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.login: https://kernelci.org/test/case/id/60d5b5ba7f11036c4d41329c
failing since 208 days (last pass: v4.19.152-cip37-rt16, first fail: v4.19.160-cip39-rt17)



platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
qemu_arm-versatilepb | arm | lab-broonie | gcc-8 | versatile_defconfig | 1

Details: https://kernelci.org/test/plan/id/60d5b5b67f11036c4d413283

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: versatile_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-broonie/baseline-qemu_arm-versatilepb.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-broonie/baseline-qemu_arm-versatilepb.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.login: https://kernelci.org/test/case/id/60d5b5b67f11036c4d413284
failing since 208 days (last pass: v4.19.152-cip37-rt16, first fail: v4.19.160-cip39-rt17)



platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
qemu_arm-versatilepb | arm | lab-cip | gcc-8 | versatile_defconfig | 1

Details: https://kernelci.org/test/plan/id/60d5b5a47f11036c4d41326b

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: versatile_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-cip/baseline-qemu_arm-versatilepb.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-cip/baseline-qemu_arm-versatilepb.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.login: https://kernelci.org/test/case/id/60d5b5a47f11036c4d41326c
failing since 208 days (last pass: v4.19.152-cip37-rt16, first fail: v4.19.160-cip39-rt17)



platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
qemu_arm-versatilepb | arm | lab-collabora | gcc-8 | versatile_defconfig | 1

Details: https://kernelci.org/test/plan/id/60d5c2bc305a0999fd41328d

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: versatile_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-collabora/baseline-qemu_arm-versatilepb.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/versatile_defconfig/gcc-8/lab-collabora/baseline-qemu_arm-versatilepb.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.login: https://kernelci.org/test/case/id/60d5c2bc305a0999fd41328e
failing since 208 days (last pass: v4.19.152-cip37-rt16, first fail: v4.19.160-cip39-rt17)



platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defconfig | 3

Details: https://kernelci.org/test/plan/id/60d5bce7ab08fc4ff54132ba

Results: 63 PASS, 6 FAIL, 0 SKIP
Full config: multi_v7_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/multi_v7_defconfig/gcc-8/lab-collabora/baseline-rk3288-veyron-jaq.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/multi_v7_defconfig/gcc-8/lab-collabora/baseline-rk3288-veyron-jaq.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.bootrr.dwmmc_rockchip-sdmmc-probed: https://kernelci.org/test/case/id/60d5bce7ab08fc4ff54132d6
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:24:15.340988 /lava-4093696/1/../bin/lava-test-case
2021-06-25T11:24:15.346193 <8>[ 14.976518] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=dwmmc_rockchip-sdmmc-probed RESULT=fail>

* baseline.bootrr.dwmmc_rockchip-sdio0-probed: https://kernelci.org/test/case/id/60d5bce7ab08fc4ff54132d7
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:24:16.359788 /lava-4093696/1/../bin/lava-test-case
2021-06-25T11:24:16.377953 <8>[ 15.996046] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=dwmmc_rockchip-sdio0-probed RESULT=fail>
2021-06-25T11:24:16.378465 /lava-4093696/1/../bin/lava-test-case

* baseline.bootrr.rockchip-iodomain-grf-probed: https://kernelci.org/test/case/id/60d5bce7ab08fc4ff54132f0
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:24:18.802652 /lava-4093696/1/../bin/lava-test-case
2021-06-25T11:24:18.819852 <8>[ 18.439161] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=rockchip-iodomain-grf-probed RESULT=fail>
2021-06-25T11:24:18.820396 /lava-4093696/1/../bin/lava-test-case



platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defc...CONFIG_SMP=n | 4

Details: https://kernelci.org/test/plan/id/60d5c2aa358250f0ae41327c

Results: 62 PASS, 7 FAIL, 0 SKIP
Full config: multi_v7_defconfig+CONFIG_SMP=n
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-8/lab-collabora/baseline-rk3288-veyron-jaq.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/multi_v7_defconfig+CONFIG_SMP=n/gcc-8/lab-collabora/baseline-rk3288-veyron-jaq.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.bootrr.cros-ec-keyb-probed: https://kernelci.org/test/case/id/60d5c2aa358250f0ae413289
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:48:47.558821 /lava-4093742/1/../bin/lava-test-case<8>[ 15.124968] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=cros-ec-keyb-probed RESULT=fail>

* baseline.bootrr.dwmmc_rockchip-sdmmc-probed: https://kernelci.org/test/case/id/60d5c2aa358250f0ae413298
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:48:48.835712 /lava-4093742/1/../bin/lava-test-case<8>[ 16.396393] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=dwmmc_rockchip-sdmmc-probed RESULT=fail>
2021-06-25T11:48:48.836345

* baseline.bootrr.dwmmc_rockchip-sdio0-probed: https://kernelci.org/test/case/id/60d5c2aa358250f0ae413299
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:48:49.865802 /lava-4093742/1/../bin/lava-test-case<8>[ 17.415410] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=dwmmc_rockchip-sdio0-probed RESULT=fail>
2021-06-25T11:48:49.866323

* baseline.bootrr.rockchip-iodomain-grf-probed: https://kernelci.org/test/case/id/60d5c2aa358250f0ae4132b2
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:48:52.286433 /lava-4093742/1/../bin/lava-test-case<8>[ 19.850885] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=rockchip-iodomain-grf-probed RESULT=fail>
2021-06-25T11:48:52.287036



platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
rk3288-veyron-jaq | arm | lab-collabora | gcc-8 | multi_v7_defc...G_ARM_LPAE=y | 3

Details: https://kernelci.org/test/plan/id/60d5c356b2cb9f0a46413276

Results: 63 PASS, 6 FAIL, 0 SKIP
Full config: multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y/gcc-8/lab-collabora/baseline-rk3288-veyron-jaq.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/multi_v7_defconfig+CONFIG_EFI=y+CONFIG_ARM_LPAE=y/gcc-8/lab-collabora/baseline-rk3288-veyron-jaq.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.bootrr.dwmmc_rockchip-sdmmc-probed: https://kernelci.org/test/case/id/60d5c356b2cb9f0a46413292
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:51:43.022548 /lava-4093790/1/../bin/lava-test-case
2021-06-25T11:51:43.028128 <8>[ 14.079034] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=dwmmc_rockchip-sdmmc-probed RESULT=fail>

* baseline.bootrr.dwmmc_rockchip-sdio0-probed: https://kernelci.org/test/case/id/60d5c356b2cb9f0a46413293
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:51:44.058673 /lava-4093790/1/../bin/lava-test-case<8>[ 15.098328] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=dwmmc_rockchip-sdio0-probed RESULT=fail>
2021-06-25T11:51:44.059102
2021-06-25T11:51:44.059367 /lava-4093790/1/../bin/lava-test-case

* baseline.bootrr.rockchip-iodomain-grf-probed: https://kernelci.org/test/case/id/60d5c356b2cb9f0a464132ac
new failure (last pass: v4.19.182-cip45-rt19)

2021-06-25T11:51:46.483621 /lava-4093790/1/../bin/lava-test-case
2021-06-25T11:51:46.499347 <8>[ 17.539516] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=rockchip-iodomain-grf-probed RESULT=fail>
2021-06-25T11:51:46.499616 /lava-4093790/1/../bin/lava-test-case



platform | arch | lab | compiler | defconfig | regressions
---------------------+------+---------------+----------+------------------------------+------------
tegra124-nyan-big | arm | lab-collabora | gcc-8 | tegra_defconfig | 1

Details: https://kernelci.org/test/plan/id/60d5be3acc3f4d18264132c3

Results: 0 PASS, 1 FAIL, 0 SKIP
Full config: tegra_defconfig
Compiler: gcc-8 (arm-linux-gnueabihf-gcc (Debian 8.3.0-2) 8.3.0)
Plain log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/tegra_defconfig/gcc-8/lab-collabora/baseline-tegra124-nyan-big.txt
HTML log: https://storage.kernelci.org//cip/linux-4.19.y-cip-rt/v4.19.195-cip52-rt20/arm/tegra_defconfig/gcc-8/lab-collabora/baseline-tegra124-nyan-big.html
Rootfs: http://storage.kernelci.org/images/rootfs/buildroot/kci-2020.05-5-g2f114cc7102b/armel/baseline/rootfs.cpio.gz


* baseline.login: https://kernelci.org/test/case/id/60d5be3acc3f4d18264132c4
new failure (last pass: v4.19.160-cip39-rt17)

461 - 480 of 7061