** Summary changed: - ubuntu-kernel-selftests.ftrace fails on riscv64 + ubuntu-kernel-selftests.ftrace hangs on riscv64
** Tags added: sru-20220509 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1940080 Title: ubuntu-kernel-selftests.ftrace hangs on riscv64 Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: Confirmed Bug description: 08/12 22:10:03 DEBUG| utils:0153| [stdout] # === Ftrace unit tests === 08/12 22:10:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check [PASS] 08/12 22:10:45 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers [PASS] 08/12 22:10:51 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test [PASS] 08/12 22:10:56 DEBUG| utils:0153| [stdout] # [4] Basic event tracing check [PASS] 08/12 22:11:01 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer size [PASS] 08/12 22:11:06 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing setting [PASS] 08/12 22:11:11 DEBUG| utils:0153| [stdout] # [7] trace_pipe and trace_marker [PASS] 08/12 22:11:15 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct functions against tracers [UNRESOLVED] 08/12 22:11:16 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct functions against kprobes [UNSUPPORTED] 08/12 22:11:20 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - add/remove kprobe events [FAIL] 08/12 22:11:21 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - add/remove synthetic events [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - selective clear (compatibility) [UNSUPPORTED] 08/12 22:11:22 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - generic clear event [UNSUPPORTED] 08/12 22:11:27 DEBUG| utils:0153| [stdout] # [14] event tracing - enable/disable with event level files [PASS] 08/12 22:11:34 DEBUG| utils:0153| [stdout] # [15] event tracing - restricts events based on pid notrace filtering [PASS] 08/12 22:11:40 DEBUG| utils:0153| [stdout] # [16] event tracing - restricts events based on pid [PASS] 08/12 22:11:45 DEBUG| utils:0153| [stdout] # [17] event tracing - enable/disable with subsystem level files [PASS] 08/12 22:11:51 DEBUG| utils:0153| [stdout] # [18] event tracing - enable/disable with top level files [PASS] 08/12 22:11:58 DEBUG| utils:0153| [stdout] # [19] Test trace_printk from module [PASS] 08/12 22:12:15 DEBUG| utils:0153| [stdout] # [20] ftrace - function graph filters with stack tracer [PASS] 08/12 22:12:24 DEBUG| utils:0153| [stdout] # [21] ftrace - function graph filters [PASS] 08/12 22:12:35 DEBUG| utils:0153| [stdout] # [22] ftrace - function pid notrace filters [PASS] 08/12 22:12:46 DEBUG| utils:0153| [stdout] # [23] ftrace - function pid filters [PASS] 08/12 22:12:54 DEBUG| utils:0153| [stdout] # [24] ftrace - stacktrace filter command [PASS] 08/12 22:13:03 DEBUG| utils:0153| [stdout] # [25] ftrace - function trace with cpumask [PASS] 08/12 22:13:28 DEBUG| utils:0153| [stdout] # [26] ftrace - test for function event triggers [FAIL] 08/12 22:13:42 DEBUG| utils:0153| [stdout] # [27] ftrace - function trace on module [PASS] ** hang, whilst a lot more test cases are expected ** I.e. the next test case result should have been # [28] ftrace - function profiling Failure: # [10] Generic dynamic event - add/remove kprobe events [FAIL] # [26] ftrace - test for function event triggers [FAIL] nothing exciting in the dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
