[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-09-08 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=214185. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help

[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-08-26 Thread Colin Ian King
** Bug watch added: Linux Kernel Bug Tracker #214185 https://bugzilla.kernel.org/show_bug.cgi?id=214185 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=214185 Importance: Unknown Status: Unknown ** Changed in: ubuntu-kernel-tests Importance: Undecided =>

[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-08-25 Thread Colin Ian King
the RCU timeout was a red-herring; it occurs during the filter set-up. The actual test to find the stack tracer traced stack sizes is running w/o causing RCU soft lockup messages but it is failing to find the kernel function names that match the *lock* regex, so that's a bug. -- You received this

[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-08-25 Thread Colin Ian King
... I've looked at this test and the following occurs: 0. go to the tracking directory: cd /sys/kernel/debug/tracing 1. tracer is disabled: echo 0 > /proc/sys/kernel/stack_tracer_enabled 2. tracer is set to track all kernel functions with *lock* in the name: echo '*lock*' > stack_trace_filter

[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-08-25 Thread Colin Ian King
FYI, to debug the test script use: impish/tools/testing/selftests/ftrace$ sudo ./ftracetest test.d/ftrace/func_stack_tracer.tc -v -d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940972 Title: v5.

[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-08-25 Thread Colin Ian King
The test script adds a tracing filter: echo '*lock*' > stack_trace_filter ..that takes a few minutes to apply and during that time we see the RCU and/or softlockup messages. This is kind of expected since we're blocked in kernel space updating ftrace points across the kernel which is slow and exp

[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-08-24 Thread Dimitri John Ledkov
[10052.121189] rcu: INFO: rcu_sched self-detected stall on CPU [10052.126125] rcu: 1-: (14995 ticks this GP) idle=a3a/1/0x4002 softirq=116019/116019 fqs=7426 [10080.057250] watchdog: BUG: soft lockup - CPU#1 stuck for 82s! [ftracetest:30662] [10124.057368] watchdog: BUG: soft

[Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched

2021-08-24 Thread Dimitri John Ledkov
** Description changed: $ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests ... # [32] ftrace - Max stack tracer [FAIL] ... + Testing using 5.13.0-1002.2 - Testing using 5.13.0-1002.2 + the full ftrace suite takes just over 2 hours on unmatched. -- You received t