ubuntu_lttng_smoke_test failed with DKMS installation on F-riscv-5.8 / F-oracle-5.11 / F-aws-5.11

Bug #1921728 reported by Po-Hsu Lin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Won't Fix
Undecided
Unassigned

Bug Description

This is not a regression since this test was added back for OEM kernel this cycle (2021 Mar.).

Test failed because of the DKMS module failed to build:
 /var/lib/dkms/lttng-modules/2.12.2/build/probes/../lib/ringbuffer/backend.h:360:9: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’?
   360 | set_fs(KERNEL_DS);
       | ^~~~~~~~~
       | KERNFS_NS
 cc1: some warnings being treated as errors
 /var/lib/dkms/lttng-modules/2.12.2/build/probes/../lib/ringbuffer/backend.h: In function ‘lib_ring_buffer_copy_from_user_check_nofault’:
 /var/lib/dkms/lttng-modules/2.12.2/build/probes/../lib/ringbuffer/backend.h:454:11: error: incompatible types when assigning to type ‘mm_segment_t’ {aka ‘struct <anonymous>’} from type ‘int’
   454 | old_fs = get_fs();
       | ^~~~~~
 /var/lib/dkms/lttng-modules/2.12.2/build/probes/../lib/ringbuffer/backend.h:455:9: error: ‘KERNEL_DS’ undeclared (first use in this function); did you mean ‘KERNFS_NS’?
   455 | set_fs(KERNEL_DS);
       | ^~~~~~~~~
       | KERNFS_NS
 make[2]: *** [scripts/Makefile.build:287: /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-writeback.o] Error 1
 cc1: some warnings being treated as errors
 make[2]: *** [scripts/Makefile.build:287: /var/lib/dkms/lttng-modules/2.12.2/build/probes/lttng-probe-sunrpc.o] Error 1
 make[1]: *** [scripts/Makefile.build:518: /var/lib/dkms/lttng-modules/2.12.2/build/probes] Error 2
 cc1: some warnings being treated as errors
 make[1]: *** [scripts/Makefile.build:287: /var/lib/dkms/lttng-modules/2.12.2/build/lttng-syscalls.o] Error 1
 make: *** [Makefile:1835: /var/lib/dkms/lttng-modules/2.12.2/build] Error 2
 make: Leaving directory '/usr/src/linux-headers-5.10.0-1020-oem'
Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 387, in _exec
    *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 865, in update_version
    install(*args, **dargs)
  File "/home/ubuntu/autotest/client/tests/ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test.py", line 62, in setup
    raise error.TestError('DKMS failed to install')
TestError: DKMS failed to install

Please find attachment for the DKMS build log.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
tags: added: 5.10 focal oem sru-20210315 ubuntu-lttng-smoke-test
Revision history for this message
Kelsey Steele (kelsey-steele) wrote :

DKMS failing to install on Focal/riscv-5.8 5.8.0-21.23~20.04.1 also

tags: added: 5.8 riscv
summary: - ubuntu_lttng_smoke_test failed with DKMS installation on F-oem-5.10
+ ubuntu_lttng_smoke_test failed with DKMS installation on F-oem-5.10 and
+ F-riscv-5.8
Revision history for this message
Krzysztof Kozlowski (krzk) wrote : Re: ubuntu_lttng_smoke_test failed with DKMS installation on F-oem-5.10 and F-riscv-5.8

Found on focal/aws-5.11 5.11.0-1013.13~20.04.1

tags: added: 5.11 aws sru-20210621
Revision history for this message
Krzysztof Kozlowski (krzk) wrote :

Found on focal/oracle-5.11 5.11.0-1012.12~20.04.1

tags: added: oracle
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Didn't see this on F-oem-5.10 anymore, modify the title accordingly.

summary: - ubuntu_lttng_smoke_test failed with DKMS installation on F-oem-5.10 and
- F-riscv-5.8
+ ubuntu_lttng_smoke_test failed with DKMS installation on F-riscv-5.8
summary: - ubuntu_lttng_smoke_test failed with DKMS installation on F-riscv-5.8
+ ubuntu_lttng_smoke_test failed with DKMS installation on F-riscv-5.8 /
+ F-oracle-5.11 / F-aws-5.11
tags: removed: 5.10 oem
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Kernel EOL and the hint we have is only referring to EOL kernel as well. Closing this bug.

Changed in ubuntu-kernel-tests:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.