ubuntu_lttng_smoke_test failed on Azure 4.15
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Fix Released
|
Undecided
|
Unassigned | ||
linux-azure (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned | ||
Cosmic |
Invalid
|
Undecided
|
Unassigned | ||
lttng-modules (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
SRU Request:
[Impact]
After bionic/linux-azure commit 4fbb658dd8ce963
kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
This is caused by lttng-modules incorrectly handling the case when CONFIG_HOTPLUG_CPU is not enabled.
[Test Case]
Install linux-azure >= 4.15.0-1014, install lttng-modules-dkms and run the autotest ubuntu_
[Fix]
commit 894ce5dc825733d
commit 1ee63d8d1b0aaf3
[Regression Potential]
Very low. The two patches can be cleanly cherry-picked from the upstream commits. The first one that really fixed the issue just changes a single #ifdef to compile a piece of code when CONFIG_HOTPLUG_CPU is not defined. The second one just updates some comments on the code to make them consistent with the changes.
[Original Description]
This test will pass with the older kernel, 4.15.0-1013-azure, but not the 4.15.0-1014-azure in -proposed.
It looks like the kernel module can be installed, but four tests have failed:
== lttng smoke test of session create/destroy ==
Session test-kernel-session created.
Traces will be written in /tmp/lttng-
PASSED (lttng create)
Session test-kernel-session destroyed
PASSED (lttng destroy)
== lttng smoke test list kernel events ==
FAILED (lttng list --kernel)
FAILED (lttng list --kernel more output expected)
== lttng smoke test trace open/close system calls ==
Session test-kernel-session created.
Traces will be written in /tmp/lttng-
PASSED (lttng create)
FAILED (lttng enable-event)
Session test-kernel-session destroyed
== lttng smoke test trace context switches ==
Session test-kernel-session created.
Traces will be written in /tmp/lttng-
PASSED (lttng create)
FAILED (lttng enable-event)
Session test-kernel-session destroyed
Summary: 4 passed, 4 failed
Error message from /var/log/syslog:
kernel: [ 639.531889] PKCS#7 signature not signed with a trusted key
kernel: [ 639.538251] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
kernel: [ 639.538280] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
lttng-
lttng-
kernel: [ 639.606845] PKCS#7 signature not signed with a trusted key
kernel: [ 639.613331] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
kernel: [ 639.613360] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
lttng-
lttng-
kernel: [ 639.677124] PKCS#7 signature not signed with a trusted key
kernel: [ 639.680857] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
kernel: [ 639.680886] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
lttng-
lttng-
kernel: [ 639.737914] PKCS#7 signature not signed with a trusted key
kernel: [ 639.753366] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
kernel: [ 639.753394] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
lttng-
lttng-
kernel: [ 639.829710] PKCS#7 signature not signed with a trusted key
kernel: [ 639.843736] lttng_tracer: Unknown symbol lttng_hp_prepare (err 0)
kernel: [ 639.843765] lttng_tracer: Unknown symbol lttng_hp_online (err 0)
lttng-
lttng-
description: | updated |
Changed in lttng-modules (Ubuntu Cosmic): | |
status: | Fix Released → In Progress |
Changed in linux-azure (Ubuntu Xenial): | |
status: | New → Invalid |
Changed in lttng-modules (Ubuntu Xenial): | |
status: | New → In Progress |
tags: | added: patch |
description: | updated |
description: | updated |
Changed in ubuntu-kernel-tests: | |
status: | Invalid → Fix Released |
Comment #1 is invalid, this test does not work on xenial/Azure because of the module build issue (bug 1765673)