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 +0000, 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
Attachment:
signature.asc
Description: PGP signature