Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
On Tue 2019-11-12 09:16:37 +0100, Christian Haul wrote: > On 11.11.19 15:33, Daniel Kahn Gillmor wrote: >> control: affects 943555 + dkms >> >> On Sun 2019-11-10 18:09:33 +0100, Christian Haul wrote: >>> On 10.11.19 14:51, Daniel Kahn Gillmor wrote: On Sat 2019-10-26 12:51:47 +, Chris. wrote: > >> However, that package looks like it's about to be superceded by >> linux-headers-5.3.0-2-arm64 because of a recent ABI bump to the kernel >> in unstable. >> >> I know this is a lot to ask, but can you take the following steps? >> >> * upgrade your system to linux-image-5.3.0-2-arm64 and reboot into the >>new kernel >> * make sure you have linux-headers-5.3.0-2-arm64 installed >> * retry building the various kernel modules that were failing? > > Kernel package just arrived. Builds fine. All good - bug can be closed. > > Thanks for your patience. Great! thanks for your followup here. This e-mail should close the bug report. --dkg signature.asc Description: PGP signature
Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
On 11.11.19 15:33, Daniel Kahn Gillmor wrote: > control: affects 943555 + dkms > > On Sun 2019-11-10 18:09:33 +0100, Christian Haul wrote: >> On 10.11.19 14:51, Daniel Kahn Gillmor wrote: >>> On Sat 2019-10-26 12:51:47 +, Chris. wrote: > However, that package looks like it's about to be superceded by > linux-headers-5.3.0-2-arm64 because of a recent ABI bump to the kernel > in unstable. > > I know this is a lot to ask, but can you take the following steps? > > * upgrade your system to linux-image-5.3.0-2-arm64 and reboot into the >new kernel > * make sure you have linux-headers-5.3.0-2-arm64 installed > * retry building the various kernel modules that were failing? Kernel package just arrived. Builds fine. All good - bug can be closed. Thanks for your patience. Chris.
Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
Control: reassign -1 src:linux Control: affects -1 - gcc-9 linux-headers-5.3.0-1-arm64 Control: forcemerge 943953 -1 On Mon, 2019-11-11 at 09:33 -0500, Daniel Kahn Gillmor wrote: > control: affects 943555 + dkms [...] > I think if anything this bug report itself should be reassigned to > linux-headers-5.3.0-1-arm64. > > However, that package looks like it's about to be superceded by > linux-headers-5.3.0-2-arm64 because of a recent ABI bump to the kernel > in unstable. [...] Which is why you should generally assign linux bugs to the source package. Anyway, the new version fixed this bug. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus signature.asc Description: This is a digitally signed message part
Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
control: affects 943555 + dkms On Sun 2019-11-10 18:09:33 +0100, Christian Haul wrote: > On 10.11.19 14:51, Daniel Kahn Gillmor wrote: >> On Sat 2019-10-26 12:51:47 +, Chris. wrote: >>> on Raspberry Pi3 kernel module stops building since updating to kernel >>> 5.3.0.1. > >> I'm not sure this is a wireguard-specific issue... > > I have added another DKMS package (iptables-netflow-dkms) and it runs > into the same issue. > > # cat /var/lib/dkms/ipt-netflow/2.4/build/make.log > DKMS make.log for ipt-netflow-2.4 for kernel 5.3.0-1-arm64 (aarch64) > Sun Nov 10 14:16:57 UTC 2019 > Compiling for kernel 5.3.7 > make -C /lib/modules/5.3.0-1-arm64/build > M=/var/lib/dkms/ipt-netflow/2.4/build modules CONFIG_DEBUG_INFO=y > make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent > make rule. > make[1]: Entering directory '/usr/src/linux-headers-5.3.0-1-arm64' > arch/arm64/Makefile:58: *** arm-linux-gnueabihf-gcc not found, check > CROSS_COMPILE_COMPAT. Stop. > make[1]: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:179: > sub-make] Error 2 > make[1]: Leaving directory '/usr/src/linux-headers-5.3.0-1-arm64' > make: *** [Makefile:25: ipt_NETFLOW.ko] Error 2 > > >> This looks to me like you don't have the arm64-specific compiler >> installed, which ought to have been installed correctly by >> linux-headers-5.3.0-1-arm64. > > Not an expert here, but I can still run > > root@rpi3:~# dkms build wireguard/0.0.20191012 -k 5.2.0-3-arm64 > > Kernel preparation unnecessary for this kernel. Skipping... > > Building module: > cleaning build area > make -j4 KERNELRELEASE=5.2.0-3-arm64 -C /lib/modules/5.2.0-3-arm64/build > M=/var/lib/dkms/wireguard/0.0.20191012/build. > > cleaning build area. > > DKMS: build completed. > > I.E. compilation works in general. Something in kernel 5.3 changed that > breaks DKMS on Raspberry Pi3. Looking for a gcc-9 for abihf I can onle > find packages marked "crosscompile" (plus it's missing a dependency so I > can't install) > > Should I file a bug against the linux-headers package instead? I think if anything this bug report itself should be reassigned to linux-headers-5.3.0-1-arm64. However, that package looks like it's about to be superceded by linux-headers-5.3.0-2-arm64 because of a recent ABI bump to the kernel in unstable. I know this is a lot to ask, but can you take the following steps? * upgrade your system to linux-image-5.3.0-2-arm64 and reboot into the new kernel * make sure you have linux-headers-5.3.0-2-arm64 installed * retry building the various kernel modules that were failing? If they are still failing for you on 5.3.0-2-arm64, i recommend reassigning this bug report to linux-headers-5.3.0-2-arm64. Sorry to not have the equipment up and running to test these things myself. I appreciate your persevering on this bug report, let's get it figured out (and hopefully, fixed)! All the best, --dkg signature.asc Description: PGP signature
Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
Hi Daniel, thanks for caring! On 10.11.19 14:51, Daniel Kahn Gillmor wrote: > On Sat 2019-10-26 12:51:47 +, Chris. wrote: >> on Raspberry Pi3 kernel module stops building since updating to kernel >> 5.3.0.1. > I'm not sure this is a wireguard-specific issue... I have added another DKMS package (iptables-netflow-dkms) and it runs into the same issue. # cat /var/lib/dkms/ipt-netflow/2.4/build/make.log DKMS make.log for ipt-netflow-2.4 for kernel 5.3.0-1-arm64 (aarch64) Sun Nov 10 14:16:57 UTC 2019 Compiling for kernel 5.3.7 make -C /lib/modules/5.3.0-1-arm64/build M=/var/lib/dkms/ipt-netflow/2.4/build modules CONFIG_DEBUG_INFO=y make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/src/linux-headers-5.3.0-1-arm64' arch/arm64/Makefile:58: *** arm-linux-gnueabihf-gcc not found, check CROSS_COMPILE_COMPAT. Stop. make[1]: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:179: sub-make] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.3.0-1-arm64' make: *** [Makefile:25: ipt_NETFLOW.ko] Error 2 > This looks to me like you don't have the arm64-specific compiler > installed, which ought to have been installed correctly by > linux-headers-5.3.0-1-arm64. Not an expert here, but I can still run root@rpi3:~# dkms build wireguard/0.0.20191012 -k 5.2.0-3-arm64 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area make -j4 KERNELRELEASE=5.2.0-3-arm64 -C /lib/modules/5.2.0-3-arm64/build M=/var/lib/dkms/wireguard/0.0.20191012/build. cleaning build area. DKMS: build completed. I.E. compilation works in general. Something in kernel 5.3 changed that breaks DKMS on Raspberry Pi3. Looking for a gcc-9 for abihf I can onle find packages marked "crosscompile" (plus it's missing a dependency so I can't install) Should I file a bug against the linux-headers package instead? Cheers, Chris.
Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
Control: tags 943555 + help moreinfo Control: severity 943555 important Control: affects 943555 + linux-headers-5.3.0-1-arm64 gcc-9 Hi Chris-- Thanks for the report! On Sat 2019-10-26 12:51:47 +, Chris. wrote: > on Raspberry Pi3 kernel module stops building since updating to kernel > 5.3.0.1. > > Output of /var/lib/dkms/wireguard/0.0.20191012/build/make.log > DKMS make.log for wireguard-0.0.20191012 for kernel 5.3.0-1-arm64 (aarch64) > Sat Oct 26 12:37:31 UTC 2019 > make: Entering directory '/usr/src/linux-headers-5.3.0-1-arm64' > arch/arm64/Makefile:58: *** arm-linux-gnueabihf-gcc not found, check > CROSS_COMPILE_COMPAT. Stop. > make: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:179: sub-make] > Error 2 > make: Leaving directory '/usr/src/linux-headers-5.3.0-1-arm64' I'm not sure this is a wireguard-specific issue... This looks to me like you don't have the arm64-specific compiler installed, which ought to have been installed correctly by linux-headers-5.3.0-1-arm64. I note that the arm64 flavor of the linux-headers-* packages just depends directly on gcc-9, and not on any specific variant of it. compare with the x86_64 variant or the armmp variant, which explicitly point toward an arch-specific metapackages for gcc: https://packages.debian.org/sid/linux-headers-5.3.0-1-arm64 vs: https://packages.debian.org/sid/linux-headers-5.3.0-1-amd64 https://packages.debian.org/sid/linux-headers-5.3.0-1-armmp Is it possible that you have some other architecture's gcc-9 installed, or something like that? Regards, --dkg signature.asc Description: PGP signature
Bug#943555: wireguard-dkms: Kernel modules don't build with kernel 5.3.0-1-arm64 on Raspberry Pi3
Package: wireguard-dkms
Version: 0.0.20191012-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
on Raspberry Pi3 kernel module stops building since updating to kernel
5.3.0.1.
Output of /var/lib/dkms/wireguard/0.0.20191012/build/make.log
DKMS make.log for wireguard-0.0.20191012 for kernel 5.3.0-1-arm64 (aarch64)
Sat Oct 26 12:37:31 UTC 2019
make: Entering directory '/usr/src/linux-headers-5.3.0-1-arm64'
arch/arm64/Makefile:58: *** arm-linux-gnueabihf-gcc not found, check
CROSS_COMPILE_COMPAT. Stop.
make: *** [/usr/src/linux-headers-5.3.0-1-common/Makefile:179: sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.3.0-1-arm64'
Thanks.
Chris.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.3.0-1-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.utf8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=de_DE.utf8 (charmap=locale: Cannot set LC_MESSAGES to default
locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages wireguard-dkms depends on:
ii dkms 2.7.1-4
ii perl 5.30.0-8
Versions of packages wireguard-dkms recommends:
ii wireguard-tools 0.0.20191012-1
wireguard-dkms suggests no packages.
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "de_DE.utf8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
-- debsums errors found:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "de_DE.utf8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
