💥 PANICKED: Test report for kernel 5.14.0-rc5 (block, 4e9e1af5)

[CKI Project <cki-project@redhat.com>]

Hello,

We ran automated tests on a recent commit from this kernel tree:

       Kernel repo: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
            Commit: 4e9e1af58800 - Merge branch 'for-5.15/block' into for-next

The results of these automated tests are provided below.

    Overall result: FAILED (see details below)
             Merge: OK
           Compile: OK
             Tests: PANICKED

All kernel binaries, config files, and logs are available for download here:

  https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefix=datawarehouse-public/2021/08/10/351063758

One or more kernel tests failed:

    s390x:
     ❌ LTP

    ppc64le:
     ❌ LTP
     💥 POSIX pjd-fstest suites
     ❌ Loopdev Sanity
     ❌ Memory: fork_mem
     💥 Storage blktests

    aarch64:
     💥 Storage blktests
     ❌ LTP

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:
      make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg

    ppc64le:
      make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg

    s390x:
      make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg

    x86_64:
      make options: make -j24 INSTALL_MOD_STRIP=1 targz-pkg



Hardware testing
----------------
We booted each kernel and ran the following tests:

  aarch64:
    Host 1:
       ✅ Boot test
       ✅ Reboot test
       ✅ xfstests - ext4
       ✅ xfstests - xfs
       ✅ storage: software RAID testing
       ✅ Storage: swraid mdadm raid_module test
       🚧 ❌ xfstests - btrfs
       🚧 💥 Storage blktests
       🚧 ⚡⚡⚡ Storage block - filesystem fio test
       🚧 ⚡⚡⚡ Storage block - queue scheduler test
       🚧 ⚡⚡⚡ Storage nvme - tcp
       🚧 ⚡⚡⚡ stress: stress-ng

    Host 2:
       ✅ Boot test
       ✅ Reboot test
       ✅ ACPI table test
       ❌ LTP
       ⚡⚡⚡ CIFS Connectathon
       ⚡⚡⚡ POSIX pjd-fstest suites
       ⚡⚡⚡ Loopdev Sanity
       ⚡⚡⚡ Memory: fork_mem
       ⚡⚡⚡ Memory function: memfd_create
       ⚡⚡⚡ AMTU (Abstract Machine Test Utility)
       ⚡⚡⚡ Ethernet drivers sanity
       ⚡⚡⚡ storage: SCSI VPD
       🚧 ⚡⚡⚡ xarray-idr-radixtree-test
       🚧 ⚡⚡⚡ NFS Connectathon
       🚧 ⚡⚡⚡ lvm cache test
       🚧 ⚡⚡⚡ lvm snapper test

  ppc64le:
    Host 1:
       ✅ Boot test
       ✅ Reboot test
       ❌ LTP
       ✅ CIFS Connectathon
       💥 POSIX pjd-fstest suites
       ❌ Loopdev Sanity
       ❌ Memory: fork_mem
       ⚡⚡⚡ Memory function: memfd_create
       ⚡⚡⚡ AMTU (Abstract Machine Test Utility)
       ⚡⚡⚡ Ethernet drivers sanity
       🚧 ⚡⚡⚡ xarray-idr-radixtree-test
       🚧 ⚡⚡⚡ NFS Connectathon
       🚧 ⚡⚡⚡ lvm cache test
       🚧 ⚡⚡⚡ lvm snapper test

    Host 2:
       ✅ Boot test
       ✅ Reboot test
       ✅ xfstests - ext4
       ✅ xfstests - xfs
       ✅ storage: software RAID testing
       ✅ Storage: swraid mdadm raid_module test
       🚧 ✅ xfstests - btrfs
       🚧 💥 Storage blktests
       🚧 ⚡⚡⚡ Storage block - filesystem fio test
       🚧 ⚡⚡⚡ Storage block - queue scheduler test
       🚧 ⚡⚡⚡ Storage nvme - tcp
       🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream

  s390x:
    Host 1:
       ✅ Boot test
       ✅ Reboot test
       ❌ LTP
       ✅ CIFS Connectathon
       ✅ POSIX pjd-fstest suites
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ✅ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ✅ Ethernet drivers sanity
       🚧 ❌ xarray-idr-radixtree-test
       🚧 ✅ NFS Connectathon
       🚧 ✅ lvm cache test
       🚧 ✅ lvm snapper test

    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
       ✅ Reboot test
       ✅ Storage: swraid mdadm raid_module test
       🚧 ✅ Storage blktests
       🚧 ✅ Storage nvme - tcp
       🚧 ⚡⚡⚡ stress: stress-ng

  x86_64:
    Host 1:

       ⚡ 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
       ⚡⚡⚡ Reboot test
       ⚡⚡⚡ Storage SAN device stress - qla2xxx driver

    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
       ⚡⚡⚡ Reboot test
       ⚡⚡⚡ Storage SAN device stress - mpt3sas_gen1

    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
       ⚡⚡⚡ Reboot test
       ⚡⚡⚡ xfstests - ext4
       ⚡⚡⚡ xfstests - xfs
       ⚡⚡⚡ xfstests - nfsv4.2
       ⚡⚡⚡ storage: software RAID testing
       ⚡⚡⚡ Storage: swraid mdadm raid_module test
       🚧 ⚡⚡⚡ xfstests - btrfs
       🚧 ⚡⚡⚡ xfstests - cifsv3.11
       🚧 ⚡⚡⚡ Storage blktests
       🚧 ⚡⚡⚡ Storage block - filesystem fio test
       🚧 ⚡⚡⚡ Storage block - queue scheduler test
       🚧 ⚡⚡⚡ Storage nvme - tcp
       🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream
       🚧 ⚡⚡⚡ stress: stress-ng

    Host 4:

       ⚡ 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
       ⚡⚡⚡ Reboot test
       ⚡⚡⚡ Storage SAN device stress - lpfc driver

    Host 5:

       ⚡ 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
       ✅ Reboot test
       ✅ ACPI table test
       ✅ LTP
       ✅ CIFS Connectathon
       ✅ POSIX pjd-fstest suites
       ✅ Loopdev Sanity
       ✅ Memory: fork_mem
       ✅ Memory function: memfd_create
       ✅ AMTU (Abstract Machine Test Utility)
       ✅ Ethernet drivers sanity
       ✅ storage: SCSI VPD
       🚧 ⚡⚡⚡ xarray-idr-radixtree-test
       🚧 ⚡⚡⚡ NFS Connectathon
       🚧 ⚡⚡⚡ lvm cache test
       🚧 ⚡⚡⚡ lvm snapper test

    Host 6:

       ⚡ 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
       ⚡⚡⚡ Reboot test
       ⚡⚡⚡ Storage SAN device stress - qedf driver

    Host 7:
       ✅ Boot test
       ✅ Reboot test
       ✅ Storage SAN device stress - qla2xxx driver

    Host 8:

       ⚡ 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
       ⚡⚡⚡ Reboot test
       ⚡⚡⚡ Storage SAN device stress - qedf driver

  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 ⏱.