Package: wireguard-dkms
Version: 0.0.20190905-1
Followup-For: Bug #939845
Same problem here.
Seems pretty normal to install updates before activating a new kernel
I notice that systems that have hand-configured wireguard intefaces, the
upgrade scripts won't reload the module, but systems just using
wg-quick@.service do.
Having a system update disable a network interface and fail to restore it is
... bad. Luckily I wasn't accessing the systems in question over that vpn!
This item from /var/log/kern.log looks like it might be useful in tracing
down the issue:
module: x86/modules: Skipping invalid relocation target, existing value is
nonzero for type 1, loc 00000000fdbe1c28, val ffffffffc14f00a6
This item from the git log for the new releae also seems like it might be
related, though unlikely:
https://git.zx2c4.com/WireGuard/commit/?id=dcca03f27879701d7377109517176a3aae86619f
> Makefile: allow specifying kernel release
> This makes depmod work when building/installing the module for a kernel
> other than the currently running one.
Not sure if the common dkms scripts might be passing the KERNELRELEASE var
in a way that is messing up the build? In fairness, that seems ... unlikely
to be the cause of an invalid relocation, and more likely to _fix_ having
built the module for the new kernel before booting it :)
-- System Information:
Debian Release: 10.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'testing'), (500, 'oldstable'), (490, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages wireguard-dkms depends on:
ii dkms 2.6.1-4
ii perl 5.28.1-6
Versions of packages wireguard-dkms recommends:
ii wireguard-tools 0.0.20190905-1
wireguard-dkms suggests no packages.
-- no debconf information
