On Wed, 11 Sep 2019, Matthew Gabeler-Lee wrote:
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 :)
Small addendum: indeed the module built for the new kernel while running
the old kernel indeed loaded correctly after booting into 4.19.0-6 -- I
did not need to rebuild the dkms module after rebooting. It was,
ironically, only the module built for the _running_ kernel that was bad.
--
-- 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
