On Wed, 11 Sep 2019, Daniel Kahn Gillmor wrote:
IIUC, dkms should build different modules for different kernel ABIs. it
won't try to install the 4.19.0-6 module into the 4.19.0-5 kernel.
Right, but it looks like the Makefile(s) for wireguard might have been
buggy. Of course, I dont know if dkms even makes use of that Makefile.
Not particularly relevant to this issue, regardless, though.
It sounds to me like you and David are saying this report is specific to
an interaction with 4.19.0-5 and wireguard 0.0.20190905-1, not that the
problem has to do with a generic upgrade path.
But hm, maybe the 4.19.0-5 ABI wasn't actually stable? do either of you
(Matthew or David) know what version of 4.19.0-5 was actually running on
your system, vs. what version of linux-headers-4.19.0-5 you had
installed when it was built? That would be a useful datapoint.
The machine in question for me has (unchanged since the issue):
linux-headers-4.19.0-5-amd64/stable,now 4.19.37-5+deb10u2
And /var/log/kern.log says it was running:
Linux version 4.19.0-5-amd64 (debian-ker...@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u2
(2019-08-08)
--
-- Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE 77C5 16AF 1460 4A3C C4E9
