* ❌ FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue)
@ 2019-11-27 14:30 CKI Project
2019-11-27 15:06 ` Rachel Sibley
0 siblings, 1 reply; 4+ messages in thread
From: CKI Project @ 2019-11-27 14:30 UTC (permalink / raw)
To: Linux Stable maillist
Cc: Memory Management, Jan Stancek, LTP Mailing List, Xiong Zhou
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
Commit: cc9917b40848 - mdio_bus: Fix init if CONFIG_RESET_CONTROLLER=n
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: OK
Tests: FAILED
All kernel binaries, config files, and logs are available for download here:
https://artifacts.cki-project.org/pipelines/309848
One or more kernel tests failed:
ppc64le:
❌ LTP
❌ xfstests: xfs
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 3 architectures:
aarch64:
make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
ppc64le:
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
✅ Podman system integration test (as root)
✅ Podman system integration test (as user)
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ Memory function: kaslr
✅ AMTU (Abstract Machine Test Utility)
✅ LTP: openposix test suite
✅ Networking bridge: sanity
✅ Ethernet drivers sanity
✅ Networking MACsec: sanity
✅ Networking socket: fuzz
✅ Networking sctp-auth: sockopts test
✅ 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
✅ audit: audit testsuite test
✅ httpd: mod_ssl smoke sanity
✅ tuned: tune-processes-through-perf
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
✅ storage: SCSI VPD
✅ trace: ftrace/tracer
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ✅ jvm test suite
🚧 ✅ Networking vnic: ipvlan/basic
🚧 ✅ iotop: sanity
🚧 ✅ Usex - version 1.9-29
🚧 ✅ storage: dm/common
Host 2:
✅ Boot test
✅ xfstests: ext4
✅ xfstests: xfs
✅ lvm thinp sanity
✅ storage: software RAID testing
🚧 ✅ selinux-policy: serge-testsuite
🚧 ✅ Storage blktests
ppc64le:
Host 1:
✅ Boot test
✅ Podman system integration test (as root)
✅ Podman system integration test (as user)
❌ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ Memory function: kaslr
✅ AMTU (Abstract Machine Test Utility)
✅ LTP: openposix test suite
✅ Networking bridge: sanity
✅ Ethernet drivers sanity
✅ Networking MACsec: sanity
✅ Networking socket: fuzz
✅ Networking sctp-auth: sockopts 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 tunnel
✅ audit: audit testsuite test
✅ httpd: mod_ssl smoke sanity
✅ tuned: tune-processes-through-perf
✅ ALSA PCM loopback test
✅ ALSA Control (mixer) Userspace Element test
✅ trace: ftrace/tracer
🚧 ✅ CIFS Connectathon
🚧 ✅ POSIX pjd-fstest suites
🚧 ✅ jvm test suite
🚧 ✅ Networking vnic: ipvlan/basic
🚧 ✅ iotop: sanity
🚧 ✅ Usex - version 1.9-29
🚧 ✅ storage: dm/common
Host 2:
✅ Boot test
✅ xfstests: ext4
❌ xfstests: xfs
✅ lvm thinp sanity
✅ storage: software RAID testing
🚧 ✅ IPMI driver test
🚧 ✅ IPMItool loop stress test
🚧 ✅ selinux-policy: serge-testsuite
🚧 ✅ Storage blktests
x86_64:
Host 1:
✅ Boot test
✅ xfstests: ext4
✅ xfstests: xfs
✅ lvm thinp sanity
✅ storage: software RAID testing
🚧 ✅ IOMMU boot test
🚧 ✅ selinux-policy: serge-testsuite
🚧 ✅ Storage blktests
Host 2:
⏱ Boot test
⏱ Storage SAN device stress - mpt3sas driver
Host 3:
⏱ Boot test
⏱ Storage SAN device stress - megaraid_sas
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
⚡⚡⚡ Podman system integration test (as root)
⚡⚡⚡ Podman system integration test (as user)
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ Memory function: kaslr
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ LTP: openposix test suite
⚡⚡⚡ Networking bridge: sanity
⚡⚡⚡ Ethernet drivers sanity
⚡⚡⚡ Networking MACsec: sanity
⚡⚡⚡ Networking socket: fuzz
⚡⚡⚡ Networking sctp-auth: sockopts test
⚡⚡⚡ 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
⚡⚡⚡ audit: audit testsuite test
⚡⚡⚡ httpd: mod_ssl smoke sanity
⚡⚡⚡ tuned: tune-processes-through-perf
⚡⚡⚡ pciutils: sanity smoke test
⚡⚡⚡ ALSA PCM loopback test
⚡⚡⚡ ALSA Control (mixer) Userspace Element test
⚡⚡⚡ storage: SCSI VPD
⚡⚡⚡ stress: stress-ng
⚡⚡⚡ trace: ftrace/tracer
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ POSIX pjd-fstest suites
🚧 ⚡⚡⚡ jvm test suite
🚧 ⚡⚡⚡ Networking vnic: ipvlan/basic
🚧 ⚡⚡⚡ iotop: sanity
🚧 ⚡⚡⚡ Usex - version 1.9-29
🚧 ⚡⚡⚡ storage: dm/common
Test sources: https://github.com/CKI-project/tests-beaker
💚 Pull requests are welcome for new tests or improvements to existing tests!
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 are marked with ⏱. Reports for non-upstream kernels have
a Beaker recipe linked to next to each host.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ❌ FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue)
2019-11-27 14:30 ❌ FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue) CKI Project
@ 2019-11-27 15:06 ` Rachel Sibley
2019-12-03 12:22 ` [LTP] ??? " Cyril Hrubis
0 siblings, 1 reply; 4+ messages in thread
From: Rachel Sibley @ 2019-11-27 15:06 UTC (permalink / raw)
To: CKI Project, Linux Stable maillist
Cc: Memory Management, Jan Stancek, LTP Mailing List, Xiong Zhou
On 11/27/19 9:30 AM, CKI Project wrote:
>
> Hello,
>
> We ran automated tests on a recent commit from this kernel tree:
>
> Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
> Commit: cc9917b40848 - mdio_bus: Fix init if CONFIG_RESET_CONTROLLER=n
>
> The results of these automated tests are provided below.
>
> Overall result: FAILED (see details below)
> Merge: OK
> Compile: OK
> Tests: FAILED
>
> All kernel binaries, config files, and logs are available for download here:
>
> https://artifacts.cki-project.org/pipelines/309848
>
> One or more kernel tests failed:
>
> ppc64le:
> ❌ LTP
I see a slew of syscalls failures here for LTP:
https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_resultoutputfile.log
https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_syscalls.run.log
> ❌ xfstests: xfs
Also generic/212 test failed for xfstests:
https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_2_xfstests__xfs_taskout.log
Running test generic/212
#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2009 Eric Sandeen. All Rights Reserved.
#
# FS QA Test No. 212
#
# Run aio-io-setup-with-nonwritable-context-pointer -
# Test what happens when a non-writable context pointer is passed to
io_setup
#
seq=`basename $0`
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/ppc64le ibm-p9b-03 5.3.13-cc9917b.cki #1 SMP Tue
Nov 26 18:18:25 UTC 2019
MKFS_OPTIONS -- -f -m crc=1,finobt=1,rmapbt=1,reflink=1 -i sparse=1
/dev/sda3
MOUNT_OPTIONS -- -o context=system_u:object_r:nfs_t:s0 /dev/sda3
/mnt/xfstests/mnt2
generic/212 0s ... [failed, exit status 135]- output mismatch (see
/var/lib/xfstests/results//generic/212.out.bad)
--- tests/generic/212.out 2019-11-26 18:36:35.624357754 -0500
+++ /var/lib/xfstests/results//generic/212.out.bad 2019-11-26
18:44:30.926323027 -0500
@@ -1,2 +1,2 @@
QA output created by 212
-aio-io-setup-with-nonwritable-context-pointer: Success!
+./common/rc: line 1949: 521294 Bus error (core
dumped) $AIO_TEST $testtemp 2>&1
...
(Run 'diff -u /var/lib/xfstests/tests/generic/212.out
/var/lib/xfstests/results//generic/212.out.bad' to see the entire diff)
Ran: generic/212
Failures: generic/212
Failed 1 of 1 tests
>
> 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 3 architectures:
>
> aarch64:
> make options: -j30 INSTALL_MOD_STRIP=1 targz-pkg
>
> ppc64le:
> 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
> ✅ Podman system integration test (as root)
> ✅ Podman system integration test (as user)
> ✅ LTP
> ✅ Loopdev Sanity
> ✅ Memory function: memfd_create
> ✅ Memory function: kaslr
> ✅ AMTU (Abstract Machine Test Utility)
> ✅ LTP: openposix test suite
> ✅ Networking bridge: sanity
> ✅ Ethernet drivers sanity
> ✅ Networking MACsec: sanity
> ✅ Networking socket: fuzz
> ✅ Networking sctp-auth: sockopts test
> ✅ 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
> ✅ audit: audit testsuite test
> ✅ httpd: mod_ssl smoke sanity
> ✅ tuned: tune-processes-through-perf
> ✅ ALSA PCM loopback test
> ✅ ALSA Control (mixer) Userspace Element test
> ✅ storage: SCSI VPD
> ✅ trace: ftrace/tracer
> 🚧 ✅ CIFS Connectathon
> 🚧 ✅ POSIX pjd-fstest suites
> 🚧 ✅ jvm test suite
> 🚧 ✅ Networking vnic: ipvlan/basic
> 🚧 ✅ iotop: sanity
> 🚧 ✅ Usex - version 1.9-29
> 🚧 ✅ storage: dm/common
>
> Host 2:
> ✅ Boot test
> ✅ xfstests: ext4
> ✅ xfstests: xfs
> ✅ lvm thinp sanity
> ✅ storage: software RAID testing
> 🚧 ✅ selinux-policy: serge-testsuite
> 🚧 ✅ Storage blktests
>
> ppc64le:
> Host 1:
> ✅ Boot test
> ✅ Podman system integration test (as root)
> ✅ Podman system integration test (as user)
> ❌ LTP
> ✅ Loopdev Sanity
> ✅ Memory function: memfd_create
> ✅ Memory function: kaslr
> ✅ AMTU (Abstract Machine Test Utility)
> ✅ LTP: openposix test suite
> ✅ Networking bridge: sanity
> ✅ Ethernet drivers sanity
> ✅ Networking MACsec: sanity
> ✅ Networking socket: fuzz
> ✅ Networking sctp-auth: sockopts 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 tunnel
> ✅ audit: audit testsuite test
> ✅ httpd: mod_ssl smoke sanity
> ✅ tuned: tune-processes-through-perf
> ✅ ALSA PCM loopback test
> ✅ ALSA Control (mixer) Userspace Element test
> ✅ trace: ftrace/tracer
> 🚧 ✅ CIFS Connectathon
> 🚧 ✅ POSIX pjd-fstest suites
> 🚧 ✅ jvm test suite
> 🚧 ✅ Networking vnic: ipvlan/basic
> 🚧 ✅ iotop: sanity
> 🚧 ✅ Usex - version 1.9-29
> 🚧 ✅ storage: dm/common
>
> Host 2:
> ✅ Boot test
> ✅ xfstests: ext4
> ❌ xfstests: xfs
> ✅ lvm thinp sanity
> ✅ storage: software RAID testing
> 🚧 ✅ IPMI driver test
> 🚧 ✅ IPMItool loop stress test
> 🚧 ✅ selinux-policy: serge-testsuite
> 🚧 ✅ Storage blktests
>
> x86_64:
> Host 1:
> ✅ Boot test
> ✅ xfstests: ext4
> ✅ xfstests: xfs
> ✅ lvm thinp sanity
> ✅ storage: software RAID testing
> 🚧 ✅ IOMMU boot test
> 🚧 ✅ selinux-policy: serge-testsuite
> 🚧 ✅ Storage blktests
>
> Host 2:
> ⏱ Boot test
> ⏱ Storage SAN device stress - mpt3sas driver
>
> Host 3:
> ⏱ Boot test
> ⏱ Storage SAN device stress - megaraid_sas
>
> 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
> ⚡⚡⚡ Podman system integration test (as root)
> ⚡⚡⚡ Podman system integration test (as user)
> ⚡⚡⚡ LTP
> ⚡⚡⚡ Loopdev Sanity
> ⚡⚡⚡ Memory function: memfd_create
> ⚡⚡⚡ Memory function: kaslr
> ⚡⚡⚡ AMTU (Abstract Machine Test Utility)
> ⚡⚡⚡ LTP: openposix test suite
> ⚡⚡⚡ Networking bridge: sanity
> ⚡⚡⚡ Ethernet drivers sanity
> ⚡⚡⚡ Networking MACsec: sanity
> ⚡⚡⚡ Networking socket: fuzz
> ⚡⚡⚡ Networking sctp-auth: sockopts test
> ⚡⚡⚡ 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
> ⚡⚡⚡ audit: audit testsuite test
> ⚡⚡⚡ httpd: mod_ssl smoke sanity
> ⚡⚡⚡ tuned: tune-processes-through-perf
> ⚡⚡⚡ pciutils: sanity smoke test
> ⚡⚡⚡ ALSA PCM loopback test
> ⚡⚡⚡ ALSA Control (mixer) Userspace Element test
> ⚡⚡⚡ storage: SCSI VPD
> ⚡⚡⚡ stress: stress-ng
> ⚡⚡⚡ trace: ftrace/tracer
> 🚧 ⚡⚡⚡ CIFS Connectathon
> 🚧 ⚡⚡⚡ POSIX pjd-fstest suites
> 🚧 ⚡⚡⚡ jvm test suite
> 🚧 ⚡⚡⚡ Networking vnic: ipvlan/basic
> 🚧 ⚡⚡⚡ iotop: sanity
> 🚧 ⚡⚡⚡ Usex - version 1.9-29
> 🚧 ⚡⚡⚡ storage: dm/common
>
> Test sources: https://github.com/CKI-project/tests-beaker
> 💚 Pull requests are welcome for new tests or improvements to existing tests!
>
> 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 are marked with ⏱. Reports for non-upstream kernels have
> a Beaker recipe linked to next to each host.
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [LTP] ??? FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue)
2019-11-27 15:06 ` Rachel Sibley
@ 2019-12-03 12:22 ` Cyril Hrubis
2019-12-03 12:37 ` Jan Stancek
0 siblings, 1 reply; 4+ messages in thread
From: Cyril Hrubis @ 2019-12-03 12:22 UTC (permalink / raw)
To: Rachel Sibley
Cc: CKI Project, Linux Stable maillist, Memory Management, LTP Mailing List
Hi!
> > We ran automated tests on a recent commit from this kernel tree:
> >
> > Kernel repo: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
> > Commit: cc9917b40848 - mdio_bus: Fix init if CONFIG_RESET_CONTROLLER=n
> >
> > The results of these automated tests are provided below.
> >
> > Overall result: FAILED (see details below)
> > Merge: OK
> > Compile: OK
> > Tests: FAILED
> >
> > All kernel binaries, config files, and logs are available for download here:
> >
> > https://artifacts.cki-project.org/pipelines/309848
> >
> > One or more kernel tests failed:
> >
> > ppc64le:
> > ??? LTP
>
> I see a slew of syscalls failures here for LTP:
> https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_resultoutputfile.log
> https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_syscalls.run.log
There are a few syslog failures, which does not seem to be related to
the kernel commit at all. The commit above seems to touch error handling
in a mdio bus which is used to configure network hardware. I would say
that this is connected to the rest of the unexplained failures on
ppc64le that seems to happen randomly.
--
Cyril Hrubis
chrubis@suse.cz
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [LTP] ??? FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue)
2019-12-03 12:22 ` [LTP] ??? " Cyril Hrubis
@ 2019-12-03 12:37 ` Jan Stancek
0 siblings, 0 replies; 4+ messages in thread
From: Jan Stancek @ 2019-12-03 12:37 UTC (permalink / raw)
To: Cyril Hrubis
Cc: Rachel Sibley, Memory Management, LTP Mailing List,
Linux Stable maillist, CKI Project
----- Original Message -----
> Hi!
> > > We ran automated tests on a recent commit from this kernel tree:
> > >
> > > Kernel repo:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
> > > Commit: cc9917b40848 - mdio_bus: Fix init if
> > > CONFIG_RESET_CONTROLLER=n
> > >
> > > The results of these automated tests are provided below.
> > >
> > > Overall result: FAILED (see details below)
> > > Merge: OK
> > > Compile: OK
> > > Tests: FAILED
> > >
> > > All kernel binaries, config files, and logs are available for download
> > > here:
> > >
> > > https://artifacts.cki-project.org/pipelines/309848
> > >
> > > One or more kernel tests failed:
> > >
> > > ppc64le:
> > > ??? LTP
> >
> > I see a slew of syscalls failures here for LTP:
> > https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_resultoutputfile.log
> > https://artifacts.cki-project.org/pipelines/309848/logs/ppc64le_host_1_LTP_syscalls.run.log
>
> There are a few syslog failures, which does not seem to be related to
> the kernel commit at all. The commit above seems to touch error handling
> in a mdio bus which is used to configure network hardware. I would say
> that this is connected to the rest of the unexplained failures on
> ppc64le that seems to happen randomly.
I think this is different. Test is spam-ing serial console with:
preadv203 (765613): drop_caches: 3
which leads to RCU stall:
[ 4338.611873] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 4517.198118] systemd[1]: systemd-journald.service: State 'stop-watchdog' timed out. Terminating.
[ 4518.688311] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 4518.688318] rcu: 0-...0: (2 ticks this GP) idle=7da/1/0x4000000000000000 softirq=208692/208696 fqs=11772
[ 4518.688321] (detected by 3, t=24007 jiffies, g=280901, q=430)
[ 4518.688324] Sending NMI from CPU 3 to CPUs 0:
[ 4524.259240] CPU 0 didn't respond to backtrace IPI, inspecting paca.
[ 4524.259243] irq_soft_mask: 0x01 in_mce: 0 in_nmi: 0 current: 765613 (preadv203)
[ 4524.259245] Back trace of paca->saved_r1 (0xc000000029b47990) (possibly stale):
[ 4524.259246] Call Trace:
[ 4524.259250] [c000000029b47990] [0000000000000001] 0x1 (unreliable)
[ 4524.259255] [c000000029b47a00] [c0000000007e8b28] hvterm_raw_put_chars+0x48/0x70
[ 4524.259257] [c000000029b47a20] [c0000000007eb174] hvc_console_print+0x124/0x2c0
[ 4524.259260] [c000000029b47ab0] [c0000000001b2238] console_unlock+0x588/0x760
[ 4524.259262] [c000000029b47b90] [c0000000001b4a8c] vprintk_emit+0x22c/0x330
[ 4524.259264] [c000000029b47c00] [c0000000001b5d28] vprintk_func+0x78/0x1b0
[ 4524.259266] [c000000029b47c50] [c0000000001b5294] printk+0x40/0x54
[ 4524.259269] [c000000029b47c70] [c0000000004e6c7c] drop_caches_sysctl_handler+0x14c/0x170
[ 4524.259271] [c000000029b47ce0] [c000000000512390] proc_sys_call_handler+0x230/0x240
[ 4524.259273] [c000000029b47d60] [c000000000432098] __vfs_write+0x38/0x70
[ 4524.259275] [c000000029b47d80] [c0000000004363c8] vfs_write+0xd8/0x250
[ 4524.259277] [c000000029b47dd0] [c000000000436798] ksys_write+0x78/0x130
[ 4524.259280] [c000000029b47e20] [c00000000000bae4] system_call+0x5c/0x70
Maybe we could temporarily lower printk level during this test.
Test also fails to release loop device and subsequent tests fail
because they try to use same one.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-12-03 12:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-27 14:30 ❌ FAIL: Test report for kernel 5.3.13-cc9917b.cki (stable-queue) CKI Project
2019-11-27 15:06 ` Rachel Sibley
2019-12-03 12:22 ` [LTP] ??? " Cyril Hrubis
2019-12-03 12:37 ` Jan Stancek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).