#912015 nvidia-legacy-340xx-kernel-dkms: dkms module does not build against kernel 4.19

#912015#5
Date:
2018-10-27 09:32:35 UTC
From:
To:
Dear Maintainer,


   * What led up to the situation?
   installed linux 4.19 built from source
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     updated to 4.19
   * What was the outcome of this action?
   dkms module failed to build with an implicit function declaration
   error
   * What outcome did you expect instead?
   module builds with no error

#912015#10
Date:
2018-10-27 09:40:26 UTC
From:
To:
Logs:

[....] dkms: running auto installation service for kernel 4.18.0-2-amd64:
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=4.18.0-2-amd64;
env CCACHE_DISABLE=1 NV_VERBOSE=1 make -C uvm modules
KERNEL_UNAME=4.18.0-2-amd64
KBUILD_EXTMOD=/var/lib/dkms/nvidia-legacy-340xx/340.107/build/uvm....................
cleaning build area...

DKMS: build completed.

nvidia-legacy-340xx.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.18.0-2-amd64/updates/dkms/

nvidia-legacy-340xx-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.18.0-2-amd64/updates/dkms/

depmod....
Job for systemd-modules-load.service failed because the control process
exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe"
for details.

DKMS: install completed.
. ok
[....] dkms: running auto installation service for kernel 4.19.0+:
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=4.19.0+; env
CCACHE_DISABLE=1 NV_VERBOSE=1 make -C uvm modules KERNEL_UNAME=4.19.0+
KBUILD_EXTMOD=/var/lib/dkms/nvidia-legacy-340xx/340.107/build/uvm............(bad
exit status: 2)
Error! Bad return status for module build on kernel: 4.19.0+ (x86_64)
Consult /var/lib/dkms/nvidia-legacy-340xx/340.107/build/make.log for more
information.
. ok

#912015#15
Date:
2018-10-27 09:40:26 UTC
From:
To:
Logs:

[....] dkms: running auto installation service for kernel 4.18.0-2-amd64:
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=4.18.0-2-amd64;
env CCACHE_DISABLE=1 NV_VERBOSE=1 make -C uvm modules
KERNEL_UNAME=4.18.0-2-amd64
KBUILD_EXTMOD=/var/lib/dkms/nvidia-legacy-340xx/340.107/build/uvm....................
cleaning build area...

DKMS: build completed.

nvidia-legacy-340xx.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.18.0-2-amd64/updates/dkms/

nvidia-legacy-340xx-uvm.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.18.0-2-amd64/updates/dkms/

depmod....
Job for systemd-modules-load.service failed because the control process
exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe"
for details.

DKMS: install completed.
. ok
[....] dkms: running auto installation service for kernel 4.19.0+:
Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=4.19.0+; env
CCACHE_DISABLE=1 NV_VERBOSE=1 make -C uvm modules KERNEL_UNAME=4.19.0+
KBUILD_EXTMOD=/var/lib/dkms/nvidia-legacy-340xx/340.107/build/uvm............(bad
exit status: 2)
Error! Bad return status for module build on kernel: 4.19.0+ (x86_64)
Consult /var/lib/dkms/nvidia-legacy-340xx/340.107/build/make.log for more
information.
. ok

#912015#20
Date:
2018-10-27 09:47:29 UTC
From:
To:
Attached log of the build in this email
#912015#25
Date:
2018-10-27 09:47:29 UTC
From:
To:
Attached log of the build in this email
#912015#30
Date:
2018-11-09 16:22:20 UTC
From:
To:
Hi,

your problems seem to be related to your custom kernel, I do cannot
reproduce it with the official Debian kernel (4.19.0-rc7-amd64 in
experimental).

Your compile command line contains
  -Wa,arch/x86/kernel/macros.s -Wa,-
this is something I do not see while building against the official
Debian kernels.


Andreas

#912015#41
Date:
2018-11-10 22:20:33 UTC
From:
To:
The issue cannot be reproduced on -rc7 because the issue started after the
4.19-rc8 tag

Also I just built the mainline kernel (4.20 at the time of speaking) and I
can still reproduce this issue

#912015#46
Date:
2018-12-01 08:24:36 UTC
From:
To:
I still cannot reproduce this with 4.19.5 in experimental.

Andreas