** Description changed:

+ [Impact]
+ 
+ lttng-modules FTBFS in Resolute on kernel 7.0.0-28.28:
+ 
+ probes/Kbuild:214: File 
/usr/src/linux-headers-7.0.0-28-generic/drivers/base/regmap/trace.h not found. 
Probe "regmap" is disabled. Use full kernel source tree
+  to enable it.
+   CC [M]  probes/lttng-probe-sched.o
+   CC [M]  probes/lttng-probe-irq.o
+   CC [M]  probes/lttng-probe-timer.o
+ In file included from probes/../../include/lttng/define_trace.h:87,
+                  from probes/../../include/instrumentation/events/timer.h:437,
+                  from probes/lttng-probe-timer.c:30:
+ probes/../../include/lttng/tracepoint-event-impl.h:133:6: error: conflicting 
types for ‘trace_hrtimer_start’; have ‘void(struct hrtimer *, enum 
hrtimer_mode)’
+   133 | void trace_##_name(_proto);
+       |      ^~~~~~
+ probes/../../include/lttng/tracepoint-event-impl.h:45:9: note: in expansion 
of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
+    45 |         LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, 
PARAMS(proto), PARAMS(args))
+       |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ probes/../../include/instrumentation/events/timer.h:229:1: note: in expansion 
of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
+   229 | LTTNG_TRACEPOINT_EVENT_MAP(hrtimer_start,
+       | ^~~~~~~~~~~~~~~~~~~~~~~~~~
+ In file included from 
/usr/src/linux-headers-7.0.0-28-generic/include/trace/events/timer.h:8,
+                  from probes/lttng-probe-timer.c:19:
+ /usr/src/linux-headers-7.0.0-28-generic/include/linux/tracepoint.h:309:28: 
note: previous definition of ‘trace_hrtimer_start’ with type ‘void(struct 
hrtimer *, enum hrtimer_mode,  bool)’ {aka ‘void(struct hrtimer *, enum 
hrtimer_mode,  _Bool)’}
+   309 |         static inline void trace_##name(proto)                        
  \
+       |                            ^~~~~~
+ /usr/src/linux-headers-7.0.0-28-generic/include/linux/tracepoint.h:515:9: 
note: in expansion of macro ‘__DECLARE_TRACE’
+   515 |         __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args),            
  \
+       |         ^~~~~~~~~~~~~~~
+ /usr/src/linux-headers-7.0.0-28-generic/include/linux/tracepoint.h:653:9: 
note: in expansion of macro ‘DECLARE_TRACE_EVENT’
+   653 |         DECLARE_TRACE_EVENT(name, PARAMS(proto), PARAMS(args))
+       |         ^~~~~~~~~~~~~~~~~~~
+ /usr/src/linux-headers-7.0.0-28-generic/include/trace/events/timer.h:223:1: 
note: in expansion of macro ‘TRACE_EVENT’
+   223 | TRACE_EVENT(hrtimer_start,
+       | ^~~~~~~~~~~
+ make[5]: *** 
[/usr/src/linux-headers-7.0.0-28-generic/scripts/Makefile.build:289: 
probes/lttng-probe-timer.o] Error 1
+ make[4]: *** 
[/usr/src/linux-headers-7.0.0-28-generic/scripts/Makefile.build:548: probes] 
Error 2
+ make[3]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:2115: .] Error 
2
+ make[2]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:248: 
__sub-make] Error 2
+ make[2]: Leaving directory '/var/lib/dkms/lttng-modules/2.15.0/build/src'
+ make[1]: *** [Makefile:248: __sub-make] Error 2
+ make[1]: Leaving directory '/usr/src/linux-headers-7.0.0-28-generic'
+ make: *** [Makefile:44: modules] Error 2
+ 
+ This is a regression happening because of an update coming from upstream
+ to Resolute kernel.
+ 
+ [Fix]
+ 
+ Appply the following patches from upstream to lttng-modules:
+ - 0f80fc3f ("fix: hrtimer: Reduce trace noise in hrtimer_start() (v7.1)")
+ - 5d6b115f ("fix: backport: hrtimer: Reduce trace noise in hrtimer_start() 
(v6.1.175)")
+ 
+ [Test Plan]
+ 
+ Build and load lttng-modules-dkms on Resolute.
+ $ sudo apt install lttng-modules-dkms
+ $ sudo dkms status
+ $ sudo modprobe lttng-test
+ 
+ [Regression Potential]
+ 
+ We may experience regressions in systems that are using the lttng
+ debugging tools in Resolute.
+ 
+ ---
  This is a potential regression:
-  * Test did not fail with previous kernel 7.0.0-27.27 in s2026.05.18 and 
7.0.0-26.26 in 2026.05.18
-  * They are using the same version of DKMS lttng-modules-dkms 
(2.15.0-1ubuntu1) between these cycles
+  * Test did not fail with previous kernel 7.0.0-27.27 in s2026.05.18 and 
7.0.0-26.26 in 2026.05.18
+  * They are using the same version of DKMS lttng-modules-dkms 
(2.15.0-1ubuntu1) between these cycles
  
  With 7.0.0-27.27, this test can be found failing on Openstack AMD64
  
  1687  ID: com.canonical.kernel::ubuntu_lttng_smoke_test/lttng-smoke-test
  1688  Category: com.canonical.plainbox::uncategorised
  1689  ... 8< 
-------------------------------------------------------------------------
  1690  22:31:07 Running 'timeout 1800s ubuntu_lttng_smoke_test.sh'
  1691  == lttng smoke test of session create/destroy ==
  1692  Session test-kernel-session created.
  1693  Traces will be output to /tmp/lttng-kernel-trace-12477-session
  1694  PASSED (lttng create)
  1695  Session `test-kernel-session` destroyed
  1696  PASSED (lttng destroy)
- 1697  
+ 1697
  1698  == lttng smoke test trace context switches ==
  1699  Session test-kernel-session created.
  1700  Traces will be output to /tmp/lttng-kernel-trace-12477-session
  1701  PASSED (lttng create)
  1702  FAILED (lttng enable-event)
  1703  Session `test-kernel-session` destroyed
- 1704  
+ 1704
  1705  Summary: 3 passed, 2 failed
  1706  
------------------------------------------------------------------------- >8 ---
  
  1707  Outcome: job failed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2158238

Title:
  [Potential regression] ubuntu_lttng_smoke_test failed with R/linux
  7.0.0-28.28

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2158238/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to