On Wed, Aug 21, 2024 at 06:18:45AM -1000, Tejun Heo wrote: ... > > tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs "2*TREE01" --trust-make ... > Hmmm... I have a hard time imagining that change causing that error. My bet > is unreliable reproducer. I'll try the repro. I'm probably doing something wrong but all the tests say that init segfaulted in the log file: [ 5.505986] init[1]: segfault at 28 ip 000000000040101f sp 00007fff1bbf6fc0 error 4 in init[101f,401000+1000] likely on CPU 12 (core 12, socket 0) [ 5.509949] Code: Unable to access opcode bytes at 0x400ff5. [ 5.512314] coredump: 1(init): over coredump resource limit, skipping core dump [ 5.514976] coredump: 1(init): coredump has not been created, error -7 [ 5.516911] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b Pasting the command output: $ tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs "2*TREE01" --trust-make tools/testing/selftests/rcutorture/initrd/init already exists, no need to create it Results directory: /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03 tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs 2*TREE01 --trust-make ----Start batch 1: Wed Aug 21 06:31:03 AM HST 2024 TREE01 8: Starting build. Wed Aug 21 06:31:03 AM HST 2024 TREE01 8: Waiting for build to complete. Wed Aug 21 06:31:03 AM HST 2024 TREE01 8: Build complete. Wed Aug 21 06:31:30 AM HST 2024 TREE01.2 8: Starting build. Wed Aug 21 06:31:30 AM HST 2024 TREE01.2 8: Waiting for build to complete. Wed Aug 21 06:31:30 AM HST 2024 TREE01.2 8: Build complete. Wed Aug 21 06:31:31 AM HST 2024 ---- TREE01 8: Kernel present. Wed Aug 21 06:31:31 AM HST 2024 ---- TREE01.2 8: Kernel present. Wed Aug 21 06:31:31 AM HST 2024 ---- Starting kernels. Wed Aug 21 06:31:31 AM HST 2024 ---- All kernel runs complete. Wed Aug 21 06:31:42 AM HST 2024 ---- TREE01 8: Build/run results: --- Wed Aug 21 06:31:03 AM HST 2024: Starting build, PID 456070 --- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel CPU-hotplug kernel, adding rcutorture onoff. --- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel, PID 483593 Monitoring qemu job at pid 483623 Wed Aug 21 06:31:41 AM HST 2024 TREE01 no success message, 0 successful version messages WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01/console.log TREE01 WARNING: Summary: Call Traces: 1 ---- TREE01.2 8: Build/run results: --- Wed Aug 21 06:31:30 AM HST 2024: Starting build, PID 482122 --- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel CPU-hotplug kernel, adding rcutorture onoff. --- Wed Aug 21 06:31:31 AM HST 2024: Starting kernel, PID 483619 Monitoring qemu job at pid 483648 Wed Aug 21 06:31:41 AM HST 2024 TREE01 no success message, 0 successful version messages WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01.2/console.log TREE01 WARNING: Summary: Call Traces: 1 --- Wed Aug 21 06:31:42 AM HST 2024 Test summary: Results directory: /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03 tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 1m --configs 2*TREE01 --trust-make TREE01 ------- TREE01 no success message, 0 successful version messages WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01/console.log TREE01 WARNING: Summary: Call Traces: 1 Completed in 10 vs. 60 TREE01.2 ------- TREE01.2 no success message, 0 successful version messages WARNING: Assertion failure in /home/htejun/os/linux-next/tools/testing/selftests/rcutorture/res/2024.08.21-06.31.03/TREE01.2/console.log TREE01.2 WARNING: Summary: Call Traces: 1 Completed in 10 vs. 60 2 runs with build errors. 2 runs with runtime errors. --- Done at Wed Aug 21 06:31:42 AM HST 2024 (39 seconds) exitcode 3 -- tejun
