Comment 1 for bug 1940080

Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: ubuntu-kernel-selftests.ftrace fails on riscv64

With Impish 5.13 riscv, this ftracetest is hanging on the same point:

 # selftests: ftrace: ftracetest
 # === Ftrace unit tests ===
 # [1] Basic trace file check [PASS]
 # [2] Basic test for tracers [PASS]
 # [3] Basic trace clock test [PASS]
 # [4] Basic event tracing check [PASS]
 # [5] Change the ringbuffer size [PASS]
 # [6] Snapshot and tracing setting [PASS]
 # [7] trace_pipe and trace_marker [PASS]
 # [8] Test ftrace direct functions against tracers [UNRESOLVED]
 # [9] Test ftrace direct functions against kprobes [UNRESOLVED]
 # [10] Generic dynamic event - add/remove kprobe events [PASS]
 # [11] Generic dynamic event - add/remove synthetic events [UNSUPPORTED]
 # [12] Generic dynamic event - selective clear (compatibility) [UNSUPPORTED]
 # [13] Generic dynamic event - generic clear event [UNSUPPORTED]
 # [14] event tracing - enable/disable with event level files [PASS]
 # [15] event tracing - restricts events based on pid notrace filtering [PASS]
 # [16] event tracing - restricts events based on pid [PASS]
 # [17] event tracing - enable/disable with subsystem level files [PASS]
 # [18] event tracing - enable/disable with top level files [PASS]
 # [19] Test trace_printk from module [PASS]
 # [20] ftrace - function graph filters with stack tracer [PASS]
 # [21] ftrace - function graph filters [PASS]
 # [22] ftrace - function trace with cpumask [PASS]
 # [23] ftrace - test for function event triggers [FAIL]
 # [24] ftrace - function pid notrace filters [PASS]
 # [25] ftrace - function pid filters [PASS]
 # [26] ftrace - stacktrace filter command [PASS]
 # [27] ftrace - function trace on module [PASS]
* hang here

Failure:
 # [23] ftrace - test for function event triggers [FAIL]