Bug#1010230: nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch
Paul Gevers
elbrus at debian.org
Tue Apr 26 20:10:31 BST 2022
Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.147-4
Severity: serious
X-Debbugs-CC: dkms at packages.debian.org
Tags: sid bookworm
User: debian-ci at lists.debian.org
Usertags: needs-update
Control: affects -1 src:dkms
Dear maintainer(s),
With a recent upload of dkms the autopkgtest of
nvidia-graphics-drivers-legacy-390xx fails in testing when that
autopkgtest is run with the binary packages of dkms from unstable on
armhf. It passes when run with only packages from testing. In tabular form:
pass fail
dkms from testing 3.0.3-1
nvidia-graphics-drivers-legacy-390xx from testing 390.147-4
all others from testing from testing
I copied some of the output at the bottom of this report. As I
understand it, the dkms changes extend the testing drastically and show
a real issue.
Currently this regression is blocking the migration of dkms to testing
[1]. Of course, dkms shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in dkms was
intended and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from dkms should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=dkms
https://ci.debian.net/data/autopkgtest/testing/armhf/n/nvidia-graphics-drivers-legacy-390xx/21184047/log.gz
At top level:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:999:5:
error: unknown type name ‘NV_WORKQUEUE_DATA_T’; did you mean
‘NV_WORKQUEUE_FLUSH’?
999 | NV_WORKQUEUE_DATA_T *data
| ^~~~~~~~~~~~~~~~~~~
| NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c: In
function ‘nv_flush_caches’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.c:225:5:
error: implicit declaration of function ‘NV_ON_EACH_CPU’
[-Werror=implicit-function-declaration]
225 | NV_ON_EACH_CPU(nv_flush_cache, NULL);
| ^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: ***
[/usr/src/linux-headers-5.17.0-1-common/scripts/Makefile.build:293:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/nv-vm.o] Error 1
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_queue_work_item’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:5:
error: implicit declaration of function ‘NV_WORKQUEUE_INIT’; did you
mean ‘NV_WORKQUEUE_FLUSH’? [-Werror=implicit-function-declaration]
1031 | NV_WORKQUEUE_INIT(&work->task, os_execute_work_item,
| ^~~~~~~~~~~~~~~~~
| NV_WORKQUEUE_FLUSH
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1031:36:
error: ‘os_execute_work_item’ undeclared (first use in this function);
did you mean ‘rm_execute_work_item’?
1031 | NV_WORKQUEUE_INIT(&work->task, os_execute_work_item,
| ^~~~~~~~~~~~~~~~~~~~
| rm_execute_work_item
In file included from
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:15:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_is_efi_enabled’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/common/inc/nv-linux.h:224:26:
warning: returning ‘bool (*)(int)’ {aka ‘_Bool (*)(int)’} from a
function with return type ‘NvS32’ {aka ‘int’} makes integer from pointer
without a cast [-Wint-conversion]
224 | #define NV_EFI_ENABLED() efi_enabled
| ^~~~~~~~~~~
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1110:12:
note: in expansion of macro ‘NV_EFI_ENABLED’
1110 | return NV_EFI_ENABLED();
| ^~~~~~~~~~~~~~
In file included from
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:15:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:
In function ‘os_get_euid’:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/common/inc/nv-linux.h:154:46:
error: ‘struct task_struct’ has no member named ‘euid’
154 | #define NV_CURRENT_EUID() (__kuid_val(current->euid))
| ^~
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.c:1338:18:
note: in expansion of macro ‘NV_CURRENT_EUID’
1338 | *pSecToken = NV_CURRENT_EUID();
| ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[3]: ***
[/usr/src/linux-headers-5.17.0-1-common/scripts/Makefile.build:293:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build/nvidia/os-interface.o]
Error 1
make[2]: *** [/usr/src/linux-headers-5.17.0-1-common/Makefile:1855:
/var/lib/dkms/nvidia-legacy-390xx/390.147/build] Error 2
make[2]: Leaving directory '/usr/src/linux-headers-5.17.0-1-armmp'
make[1]: *** [Makefile:231: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.17.0-1-common'
make: *** [Makefile:81: modules] Error 2
====================
I: Trying to build nvidia-legacy-390xx/390.147 for 5.17.0-1-rt-armmp
Error! The
/var/lib/dkms/nvidia-legacy-390xx/390.147/5.17.0-1-rt-armmp/armv8l/dkms.conf
for module nvidia-legacy-390xx includes a BUILD_EXCLUSIVE directive
which does not match this kernel/arch.
This indicates that it should not be built.
I: nvidia-legacy-390xx/390.147 is not supported on 5.17.0-1-rt-armmp
(BUILD_EXCLUSIVE directive), skipping
./nvidia-legacy-390xx/390.147/build/make.log
autopkgtest [12:12:01]: test dkms-autopkgtest
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/attachments/20220426/8e7f0934/attachment.sig>
More information about the pkg-nvidia-devel
mailing list