Hello Colin,
I can see this issue on zVM(kernel02) with Yakkety (4.8.0-52), maybe we will need to patch this for lttng-modules on it as well?
05/03 00:35:44 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tests/ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test.sh' 05/03 00:35:44 DEBUG| utils:0153| [stdout] == lttng smoke test of session create/destroy == 05/03 00:36:01 DEBUG| utils:0153| [stdout] Spawning a session daemon 05/03 00:36:01 DEBUG| utils:0153| [stdout] Session test-kernel-session created. 05/03 00:36:01 DEBUG| utils:0153| [stdout] Traces will be written in /tmp/lttng-kernel-trace-27287-session 05/03 00:36:01 DEBUG| utils:0153| [stdout] PASSED (lttng create) 05/03 00:36:01 DEBUG| utils:0153| [stdout] Session test-kernel-session destroyed 05/03 00:36:01 DEBUG| utils:0153| [stdout] PASSED (lttng destroy) 05/03 00:36:01 DEBUG| utils:0153| [stdout] 05/03 00:36:01 DEBUG| utils:0153| [stdout] == lttng smoke test list kernel events == 05/03 00:36:01 ERROR| utils:0153| [stderr] Error: Unable to list kernel events: Kernel tracer not available 05/03 00:36:01 ERROR| utils:0153| [stderr] Error: Command error 05/03 00:36:01 DEBUG| utils:0153| [stdout] FAILED (lttng list --kernel) 05/03 00:36:01 DEBUG| utils:0153| [stdout] FAILED (lttng list --kernel more output expected) 05/03 00:36:01 DEBUG| utils:0153| [stdout] 05/03 00:36:01 DEBUG| utils:0153| [stdout] lttng smoke test trace open/close system calls SKIPPED for s390x 05/03 00:36:01 DEBUG| utils:0153| [stdout] 05/03 00:36:01 DEBUG| utils:0153| [stdout] == lttng smoke test trace context switches == 05/03 00:36:01 DEBUG| utils:0153| [stdout] Session test-kernel-session created. 05/03 00:36:01 DEBUG| utils:0153| [stdout] Traces will be written in /tmp/lttng-kernel-trace-27287-session 05/03 00:36:01 DEBUG| utils:0153| [stdout] PASSED (lttng create) 05/03 00:36:01 ERROR| utils:0153| [stderr] Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-session)
Hello Colin,
I can see this issue on zVM(kernel02) with Yakkety (4.8.0-52), maybe we will need to patch this for lttng-modules on it as well?
05/03 00:35:44 DEBUG| utils:0116| Running '/home/ ubuntu/ autotest/ client/ tests/ubuntu_ lttng_smoke_ test/ubuntu_ lttng_smoke_ test.sh' kernel- trace-27287- session kernel- trace-27287- session session)
05/03 00:35:44 DEBUG| utils:0153| [stdout] == lttng smoke test of session create/destroy ==
05/03 00:36:01 DEBUG| utils:0153| [stdout] Spawning a session daemon
05/03 00:36:01 DEBUG| utils:0153| [stdout] Session test-kernel-session created.
05/03 00:36:01 DEBUG| utils:0153| [stdout] Traces will be written in /tmp/lttng-
05/03 00:36:01 DEBUG| utils:0153| [stdout] PASSED (lttng create)
05/03 00:36:01 DEBUG| utils:0153| [stdout] Session test-kernel-session destroyed
05/03 00:36:01 DEBUG| utils:0153| [stdout] PASSED (lttng destroy)
05/03 00:36:01 DEBUG| utils:0153| [stdout]
05/03 00:36:01 DEBUG| utils:0153| [stdout] == lttng smoke test list kernel events ==
05/03 00:36:01 ERROR| utils:0153| [stderr] Error: Unable to list kernel events: Kernel tracer not available
05/03 00:36:01 ERROR| utils:0153| [stderr] Error: Command error
05/03 00:36:01 DEBUG| utils:0153| [stdout] FAILED (lttng list --kernel)
05/03 00:36:01 DEBUG| utils:0153| [stdout] FAILED (lttng list --kernel more output expected)
05/03 00:36:01 DEBUG| utils:0153| [stdout]
05/03 00:36:01 DEBUG| utils:0153| [stdout] lttng smoke test trace open/close system calls SKIPPED for s390x
05/03 00:36:01 DEBUG| utils:0153| [stdout]
05/03 00:36:01 DEBUG| utils:0153| [stdout] == lttng smoke test trace context switches ==
05/03 00:36:01 DEBUG| utils:0153| [stdout] Session test-kernel-session created.
05/03 00:36:01 DEBUG| utils:0153| [stdout] Traces will be written in /tmp/lttng-
05/03 00:36:01 DEBUG| utils:0153| [stdout] PASSED (lttng create)
05/03 00:36:01 ERROR| utils:0153| [stderr] Error: Event sched_switch: Kernel tracer not available (channel channel0, session test-kernel-