From: Veronika Kabatova <vkabatov@redhat.com>
To: Linux Stable maillist <stable@vger.kernel.org>
Cc: Xiong Zhou <xzhou@redhat.com>
Subject: Re: 💥 PANICKED: Test report for kernel 5.7.9-rc1-c2fb28a.cki (stable)
Date: Wed, 15 Jul 2020 09:36:44 -0400 (EDT) [thread overview]
Message-ID: <2125467353.2778784.1594820204666.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <cki.9BE0703C38.BLD1GT3V8U@redhat.com>
----- Original Message -----
> From: "CKI Project" <cki-project@redhat.com>
> To: "Linux Stable maillist" <stable@vger.kernel.org>
> Cc: "Xiong Zhou" <xzhou@redhat.com>
> Sent: Wednesday, July 15, 2020 3:33:45 PM
> Subject: 💥 PANICKED: Test report for kernel 5.7.9-rc1-c2fb28a.cki (stable)
>
>
> Hello,
>
> We ran automated tests on a recent commit from this kernel tree:
>
> Kernel repo:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> Commit: c2fb28a4b6e4 - Linux 5.7.9-rc1
>
> 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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawarehouse/2020/07/14/610210
>
> One or more kernel tests failed:
>
> s390x:
> ❌ Boot test
> ❌ Boot test
> 💥 Boot test
>
Hi,
we started observing boot panics with 5.7 on s390x yesterday:
[ 0.388965] Kernel panic - not syncing: Corrupted kernel text
[ 0.388970] CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.7.8-0930ce5.cki #1
[ 0.388971] Hardware name: IBM 2964 N96 400 (z/VM 6.4.0)
[ 0.388975] Workqueue: events timer_update_keys
[ 0.388977] Call Trace:
[ 0.388980] [<00000001378c868a>] show_stack+0x8a/0xd0
[ 0.388983] [<0000000137e0c9c2>] dump_stack+0x8a/0xb8
[ 0.388985] [<00000001378fa372>] panic+0x112/0x308
[ 0.388989] [<00000001378d20b6>] jump_label_bug+0x7e/0x80
[ 0.388990] [<00000001378d1fb8>] __jump_label_transform+0xa8/0xd8
[ 0.388992] [<00000001378d200e>] arch_jump_label_transform+0x26/0x40
[ 0.388995] [<0000000137a8d448>] __jump_label_update+0xb8/0x128
[ 0.388996] [<0000000137a8dca6>] static_key_enable_cpuslocked+0x8e/0xd0
[ 0.388998] [<0000000137a8dd18>] static_key_enable+0x30/0x40
[ 0.389000] [<000000013798a0d2>] timer_update_keys+0x3a/0x50
[ 0.389003] [<000000013791cdde>] process_one_work+0x206/0x458
[ 0.389005] [<000000013791d078>] worker_thread+0x48/0x460
[ 0.389007] [<0000000137924912>] kthread+0x12a/0x160
[ 0.389013] [<00000001381b9a70>] ret_from_fork+0x2c/0x30
I only released one of the reports to not spam too much but the panics are
still happening with the most recent code.
These panics are NOT present on the current mainline. All other arches are OK.
Given the call trace, I'm guessing it is something related to
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-5.7.y&id=477d4930b0c7e70c1ac3e3c35e5ad15c5ebde8be
Veronika
> ppc64le:
> ❌ Loopdev Sanity
>
> aarch64:
> ❌ Loopdev Sanity
>
> x86_64:
> ❌ Loopdev Sanity
>
[We're still investigating these, feel free to ignore for now.]
> 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: -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> ppc64le:
> make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> s390x:
> make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> x86_64:
> make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
>
>
> Hardware testing
> ----------------
> We booted each kernel and ran the following tests:
>
> aarch64:
> Host 1:
> ✅ Boot test
> ✅ ACPI table test
> ✅ ACPI enabled test
> ✅ Podman system integration test - as root
> ✅ Podman system integration test - as user
> ✅ LTP
> ❌ Loopdev Sanity
> ✅ Memory function: memfd_create
> ✅ AMTU (Abstract Machine Test Utility)
> ✅ Networking bridge: sanity
> ✅ Ethernet drivers sanity
> ✅ Networking socket: fuzz
> ✅ Networking: igmp conformance test
> ✅ Networking route: pmtu
> ✅ Networking route_func - local
> ✅ Networking route_func - forward
> ✅ Networking TCP: keepalive test
> ✅ Networking UDP: socket
> ✅ Networking tunnel: geneve basic test
> ✅ Networking tunnel: gre basic
> ✅ L2TP basic test
> ✅ Networking tunnel: vxlan basic
> ✅ Networking ipsec: basic netns - transport
> ✅ Networking ipsec: basic netns - tunnel
> ✅ Libkcapi AF_ALG test
> ✅ pciutils: update pci ids test
> ✅ ALSA PCM loopback test
> ✅ ALSA Control (mixer) Userspace Element test
> ✅ storage: SCSI VPD
> 🚧 ✅ CIFS Connectathon
> 🚧 ✅ POSIX pjd-fstest suites
> 🚧 ✅ jvm - DaCapo Benchmark Suite
> 🚧 ✅ jvm - jcstress tests
> 🚧 ✅ Memory function: kaslr
> 🚧 ✅ Networking firewall: basic netfilter test
> 🚧 ✅ audit: audit testsuite test
> 🚧 ✅ trace: ftrace/tracer
> 🚧 ✅ kdump - kexec_boot
>
> Host 2:
> ✅ Boot test
> ✅ xfstests - ext4
> ✅ xfstests - xfs
> ✅ selinux-policy: serge-testsuite
> ✅ storage: software RAID testing
> ✅ stress: stress-ng
> 🚧 ✅ IPMI driver test
> 🚧 ✅ IPMItool loop stress test
> 🚧 ✅ Storage blktests
>
> ppc64le:
> Host 1:
> ✅ Boot test
> ✅ xfstests - ext4
> ✅ xfstests - xfs
> ✅ selinux-policy: serge-testsuite
> ✅ storage: software RAID testing
> 🚧 ✅ IPMI driver test
> 🚧 ✅ IPMItool loop stress test
> 🚧 ✅ Storage blktests
>
> Host 2:
> ✅ Boot test
> 🚧 ✅ kdump - sysrq-c
>
> Host 3:
> ✅ Boot test
> ✅ Podman system integration test - as root
> ✅ Podman system integration test - as user
> ✅ LTP
> ❌ Loopdev Sanity
> ✅ Memory function: memfd_create
> ✅ AMTU (Abstract Machine Test Utility)
> ✅ Networking bridge: sanity
> ✅ Ethernet drivers sanity
> ✅ Networking socket: fuzz
> ✅ Networking route: pmtu
> ✅ Networking route_func - local
> ✅ Networking route_func - forward
> ✅ Networking TCP: keepalive test
> ✅ Networking UDP: socket
> ✅ Networking tunnel: geneve basic test
> ✅ Networking tunnel: gre basic
> ✅ L2TP basic test
> ✅ Networking tunnel: vxlan basic
> ✅ Networking ipsec: basic netns - tunnel
> ✅ Libkcapi AF_ALG test
> ✅ pciutils: update pci ids test
> ✅ ALSA PCM loopback test
> ✅ ALSA Control (mixer) Userspace Element test
> 🚧 ✅ CIFS Connectathon
> 🚧 ✅ POSIX pjd-fstest suites
> 🚧 ✅ jvm - DaCapo Benchmark Suite
> 🚧 ✅ jvm - jcstress tests
> 🚧 ✅ Memory function: kaslr
> 🚧 ✅ Networking firewall: basic netfilter test
> 🚧 ✅ audit: audit testsuite test
> 🚧 ✅ trace: ftrace/tracer
>
> s390x:
> Host 1:
> ❌ Boot test
> ⚡⚡⚡ selinux-policy: serge-testsuite
> ⚡⚡⚡ stress: stress-ng
> 🚧 ⚡⚡⚡ Storage blktests
>
> Host 2:
> ❌ Boot test
> 🚧 ⚡⚡⚡ kdump - sysrq-c
> 🚧 ⚡⚡⚡ kdump - file-load
>
> Host 3:
> ❌ Boot test
> ⚡⚡⚡ Podman system integration test - as root
> ⚡⚡⚡ Podman system integration test - as user
> ⚡⚡⚡ LTP
> ⚡⚡⚡ Loopdev Sanity
> ⚡⚡⚡ Memory function: memfd_create
> ⚡⚡⚡ Networking bridge: sanity
> ⚡⚡⚡ Ethernet drivers sanity
> ⚡⚡⚡ Networking route: pmtu
> ⚡⚡⚡ Networking route_func - local
> ⚡⚡⚡ Networking route_func - forward
> ⚡⚡⚡ Networking TCP: keepalive test
> ⚡⚡⚡ Networking UDP: socket
> ⚡⚡⚡ Networking tunnel: geneve basic test
> ⚡⚡⚡ Networking tunnel: gre basic
> ⚡⚡⚡ L2TP basic test
> ⚡⚡⚡ Networking tunnel: vxlan basic
> ⚡⚡⚡ Networking ipsec: basic netns - transport
> ⚡⚡⚡ Networking ipsec: basic netns - tunnel
> ⚡⚡⚡ Libkcapi AF_ALG test
> 🚧 ⚡⚡⚡ CIFS Connectathon
> 🚧 ⚡⚡⚡ POSIX pjd-fstest suites
> 🚧 ⚡⚡⚡ jvm - DaCapo Benchmark Suite
> 🚧 ⚡⚡⚡ jvm - jcstress tests
> 🚧 ⚡⚡⚡ Memory function: kaslr
> 🚧 ⚡⚡⚡ Networking firewall: basic netfilter test
> 🚧 ⚡⚡⚡ audit: audit testsuite test
> 🚧 ⚡⚡⚡ trace: ftrace/tracer
> 🚧 ⚡⚡⚡ kdump - kexec_boot
>
> x86_64:
> Host 1:
> ✅ Boot test
> ✅ xfstests - ext4
> ✅ xfstests - xfs
> ✅ selinux-policy: serge-testsuite
> ✅ storage: software RAID testing
> ✅ stress: stress-ng
> 🚧 ✅ CPU: Frequency Driver Test
> 🚧 ✅ CPU: Idle Test
> 🚧 ✅ IOMMU boot test
> 🚧 ✅ IPMI driver test
> 🚧 ✅ IPMItool loop stress test
> 🚧 ✅ power-management: cpupower/sanity test
> 🚧 ✅ Storage blktests
>
> Host 2:
> ✅ Boot test
> ✅ ACPI table test
> ✅ Podman system integration test - as root
> ✅ Podman system integration test - as user
> ✅ LTP
> ❌ Loopdev Sanity
> ✅ Memory function: memfd_create
> ✅ AMTU (Abstract Machine Test Utility)
> ✅ Networking bridge: sanity
> ✅ Ethernet drivers sanity
> ✅ Networking socket: fuzz
> ✅ Networking: igmp conformance test
> ✅ Networking route: pmtu
> ✅ Networking route_func - local
> ✅ Networking route_func - forward
> ✅ Networking TCP: keepalive test
> ✅ Networking UDP: socket
> ✅ Networking tunnel: geneve basic test
> ✅ Networking tunnel: gre basic
> ✅ L2TP basic test
> ✅ Networking tunnel: vxlan basic
> ✅ Networking ipsec: basic netns - transport
> ✅ Networking ipsec: basic netns - tunnel
> ✅ Libkcapi AF_ALG test
> ✅ pciutils: sanity smoke test
> ✅ pciutils: update pci ids test
> ✅ ALSA PCM loopback test
> ✅ ALSA Control (mixer) Userspace Element test
> ✅ storage: SCSI VPD
> 🚧 ✅ CIFS Connectathon
> 🚧 ✅ POSIX pjd-fstest suites
> 🚧 ✅ jvm - DaCapo Benchmark Suite
> 🚧 ✅ jvm - jcstress tests
> 🚧 ✅ Memory function: kaslr
> 🚧 ✅ Networking firewall: basic netfilter test
> 🚧 ✅ audit: audit testsuite test
> 🚧 ✅ trace: ftrace/tracer
> 🚧 ✅ kdump - kexec_boot
>
> Host 3:
> ✅ Boot test
> 🚧 ✅ kdump - sysrq-c
> 🚧 ✅ kdump - file-load
>
> 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 ⏱.
>
>
next prev parent reply other threads:[~2020-07-15 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 13:33 💥 PANICKED: Test report for kernel 5.7.9-rc1-c2fb28a.cki (stable) CKI Project
2020-07-15 13:36 ` Veronika Kabatova [this message]
2020-07-15 13:52 ` Greg KH
2020-07-15 14:34 ` Sasha Levin
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=2125467353.2778784.1594820204666.JavaMail.zimbra@redhat.com \
--to=vkabatov@redhat.com \
--cc=stable@vger.kernel.org \
--cc=xzhou@redhat.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