Your message dated Thu, 19 May 2022 10:36:14 +0000
with message-id <e1nrdvu-0003wm...@fasolo.debian.org>
and subject line Bug#1010230: fixed in nvidia-graphics-drivers-legacy-390xx
390.151-1
has caused the Debian Bug report #1010230,
regarding nvidia-graphics-drivers-legacy-390xx: spurious module build failure
in autopkgtest on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1010230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Version: 390.147-4
Severity: serious
X-Debbugs-CC: d...@packages.debian.org
Tags: sid bookworm
User: debian...@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
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Source-Version: 390.151-1
Done: Andreas Beckmann <a...@debian.org>
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers-legacy-390xx, which is due to be installed in the
Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1010...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann <a...@debian.org> (supplier of updated
nvidia-graphics-drivers-legacy-390xx package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 19 May 2022 12:07:44 +0200
Source: nvidia-graphics-drivers-legacy-390xx
Architecture: source
Version: 390.151-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers <pkg-nvidia-de...@lists.alioth.debian.org>
Changed-By: Andreas Beckmann <a...@debian.org>
Closes: 1004849 1010230 1011142
Changes:
nvidia-graphics-drivers-legacy-390xx (390.151-1) unstable; urgency=medium
.
* New upstream legacy branch release 390.151 (2022-05-16).
* Fixed CVE-2022-28181, CVE-2022-28185. (Closes: #1011142, #1004849)
https://nvidia.custhelp.com/app/answers/detail/a_id/5353
- Fixed a bug which prevented kernel modules linked from precompiled
kernel interface object files from being loaded on recent Linux
kernels. This affected custom packages which were prepared with
nvidia-installer's --add-this-kernel option, for example.
- Fixed a driver installation failure on Linux kernel 5.17 release
candidates, where the NVIDIA kernel module failed to build with error
"implicit declaration of function 'PDE'".
.
[ Andreas Beckmann ]
* Refresh patches.
* Work around architecture misdetection when building the kernel modules in
an armhf environment on an arm64 host. (Closes: #1010230)
* Bump Standards-Version to 4.6.1. No changes needed.
Checksums-Sha1:
00730656c8e31afbba6f6150d2ed63d285f73463 7630
nvidia-graphics-drivers-legacy-390xx_390.151-1.dsc
5dfd3ce25e0d65132d88101b7d2969580c92f1c5 85992146
nvidia-graphics-drivers-legacy-390xx_390.151.orig-amd64.tar.gz
5c1b279662b2d11d54b8bb56097963e4e80636bf 30012714
nvidia-graphics-drivers-legacy-390xx_390.151.orig-armhf.tar.gz
2b0cd08db5b72a7fe51f20e14010c612aecc096b 50721019
nvidia-graphics-drivers-legacy-390xx_390.151.orig-i386.tar.gz
567d1efc90f8b6b0eef5469d9caf786ceec2f9b0 139
nvidia-graphics-drivers-legacy-390xx_390.151.orig.tar.gz
b20ad384497f6b1d48f55d14ac060e9c767c6938 178832
nvidia-graphics-drivers-legacy-390xx_390.151-1.debian.tar.xz
7c2907ad2a2a347f686f3476c4d2babd53920999 7864
nvidia-graphics-drivers-legacy-390xx_390.151-1_source.buildinfo
Checksums-Sha256:
a19daf6fa612111ec19f7d7a2a43303c78f33af7902d2a4553ee4e70039f26f3 7630
nvidia-graphics-drivers-legacy-390xx_390.151-1.dsc
fad1c613b79743c56c49558f0232a9ff5a4fd3d8ce8650f7d47a98ec3e085388 85992146
nvidia-graphics-drivers-legacy-390xx_390.151.orig-amd64.tar.gz
5f72c63b8f86652cc0d14310717bcd1483a95f3a15d7ebcacba826555f46462c 30012714
nvidia-graphics-drivers-legacy-390xx_390.151.orig-armhf.tar.gz
b1185b0ec9b3616c3aa26aa7a5d23f365fa970cc873c091fdb24a0098bf422e3 50721019
nvidia-graphics-drivers-legacy-390xx_390.151.orig-i386.tar.gz
92b059d69e5c54194808d967e45b48ea77d7054b95bfb26fcac89be27a76acc8 139
nvidia-graphics-drivers-legacy-390xx_390.151.orig.tar.gz
fcb7962df38efff55b969fa380a87f081125797ca0d5ecbd465d6b4781a1892f 178832
nvidia-graphics-drivers-legacy-390xx_390.151-1.debian.tar.xz
2621da212e13209d4083052147529c78ee9850d3a6b8ac1aa48dc969672ee372 7864
nvidia-graphics-drivers-legacy-390xx_390.151-1_source.buildinfo
Files:
f74524069ce895af24252bce2c641151 7630 non-free/libs optional
nvidia-graphics-drivers-legacy-390xx_390.151-1.dsc
c57713980e8c8e620460fc5d60f5c7af 85992146 non-free/libs optional
nvidia-graphics-drivers-legacy-390xx_390.151.orig-amd64.tar.gz
a83ee8d755c2aef706eb8cc5f6e6c8af 30012714 non-free/libs optional
nvidia-graphics-drivers-legacy-390xx_390.151.orig-armhf.tar.gz
8dbecc46d84124e28ebd5ce7320c46b8 50721019 non-free/libs optional
nvidia-graphics-drivers-legacy-390xx_390.151.orig-i386.tar.gz
14db86547dc0299daed5acababf472a6 139 non-free/libs optional
nvidia-graphics-drivers-legacy-390xx_390.151.orig.tar.gz
09abfe5d3751b94677e562185f2032fe 178832 non-free/libs optional
nvidia-graphics-drivers-legacy-390xx_390.151-1.debian.tar.xz
cfe8ceb6c811e5d6b906dd1e734fc90c 7864 non-free/libs optional
nvidia-graphics-drivers-legacy-390xx_390.151-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmKGF7oQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCGGzD/9cxBZ14+smOQ0kEJDveOSKDWC1+sDtFo8j
iVcpRAt5LtLk9yT1wav/DGRKM1SWMU1OAxMiuqoLHhdECuMJTKskQgAtfqcx5mOs
Kkgds0Msi3H2+PbBgS0+iDvxB20C5HrMfCI61yK1wSHGiz38GjBmwvG+NxCnn/cC
9OPTHAR03sNAxaWGXiq54yAcPkHfsNNGd6FJBqzSfY3P2D6qv+yKsvFQivKJ4B7U
2Kp0AFzZNmlf9EJUqS/3Wlb2jV8vehxBvbQDvfOTqL1sLilsFFJJR9iYC8wK2JRS
W85HzAI6gg8iyUBqmUZxQsAKuslVEgMgyatSefaKpvw8n5/x9zT63vjiKWuieSoP
M4NjVR3etr6V2pgKZ9lJj86wRTlxa0vR20P+xNY4oHaWwCgI9uTWXEPs6BTM/Yy5
M8sYB6muFufN5/dxIuj2aJg/MkYRCUp1hdb8Dmt5CljO0kq+k2ouGpYjnU7Pjp86
Scy5/wFcDM4xe5iaOygf6JCExyPg5PCBUOSX8VK5NIbVE7GzvI+oiqW8vz+jtF3Z
KOGJm2XSnm0ls4w1kXN2v4lGAVvRsQl7NGtUHOgJBnnWyQJ3v9Z9d/EPV1EXa7dO
2Wluq0nUVbHoam7viwgROppqLXkWsXuQw0/WC/Z5lqHQJ2H4RF8BrcLJUP687RHA
hpjRbrv1GA==
=dUkm
-----END PGP SIGNATURE-----
--- End Message ---
