Control: tag 939845 + moreinfo unreproducible

Hi David--

On Mon 2019-09-09 14:52:48 +0200, David Raison wrote:
> I upgraded the wireguard-dkms package during a regular apt upgrade,
> which seems to have produced an invalid module:
>
> Unpacking wireguard-dkms (0.0.20190905-1) over (0.0.20190702-3) ...
> Setting up wireguard-dkms (0.0.20190905-1) ...
> Loading new wireguard-0.0.20190905 DKMS files...
> Reloading wireguard module...
> modprobe: ERROR: could not insert 'wireguard': Exec format error
> dpkg: error processing package wireguard (--configure):
>  installed wireguard package post-installation script subprocess returned 
> error exit status 1


I tried to reproduce this on a simple debian buster system with the
packages from snapshots, via:

    apt install /root/wireguard/wireguard{,-dkms,-tools}_0.0.20190702-3_*.deb
    modprobe -v wireguard
    cat /sys/module/wireguard/version
    apt install /root/wireguard/wireguard{,-dkms,-tools}_0.0.20190905-1_*.deb
    cat /sys/module/wireguard/version

and that worked as expected.

the equivalent section of the apt output is:

    DKMS: install completed.
    Setting up wireguard-tools (0.0.20190905-1) ...
    Setting up wireguard (0.0.20190905-1) ...
    Reloading wireguard module...
    Processing triggers for man-db (2.8.5-2) ...


> Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)

I note here that you're not running the latest kernel -- 4.19.0-5-amd64
is not 4.19.0-6-amd64.  is it possible that you don't have
linux-image-4.19.0-5-amd64 or its headers installed any more, despite
running that kernel?

Do we need to check that wireguard-dkms specifically succeeded in
generating a module for the running kernel?

i'd have expected that the postinst script itself would verify that
based on its invocation of 

    modinfo -F version wireguard

which should only verify the available modules for the current version.

can you show the output of:

    dpkg -l 'linux-headers-*' 'linux-image-*'

on the affected system?

thanks for the report, and sorry that i'm not currently able to
replicate it, hopefully we can figure it out.

   --dkg

Attachment: signature.asc
Description: PGP signature

Reply via email to