kernel September 2020

kernel@lists.fedoraproject.org

21 participants
128 discussions

❌ FAIL: Test report for kernel 5.8.6-201.fc32 (fedora-32)
by CKI Project 04 Sep '20

04 Sep '20

Hello jforbes, We ran automated tests on the following kernel build: Kernel package: kernel-5.8.6-201.fc32 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=50733705 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: aarch64: ❌ ACPI table test All kernel binaries, config files, and logs are available for download here: https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=dataware… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ stress: stress-ng 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp Host 2: ✅ Boot test ❌ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ CIFS Connectathon ppc64le: Host 1: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp Host 2: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test 🚧 ⚡⚡⚡ kdump - sysrq-c Host 3: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ CIFS Connectathon Host 4: ✅ Boot test 🚧 ✅ kdump - sysrq-c s390x: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ CIFS Connectathon Host 2: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ Storage blktests 🚧 ❌ Storage nvme - tcp x86_64: Host 1: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity ✅ kernel-rt: rt_migrate_test ✅ kernel-rt: rteval ✅ kernel-rt: sched_deadline ✅ kernel-rt: smidetect 🚧 ✅ CIFS Connectathon Host 2: ✅ Boot test 🚧 ✅ kdump - sysrq-c Host 3: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ stress: stress-ng 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

❌ FAIL: Test report for kernel (ark)
by CKI Project 03 Sep '20

03 Sep '20

Hello, We ran automated tests on a recent commit from this kernel tree: Kernel repo: https://gitlab.com/cki-project/kernel-ark.git Commit: aec6344d1257 - [redhat] kernel-5.9.0-0.rc3.20200904git59126901f200.1 The results of these automated tests are provided below. Overall result: FAILED (see details below) Merge: OK Compile: FAILED All kernel binaries, config files, and logs are available for download here: https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=dataware… We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures: aarch64: FAILED (see build-aarch64.log.xz attachment) ppc64le: FAILED (see build-ppc64le.log.xz attachment) s390x: FAILED (see build-s390x.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment) We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message. Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Compile testing --------------- We compiled the kernel for 4 architectures: aarch64: rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools ppc64le: rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools s390x: rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools x86_64: rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/media
by GitLab Bridge on behalf of jeremycline 03 Sep '20

03 Sep '20

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_VIDEO_IMX214: This is a Video4Linux2 sensor driver for the Sony IMX214 camera. To compile this driver as a module, choose M here: the module will be called imx214. Symbol: VIDEO_IMX214 [=n] Type : tristate Defined at drivers/media/i2c/Kconfig:741 Prompt: Sony IMX214 sensor support Depends on: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m] Visible if: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] Location: -> Device Drivers -> Multimedia support (MEDIA_SUPPORT [=m]) -> Media ancillary drivers -> Camera sensor devices Selects: V4L2_FWNODE [=n] && MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && REGMAP_I2C [=m] --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_VIDEO_IMX214 | 1 + .../generic/CONFIG_VIDEO_IMX214 | 24 ------------------- 2 files changed, 1 insertion(+), 24 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_VIDEO_IMX214 delete mode 100644 redhat/configs/pending-common/generic/CONFIG_VIDEO_IMX214 diff --git a/redhat/configs/common/generic/CONFIG_VIDEO_IMX214 b/redhat/configs/common/generic/CONFIG_VIDEO_IMX214 new file mode 100644 index 000000000000..779d7f97b581 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_VIDEO_IMX214 @@ -0,0 +1 @@ +# CONFIG_VIDEO_IMX214 is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_VIDEO_IMX214 b/redhat/configs/pending-common/generic/CONFIG_VIDEO_IMX214 deleted file mode 100644 index 409e4ed2d5f8..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_VIDEO_IMX214 +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_VIDEO_IMX214: -# -# This is a Video4Linux2 sensor driver for the Sony -# IMX214 camera. -# -# To compile this driver as a module, choose M here: the -# module will be called imx214. -# -# Symbol: VIDEO_IMX214 [=n] -# Type : tristate -# Defined at drivers/media/i2c/Kconfig:741 -# Prompt: Sony IMX214 sensor support -# Depends on: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m] -# Visible if: MEDIA_SUPPORT [=m] && GPIOLIB [=y] && I2C [=y] && VIDEO_V4L2 [=m] && MEDIA_CAMERA_SUPPORT [=y] -# Location: -# -> Device Drivers -# -> Multimedia support (MEDIA_SUPPORT [=m]) -# -> Media ancillary drivers -# -> Camera sensor devices -# Selects: V4L2_FWNODE [=n] && MEDIA_CONTROLLER [=y] && VIDEO_V4L2_SUBDEV_API [=n] && REGMAP_I2C [=m] -# -# -# -# CONFIG_VIDEO_IMX214 is not set -- GitLab

1 0

❌ FAIL: Test report for kernel 5.8.6-200.fc32 (fedora-32)
by CKI Project 03 Sep '20

03 Sep '20

Hello jforbes, We ran automated tests on the following kernel build: Kernel package: kernel-5.8.6-200.fc32 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=50696372 The results of these automated tests are provided below. Overall result: FAILED (see details below) Tests: FAILED One or more kernel tests failed: ppc64le: ❌ LTP All kernel binaries, config files, and logs are available for download here: https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=dataware… Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. For the full detail on our testing procedures, please scroll to the bottom of this message. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Hardware testing ---------------- We booted each kernel and ran the following tests: aarch64: Host 1: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ stress: stress-ng 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp Host 2: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ CIFS Connectathon ppc64le: Host 1: ✅ Boot test ❌ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ CIFS Connectathon Host 2: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp Host 3: ⚡ Internal infrastructure issues prevented one or more tests (marked with ⚡⚡⚡) from running on this architecture. This is not the fault of the kernel that was tested. ⚡⚡⚡ Boot test 🚧 ⚡⚡⚡ kdump - sysrq-c Host 4: ✅ Boot test 🚧 ✅ kdump - sysrq-c s390x: Host 1: ✅ Boot test ✅ stress: stress-ng 🚧 ✅ Storage blktests 🚧 💥 Storage nvme - tcp Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity 🚧 ✅ CIFS Connectathon x86_64: Host 1: ✅ Boot test ✅ xfstests - ext4 ✅ xfstests - xfs ✅ stress: stress-ng 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp Host 2: ✅ Boot test 🚧 ✅ kdump - sysrq-c Host 3: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) ✅ Ethernet drivers sanity ✅ kernel-rt: rt_migrate_test ✅ kernel-rt: rteval ✅ kernel-rt: sched_deadline ✅ kernel-rt: smidetect 🚧 ✅ CIFS Connectathon Test sources: https://gitlab.com/cki-project/kernel-tests 💚 Pull requests are welcome for new tests or improvements to existing tests! Aborted tests ------------- Tests that didn't complete running successfully are marked with ⚡⚡⚡. If this was caused by an infrastructure issue, we try to mark that explicitly in the report. Waived tests ------------ If the test run included waived tests, they are marked with 🚧. Such tests are executed but their results are not taken into account. Tests are waived when their results are not reliable enough, e.g. when they're just introduced or are being fixed. Testing timeout --------------- We aim to provide a report within reasonable timeframe. Tests that haven't finished running yet are marked with ⏱.

1 0

❌ FAIL: Test report for kernel (ark)
by CKI Project 03 Sep '20

03 Sep '20

Hello, We ran automated tests on a recent commit from this kernel tree: Kernel repo: https://gitlab.com/cki-project/kernel-ark.git Commit: 74fc92fa5e88 - [redhat] kernel-5.9.0-0.rc3.20200903gitfc3abb53250a.1 The results of these automated tests are provided below. Overall result: FAILED (see details below) Merge: OK Compile: FAILED All kernel binaries, config files, and logs are available for download here: https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=dataware… We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures: aarch64: FAILED (see build-aarch64.log.xz attachment) ppc64le: FAILED (see build-ppc64le.log.xz attachment) s390x: FAILED (see build-s390x.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment) We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message. Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Compile testing --------------- We compiled the kernel for 4 architectures: aarch64: rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools ppc64le: rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools s390x: rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools x86_64: rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug

1 0

Fedora kernels >= 5.8 have xhci-pci build as a module
by Hans de Goede 02 Sep '20

02 Sep '20

Hi All, 5.8 introduces a new CONFIG_USB_XHCI_PCI_RENESAS Kconfig symbol. The current Fedora kernel config says this to 'm'. I assume that this was done because the help-text suggests that doing so will make support for some special XHCI controllers which need to be "booted" (have firmware loaded) by the kernel modular, while keeping the generic xhci-pci code builtin so that we start probing XHCI USB busses ASAP during boot. But, and this is somewhat of a surprise, the xhci-pci-renesas code does not use the xhci-pci code as a library on top of which it builds. Instead it offers some hooks for the xhci-pci code to call in and having CONFIG_USB_XHCI_PCI_RENESAS set will thus make xhci-pci.ko depend on xhci-pci-renesas.ko. Which means that if xhci-pci-renesas.ko is not builtin, this also forces xhci-pci.ko to not be builtin. As said I assume that this xhci-pci.ko no longer being builtin is not intentional, so that the right way to fix this would be to set CONFIG_USB_XHCI_PCI_RENESAS=y, right ? This problem is leading to some people not being able to enter their disk passwords, see: https://bugzilla.redhat.com/show_bug.cgi?id=1874300 Regards, Hans

3 3

❌ FAIL: Test report for kernel (ark)
by CKI Project 02 Sep '20

02 Sep '20

Hello, We ran automated tests on a recent commit from this kernel tree: Kernel repo: https://gitlab.com/cki-project/kernel-ark.git Commit: e14704555483 - [redhat] kernel-5.9.0-0.rc3.20200902git9c7d619be5a0.1 The results of these automated tests are provided below. Overall result: FAILED (see details below) Merge: OK Compile: FAILED All kernel binaries, config files, and logs are available for download here: https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=dataware… We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures: aarch64: FAILED (see build-aarch64.log.xz attachment) ppc64le: FAILED (see build-ppc64le.log.xz attachment) s390x: FAILED (see build-s390x.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment) We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message. Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Compile testing --------------- We compiled the kernel for 4 architectures: aarch64: rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools ppc64le: rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools s390x: rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools x86_64: rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug

1 0

❌ FAIL: Test report for kernel (ark)
by CKI Project 01 Sep '20

01 Sep '20

Hello, We ran automated tests on a recent commit from this kernel tree: Kernel repo: https://gitlab.com/cki-project/kernel-ark.git Commit: 540ffbeb6593 - [redhat] kernel-5.9.0-0.rc3.20200901gitb51594df17d0.1 The results of these automated tests are provided below. Overall result: FAILED (see details below) Merge: OK Compile: FAILED All kernel binaries, config files, and logs are available for download here: https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=dataware… We attempted to compile the kernel for multiple architectures, but the compile failed on one or more architectures: aarch64: FAILED (see build-aarch64.log.xz attachment) ppc64le: FAILED (see build-ppc64le.log.xz attachment) s390x: FAILED (see build-s390x.log.xz attachment) x86_64: FAILED (see build-x86_64.log.xz attachment) We hope that these logs can help you find the problem quickly. For the full detail on our testing procedures, please scroll to the bottom of this message. Please reply to this email if you have any questions about the tests that we ran or if you have any suggestions on how to make future tests more effective. ,-. ,-. ( C ) ( K ) Continuous `-',-.`-' Kernel ( I ) Integration `-' ______________________________________________________________________________ Compile testing --------------- We compiled the kernel for 4 architectures: aarch64: rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools ppc64le: rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools s390x: rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools x86_64: rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel September 2020