action #47390
closed[sle][functional][y] - clarify which modules needs to be loaded manually in test module kmp_modules
0%
Description
Observation¶
Listed packages contain several modules which we used to load manually in the previous SLERT releases. According to bsc#1123696 we should never directly load any lttng modules. Command lttng (lttng-tools) loads automatically what is required.
cluster-md-kmp-rt-4.12.14-9.2.x86_64
gfs2-kmp-rt-4.12.14-9.2.x86_64
dlm-kmp-rt-4.12.14-9.2.x86_64
crash-kmp-rt-7.2.1_k4.12.14_9-6.3.x86_64
oracleasm-kmp-rt-2.0.8_k4.12.14_9-5.4.x86_64
lttng-modules-kmp-rt-2.10.0_k4.12.14_9-8.3.x86_64
ocfs2-kmp-rt-4.12.14-9.2.x86_64
As a conclusion of bsc#1123696 we have to update bash script below.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/rt/kmp_modules.pm#L40
Acceptance Criteria¶
- AC1: Clarify with Jeffrey Cheung which modules should be loaded manually from listed KMP packages and update test module accordingly
- AC2: Read lttng documentation https://lttng.org/docs/v2.10/
- AC3: Execute simple lttng tracing to verify whether lttng loads modules correctly
Updated by mloviska about 5 years ago
- Status changed from New to In Progress
- Assignee set to mloviska
Manually loaded modules:
- ocfs2-kmp-rt-4.12.14-9.2.x86_64:
/lib/modules/4.12.14-10-rt/kernel/fs/ocfs2/cluster/ocfs2_nodemanager.ko
/lib/modules/4.12.14-10-rt/kernel/fs/ocfs2/dlm/ocfs2_dlm.ko
/lib/modules/4.12.14-10-rt/kernel/fs/ocfs2/dlmfs/ocfs2_dlmfs.ko
/lib/modules/4.12.14-10-rt/kernel/fs/ocfs2/ocfs2.ko
/lib/modules/4.12.14-10-rt/kernel/fs/ocfs2/ocfs2_stack_o2cb.ko
/lib/modules/4.12.14-10-rt/kernel/fs/ocfs2/ocfs2_stack_user.ko
/lib/modules/4.12.14-10-rt/kernel/fs/ocfs2/ocfs2_stackglue.ko
zoidberg:~ # lsmod |grep ocfs2
ocfs2_stack_user 16384 0
dlm 208896 1 ocfs2_stack_user
ocfs2_stack_o2cb 16384 0
ocfs2 1167360 0
ocfs2_dlmfs 24576 0
ocfs2_stackglue 20480 4 ocfs2,ocfs2_dlmfs,ocfs2_stack_user,ocfs2_stack_o2cb
ocfs2_dlm 212992 1 ocfs2_stack_o2cb
ocfs2_nodemanager 237568 4 ocfs2,ocfs2_dlm,ocfs2_dlmfs,ocfs2_stack_o2cb
configfs 45056 3 ocfs2_nodemanager,dlm
quota_tree 20480 2 ocfs2,quota_v2
jbd2 122880 2 ocfs2,ext4
- dlm-kmp-rt-4.12.14-10.2.x86_64:
/lib/modules/4.12.14-10-rt/kernel/fs/dlm/dlm.ko
zoidberg:~ # lsmod | grep dlm
dlm 208896 1 ocfs2_stack_user
ocfs2_dlmfs 24576 0
ocfs2_stackglue 20480 4 ocfs2,ocfs2_dlmfs,ocfs2_stack_user,ocfs2_stack_o2cb
ocfs2_dlm 212992 1 ocfs2_stack_o2cb
ocfs2_nodemanager 237568 4 ocfs2,ocfs2_dlm,ocfs2_dlmfs,ocfs2_stack_o2cb
configfs 45056 3 ocfs2_nodemanager,dlm
dlm was loaded by modprobe as a dependency of ocfs2_stack_user. In any case loading the module manually does not seems to be a issue.
- oracleasm-kmp-rt-2.0.8_k4.12.14_10-5.9.x86_64
zoidberg:~ # lsmod | grep -i oracleasm
oracleasm 61440 0
- gfs2-kmp-rt-4.12.14-10.2.x86_64
zoidberg:~ # lsmod | grep gfs2
gfs2 417792 0
dlm 208896 2 ocfs2_stack_user,gfs2
- cluster-md-kmp-rt-4.12.14-10.2.x86_64
zoidberg:~ # lsmod | grep cluster
md_cluster 28672 0
md_mod 167936 1 md_cluster
dlm 208896 3 ocfs2_stack_user,md_cluster,gfs2
- crash-kmp-rt-7.2.1_k4.12.14_10-6.8.x86_64
zoidberg:~ # lsmod | grep crash
crash 16384 0
Apparently, we just need to exclude lttng-modules-kmp-rt-2.10.0_k4.12.14_9-8.3.x86_64 which uses lttng-tools to load its modules.
Updated by okurz about 5 years ago
- Priority changed from Normal to High
- Target version changed from Milestone 25 to Milestone 23
So I understand this is more important as linked to currently failing tests :)
Updated by mloviska about 5 years ago
Jeffrey confirmed that only lttng modules should not be loaded directly.
I will try to use below tracing schema to test lttng.
# lttng create TEST_TRACE -o /tmp/sched_trace_example
# lttng enable-channel --kernel test-channel
# lttng enable-event --kernel -a sched_switch
# lttng start
# lttng list TEST_TRACE
# lttng stop
# lttng destroy -a
Updated by mloviska about 5 years ago
- Status changed from In Progress to Feedback
Updated by mloviska about 5 years ago
- Status changed from Feedback to Resolved