Package: lttng-modules-dkms
Version: 2.10.8-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***
   * What led up to the situation?

   Upgrading Debian 10 from 10.5 to 10.6 led up to the current situation.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

   I successfully installed lttng-modules-dkms in Debian 10.5, where
   linux-headers was 4.19.0-10-amd64 by default.
   However, after upgrading Debian to 10.6, where linux-headers is
   4.19.0-11-amd64, the package failed to install.

   * What was the outcome of this action?

   The installation fails with the following error.

              ```
              2020/10/14 05:02:40 apt | Setting up lttng-modules-dkms 
(2.10.8-1) ...
              2020/10/14 05:02:40 apt | Loading new lttng-modules-2.10.8 DKMS 
files...
              2020/10/14 05:02:40 apt | It is likely that 4.19.0-10-amd64 
belongs to a chroot's host
              2020/10/14 05:02:40 apt | Building for 4.19.0-11-amd64
              2020/10/14 05:02:40 apt | Building initial module for 
4.19.0-11-amd64
              2020/10/14 05:02:55 apt | Error! Bad return status for module 
build on kernel: 4.19.0-11-amd64 (x86_64)
              2020/10/14 05:02:55 apt | Consult 
/var/lib/dkms/lttng-modules/2.10.8/build/make.log for more information.
              2020/10/14 05:02:55 apt | dpkg: error processing package 
lttng-modules-dkms (--configure):
              2020/10/14 05:02:55 apt |  installed lttng-modules-dkms package 
post-installation script subprocess returned error exit status 10
              2020/10/14 05:02:55 apt | Processing triggers for systemd 
(241-7~deb10u4) ...
              2020/10/14 05:02:55 apt | Processing triggers for libc-bin 
(2.28-10) ...
              2020/10/14 05:02:55 apt | Errors were encountered while 
processing:
              2020/10/14 05:02:55 apt |  lttng-modules-dkms
              2020/10/14 05:02:55 apt | E: Sub-process /usr/bin/dpkg returned 
an error code (1)
              ```
/var/lib/dkms/lttng-modules/2.10.8/build/make.log shows errors as below.
See attachment for more details.
```
  CC [M]  
/var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-writeback.o
  CC [M]  /var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-kprobes.o
In file included from 
/var/lib/dkms/lttng-modules/2.10.8/build/probes/../probes/define_trace.h:100,
                 from 
/var/lib/dkms/lttng-modules/2.10.8/build/probes/../instrumentation/events/lttng-module/writeback.h:735,
                 from 
/var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-writeback.c:51:
/var/lib/dkms/lttng-modules/2.10.8/build/probes/../probes/lttng-tracepoint-event-impl.h:143:6:
 error: conflicting types for 'trace_writeback_queue_io'
void trace_##_name(_proto);
      ^~~~~~
/var/lib/dkms/lttng-modules/2.10.8/build/probes/../probes/lttng-tracepoint-event-impl.h:55:2:
 note: in expansion of macro 'LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP'
  LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), 
PARAMS(args))
  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/lttng-modules/2.10.8/build/probes/../probes/lttng-tracepoint-event-impl.h:97:2:
 note: in expansion of macro 'LTTNG_TRACEPOINT_EVENT_MAP'
  LTTNG_TRACEPOINT_EVENT_MAP(name, name,    \
  ^~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/lttng-modules/2.10.8/build/probes/../instrumentation/events/lttng-module/writeback.h:375:1:
 note: in expansion of macro 'LTTNG_TRACEPOINT_EVENT'
LTTNG_TRACEPOINT_EVENT(writeback_queue_io,
^~~~~~~~~~~~~~~~~~~~~~
In file included from 
/usr/src/linux-headers-4.19.0-11-common/include/trace/events/writeback.h:8,
                 from 
/var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-writeback.c:33:
/usr/src/linux-headers-4.19.0-11-common/include/linux/tracepoint.h:235:21: 
note: previous definition of 'trace_writeback_queue_io' was here
  static inline void trace_##name(proto)    \
                     ^~~~~~
/usr/src/linux-headers-4.19.0-11-common/include/linux/tracepoint.h:398:2: note: 
in expansion of macro '__DECLARE_TRACE'
  __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args),  \
  ^~~~~~~~~~~~~~~
/usr/src/linux-headers-4.19.0-11-common/include/linux/tracepoint.h:534:2: note: 
in expansion of macro 'DECLARE_TRACE'
  DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
  ^~~~~~~~~~~~~
/usr/src/linux-headers-4.19.0-11-common/include/trace/events/writeback.h:360:1: 
note: in expansion of macro 'TRACE_EVENT'
TRACE_EVENT(writeback_queue_io,
^~~~~~~~~~~
make[4]: *** 
[/usr/src/linux-headers-4.19.0-11-common/scripts/Makefile.build:314: 
/var/lib/dkms/lttng-modules/2.10.8/build/probes/lttng-probe-writeback.o] Error 1
make[4]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/lttng-modules/2.10.8/build/lttng-abi.o
make[3]: *** 
[/usr/src/linux-headers-4.19.0-11-common/scripts/Makefile.build:549: 
/var/lib/dkms/lttng-modules/2.10.8/build/probes] Error 2
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [/usr/src/linux-headers-4.19.0-11-common/Makefile:1545: 
_module_/var/lib/dkms/lttng-modules/2.10.8/build] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.19.0-11-amd64'
```

* What outcome did you expect instead?

Lttng modules were successfully built and installed in Debian 10.6 without a 
hitch.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lttng-modules-dkms depends on:
ii  dkms  2.6.1-4

Versions of packages lttng-modules-dkms recommends:
ii  lttng-tools  2.10.6-1

lttng-modules-dkms suggests no packages.

-- no debconf information

Attachment: make-20201014.log
Description: make-20201014.log

Reply via email to