Ubuntu
lttng-modules package

lttng-modules-dkms FTBS on jammy with the latest 6.5 kernel

  1. Jammy (22.04)
  2. Bug #2043004
Bug #2043004 reported by Andrea Righi
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
lttng-modules (Ubuntu)
Confirmed
Undecided
Unassigned
Jammy
Confirmed
Undecided
Unassigned

Bug Description

[Impact]

/var/lib/dkms/lttng-modules/2.13.8/build/src/../include/lttng/events-internal.h:292:9: error: unknown type name
‘uuid_le’
  292 | uuid_le uuid; /* Trace session unique ID (copy) */
      | ^~~~~~~
/var/lib/dkms/lttng-modules/2.13.8/build/src/../include/lttng/events-internal.h:466:9: error: unknown type name
‘uuid_le’
  466 | uuid_le uuid; /* Trace session unique ID */
      | ^~~~~~~

[Test case]

 $ sudo apt install lttng-modules-dkms
 $ sudo lttng list -k

[Fix]

Backport the changes from mantic to properly support the new 6.5 kernel ABI.

[Regression potential]

We may experience regressions in systems that are using the lttng debugging tool with the new 6.5 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lttng-modules-dkms 2.13.8-1~ubuntu22.04.1
ProcVersionSignature: User Name 6.5.0-9.9~22.04.2-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/vdb)
Date: Wed Nov 8 10:12:03 2023
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: lttng-modules
UpgradeStatus: No upgrade log present (probably fresh install)

See original description
Revision history for this message
Andrea Righi (arighi) wrote :
Revision history for this message
Andrea Righi (arighi) wrote :
description: updated
Revision history for this message
Andrea Righi (arighi) wrote :

debdiff tested with GA kernel and new 6.5 kernel:

12:29 ubuntu@jammy$ uname -r
5.15.0-90-generic
5.15.0-90-generic ~
12:29 ubuntu@jammy$ sudo lttng list -k | grep sched
      sched_kthread_stop (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_kthread_stop_ret (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_waking (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_wakeup (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_wakeup_new (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_switch (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_migrate_task (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_free (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_exit (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_wait_task (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_wait (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_fork (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_exec (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_wait (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_sleep (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_iowait (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_blocked (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_runtime (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_pi_setprio (loglevel: TRACE_EMERG (0)) (type: tracepoint)
...

12:39 ubuntu@jammy$ uname -r
6.5.0-9-generic
6.5.0-9-generic ~
12:39 ubuntu@jammy$ sudo lttng list -k | grep sched
      sched_kthread_stop (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_kthread_stop_ret (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_waking (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_wakeup (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_wakeup_new (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_switch (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_migrate_task (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_free (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_exit (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_wait_task (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_wait (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_fork (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_process_exec (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_wait (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_sleep (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_iowait (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_blocked (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_stat_runtime (loglevel: TRACE_EMERG (0)) (type: tracepoint)
      sched_pi_setprio (loglevel: TRACE_EMERG (0)) (type: tracepoint)

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "lttng-modules-dkms-support-linux-6.5-jammy.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

This is on the sru queue already, so doesn't need sponsoring

Also, jammy-proposed has another upload on it for lp2017006. It was marked as wontfix, so what should we do about these? Just ignore the older bug?

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Normally, the changes file for this upload[1] should include the existing package in jammy-proposed[2].

But I see that the bug[3] for the [2] upload is marked as wontfix, so looks like that package[2] should be rejected. Can you please clarify?

1. https://launchpadlibrarian.net/696761522/lttng-modules_2.13.8-1~ubuntu22.04.2_source.changes
2. https://launchpad.net/ubuntu/+source/lttng-modules/2.13.8-1~ubuntu22.04.1
3. https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/2017006

Changed in lttng-modules (Ubuntu Jammy):
status: New → Incomplete
Changed in lttng-modules (Ubuntu):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote : Proposed package upload rejected

An upload of lttng-modules to jammy-proposed has been rejected from the upload queue for the following reason: "incorporates contents of 2.13.8-1~ubuntu22.04.1 which was verification-failed but does not address that failure".

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lttng-modules (Ubuntu) because there has been no activity for 60 days.]

Changed in lttng-modules (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lttng-modules (Ubuntu Jammy) because there has been no activity for 60 days.]

Changed in lttng-modules (Ubuntu Jammy):
status: Incomplete → Expired
Revision history for this message
Zixian Cai (caizixian) wrote :

Should we reconsider this bug? It still exists when I tests with a 6.5.0-28-generic HWE installation of 22.04.4

Changed in lttng-modules (Ubuntu Jammy):
status: Expired → Confirmed
Changed in lttng-modules (Ubuntu):
status: Expired → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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