From: Paul Menzel <pmenzel@molgen.mpg.de>
To: "Paul E. McKenney" <paulmck@kernel.org>,
Josh Triplett <josh@joshtriplett.org>
Cc: rcu@vger.kernel.org, linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Zhouyi Zhou <zhouzhouyi@gmail.com>
Subject: Re: Problems with rcutorture on ppc64le: allmodconfig(2) and other failures
Date: Tue, 18 Jan 2022 09:01:56 +0100 [thread overview]
Message-ID: <a312d512-1709-b69f-e685-e0301bce6a14@molgen.mpg.de> (raw)
In-Reply-To: <36bd91e4-8eda-5677-7fde-40295932a640@molgen.mpg.de>
[Correct references]
Am 17.01.22 um 23:00 schrieb Paul Menzel:
> Dear Linux folks,
>
>
> On an IBM S822LC SL822 (ppc64le) with Ubuntu 21.04, I tried to torture
> the RCU. allmodconfig(2) failed though.
>
> ```
> $ git describe
> v5.16-10660-g0c947b893d69
> $ tools/testing/selftests/rcutorture/bin/torture.sh --duration 10
> --- tools/testing/selftests/rcutorture/bin/torture.sh --duration 10
> --- Results directory: 2022.01.17-18.44.36-torture
> --- allmodconfig: Start Mon Jan 17 06:44:36 PM CET 2022
> --- rcutorture: Start Mon Jan 17 06:45:02 PM CET 2022
> --- rcutorture-kasan: Start Mon Jan 17 07:07:41 PM CET 2022
> --- locktorture: Start Mon Jan 17 07:33:38 PM CET 2022
> --- locktorture-kasan: Start Mon Jan 17 07:37:05 PM CET 2022
> --- scftorture: Start Mon Jan 17 07:40:54 PM CET 2022
> --- scftorture-kasan: Start Mon Jan 17 07:43:31 PM CET 2022
> --- refscale-rcu: Start Mon Jan 17 07:46:34 PM CET 2022
> --- refscale-rcu-kasan: Start Mon Jan 17 07:49:08 PM CET 2022
> --- refscale-srcu: Start Mon Jan 17 07:52:05 PM CET 2022
> --- refscale-srcu-kasan: Start Mon Jan 17 07:54:39 PM CET 2022
> --- refscale-rcu-tasks: Start Mon Jan 17 07:57:35 PM CET 2022
> --- refscale-rcu-tasks-kasan: Start Mon Jan 17 08:00:10 PM CET 2022
> --- refscale-rcu-trace: Start Mon Jan 17 08:03:06 PM CET 2022
> --- refscale-rcu-trace-kasan: Start Mon Jan 17 08:05:40 PM CET 2022
> --- refscale-refcnt: Start Mon Jan 17 08:08:40 PM CET 2022
> --- refscale-refcnt-kasan: Start Mon Jan 17 08:11:15 PM CET 2022
> --- refscale-rwlock: Start Mon Jan 17 08:14:14 PM CET 2022
> --- refscale-rwlock-kasan: Start Mon Jan 17 08:16:48 PM CET 2022
> --- refscale-rwsem: Start Mon Jan 17 08:19:45 PM CET 2022
> --- refscale-rwsem-kasan: Start Mon Jan 17 08:22:18 PM CET 2022
> --- refscale-lock: Start Mon Jan 17 08:25:17 PM CET 2022
> --- refscale-lock-kasan: Start Mon Jan 17 08:27:53 PM CET 2022
> --- refscale-lock-irq: Start Mon Jan 17 08:30:58 PM CET 2022
> --- refscale-lock-irq-kasan: Start Mon Jan 17 08:33:42 PM CET 2022
> --- refscale-acqrel: Start Mon Jan 17 08:36:58 PM CET 2022
> --- refscale-acqrel-kasan: Start Mon Jan 17 08:39:33 PM CET 2022
> --- refscale-clock: Start Mon Jan 17 08:42:33 PM CET 2022
> --- refscale-clock-kasan: Start Mon Jan 17 08:45:08 PM CET 2022
> --- rcuscale-rcu: Start Mon Jan 17 08:48:06 PM CET 2022
> --- rcuscale-rcu-kasan: Start Mon Jan 17 08:49:25 PM CET 2022
> --- rcuscale-srcu: Start Mon Jan 17 08:50:56 PM CET 2022
> --- rcuscale-srcu-kasan: Start Mon Jan 17 08:52:14 PM CET 2022
> --- rcuscale-srcud: Start Mon Jan 17 08:53:43 PM CET 2022
> --- rcuscale-srcud-kasan: Start Mon Jan 17 08:55:01 PM CET 2022
> --- rcuscale-tasks: Start Mon Jan 17 08:56:31 PM CET 2022
> --- rcuscale-tasks-kasan: Start Mon Jan 17 08:57:48 PM CET 2022
> --- rcuscale-tasks-tracing: Start Mon Jan 17 08:59:17 PM CET 2022
> --- rcuscale-tasks-tracing-kasan: Start Mon Jan 17 09:00:35 PM CET 2022
> --- rcuscale-kvfree: Start Mon Jan 17 09:02:05 PM CET 2022
> --- rcuscale-kvfree-kasan: Start Mon Jan 17 09:03:23 PM CET 2022
> --- clocksourcewd-1: Start Mon Jan 17 09:04:52 PM CET 2022
> --- clocksourcewd-1-kasan: Start Mon Jan 17 09:06:11 PM CET 2022
> --- clocksourcewd-2: Start Mon Jan 17 09:07:42 PM CET 2022
> --- clocksourcewd-2-kasan: Start Mon Jan 17 09:08:59 PM CET 2022
> --- tools/testing/selftests/rcutorture/bin/torture.sh --duration 10
> --- Done Mon Jan 17 09:10:29 PM CET 2022
> SUCCESSES:
> rcutorture(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcutorture
> rcutorture-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcutorture-kasan
> locktorture(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-locktorture
> locktorture-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-locktorture-kasan
> scftorture(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-scftorture
> scftorture-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-scftorture-kasan
> refscale-rcu(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rcu
> refscale-rcu-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rcu-kasan
> refscale-srcu(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-srcu
> refscale-srcu-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-srcu-kasan
> refscale-rcu-tasks(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rcu-tasks
> refscale-rcu-tasks-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rcu-tasks-kasan
> refscale-rcu-trace(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rcu-trace
> refscale-rcu-trace-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rcu-trace-kasan
> refscale-refcnt(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-refcnt
> refscale-refcnt-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-refcnt-kasan
> refscale-rwlock(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rwlock
> refscale-rwlock-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rwlock-kasan
> refscale-rwsem(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rwsem
> refscale-rwsem-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-rwsem-kasan
> refscale-lock(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-lock
> refscale-lock-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-lock-kasan
> refscale-lock-irq(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-lock-irq
> refscale-lock-irq-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-lock-irq-kasan
> refscale-acqrel(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-acqrel
> refscale-acqrel-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-acqrel-kasan
> refscale-clock(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-clock
> refscale-clock-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-refscale-clock-kasan
> rcuscale-rcu(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-rcu
> rcuscale-rcu-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-rcu-kasan
> rcuscale-srcu(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-srcu
> rcuscale-srcu-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-srcu-kasan
> rcuscale-srcud(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-srcud
> rcuscale-srcud-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-srcud-kasan
> rcuscale-tasks(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-tasks
> rcuscale-tasks-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-tasks-kasan
> rcuscale-tasks-tracing(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-tasks-tracing
> rcuscale-tasks-tracing-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-tasks-tracing-kasan
> rcuscale-kvfree(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-kvfree
> rcuscale-kvfree-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcuscale-kvfree-kasan
> clocksourcewd-1(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-clocksourcewd-1
> clocksourcewd-1-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-clocksourcewd-1-kasan
> clocksourcewd-2(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-clocksourcewd-2
> clocksourcewd-2-kasan(0) /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-clocksourcewd-2-kasan
>
> FAILURES:
> allmodconfig(2) tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/allmodconfig
> Started at Mon Jan 17 06:44:36 PM CET 2022, ended at Mon Jan 17 09:10:29
> PM CET 2022, duration 2:25:53.
> Summary: Successes: 44 Failures: 1.
> Size before compressing 0 files: 86M Mon Jan 17 09:10:29 PM CET 2022
> Waiting for final batch 1 of 22 compressions Mon Jan 17 09:10:29 PM CET 2022
> Size after compressing 0 files: 86M Mon Jan 17 09:10:29 PM CET 2022
> Total duration 2:25:53.
> ```
>
> Here is an excerpt from `Make.out` [1]:
>
> ```
> CC [M] sound/isa/ad1848/ad1848.o
> CC security/keys/encrypted-keys/ecryptfs_format.o
> In file included from <command-line>:
> ././include/linux/kconfig.h:5:10: fatal error: generated/autoconf.h: No such file or directory
> 5 | #include <generated/autoconf.h>
> | ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> CC [M] fs/reiserfs/inode.o
> In file included from <command-line>:
> ././include/linux/kconfig.h:5:10: fatal error: generated/autoconf.h: No such file or directory
> 5 | #include <generated/autoconf.h>
> | ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> In file included from <command-line>:
> ././include/linux/kconfig.h:5:10: fatal error: generated/autoconf.h: No such file or directory
> 5 | #include <generated/autoconf.h>
> | ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[3]: *** [scripts/Makefile.build:288:
> security/keys/encrypted-keys/ecryptfs_format.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> In file included from <command-line>:
> ././include/linux/kconfig.h:5:10: fatal error: generated/autoconf.h: No such file or directory
> 5 | #include <generated/autoconf.h>
> | ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> CC [M] sound/i2c/i2c.o
> In file included from <command-line>:
> ././include/linux/kconfig.h:5:10: fatal error: generated/autoconf.h: No such file or directory
> 5 | #include <generated/autoconf.h>
> | ^~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> CC [M] fs/ext4/block_validity.o
> make[3]: *** [scripts/Makefile.build:288: sound/isa/ad1848/ad1848.o]
> Error 1
> make[2]: *** [scripts/Makefile.build:550: sound/isa/ad1848] Error 2
> make[1]: *** [scripts/Makefile.build:550: sound/isa] Error 2
> make[1]: *** Waiting for unfinished jobs....
> ```
>
> I wonder why other builds seem to have worked. But checking the other
> results, despite the output saying the runs were a success the Linux
> kernel builds seem to have failed. For example [2]:
>
> ```
> $ more
> tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcutorture/log
>
> tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 7
> --configs CFLIST --trust-make --bootargs rcupdate.rcu_cpu_stall_suppress_at_boot=1 torture.disable_onoff_at_boot rcupdate.rcu_task_stall_timeout=30000 --datestamp 2022.01.17-18.44.36-torture/results-rcutorture
> ----Start batch 1: Mon Jan 17 06:45:03 PM CET 2022
> TREE03 16: Starting build. Mon Jan 17 06:45:03 PM CET 2022
> […]
> TREE09 1: Build complete. Mon Jan 17 07:07:40 PM CET 2022
> ---- No kernel runs. Mon Jan 17 07:07:40 PM CET 2022
> ---- TREE03 16: Build/run results:
> --- Mon Jan 17 06:45:03 PM CET 2022: Starting build, PID 3530842
> :CONFIG_HYPERVISOR_GUEST=y: improperly set
> :CONFIG_PARAVIRT=y: improperly set
> Kernel build error
> make[2]: *** No rule to make target
> 'arch/powerpc/kvm//dev/shm/linux/tools/testing/selftests/rcutorture/kvm_main.o', needed by 'arch/powerpc/kvm/kvm.o'. Stop.
> make[1]: *** [scripts/Makefile.build:550: arch/powerpc/kvm] Error 2
> make: *** [Makefile:1840: arch/powerpc] Error 2
> Run aborted.
> Build failed, not running KVM, see
> /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcutorture/TREE03.
>
> […]
> ESC[031mBUG: ESC[mBuild failed
>
> /dev/shm/linux/tools/testing/selftests/rcutorture/res/2022.01.17-18.44.36-torture/results-rcutorture/TREE09
>
> --- Done at Mon Jan 17 07:07:41 PM CET 2022 (22:39.0) exitcode 0
> ```
>
>
> Kind regards,
>
> Paul
>
>
> [1]: https://owww.molgen.mpg.de/~pmenzel/allmodconf-Make.out.txt
> [2]: https://owww.molgen.mpg.de/~pmenzel/rcutorture-log.txt
I botched those. The correct once are:
[1]: https://owww.molgen.mpg.de/~pmenzel/rcutorture/allmodconf-Make.out.txt
[2]: https://owww.molgen.mpg.de/~pmenzel/rcutorture/rcutorture-log.txt
prev parent reply other threads:[~2022-01-18 8:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 22:00 Paul Menzel
2022-01-18 7:34 ` Zhouyi Zhou
2022-01-18 7:56 ` Paul Menzel
2022-01-18 10:56 ` Zhouyi Zhou
2022-01-18 17:29 ` Paul E. McKenney
2022-01-18 23:46 ` Paul E. McKenney
2022-01-19 2:07 ` Zhouyi Zhou
2022-01-19 4:46 ` Paul E. McKenney
2022-01-19 18:21 ` Paul E. McKenney
2022-01-19 19:30 ` Zhouyi Zhou
2022-01-20 21:06 ` Paul E. McKenney
2022-01-21 0:44 ` Zhouyi Zhou
2022-01-25 16:19 ` Zhouyi Zhou
2022-01-25 18:09 ` Paul E. McKenney
2022-01-26 1:59 ` Zhouyi Zhou
2022-01-26 4:09 ` Zhouyi Zhou
2022-01-26 4:50 ` Paul E. McKenney
2022-01-26 5:14 ` Paul E. McKenney
2022-01-26 5:28 ` Zhouyi Zhou
2022-01-27 0:57 ` Zhouyi Zhou
2022-01-27 1:20 ` Paul E. McKenney
2022-01-27 1:37 ` Zhouyi Zhou
2022-01-18 8:01 ` Paul Menzel [this message]
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=a312d512-1709-b69f-e685-e0301bce6a14@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=zhouzhouyi@gmail.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
all inboxes | Powered by JetHome®