Bug#1003210: Module loading also fails on boot

[Martijn van de Streek <martijn@vandestreek.xyz>]

I'm getting very similar errors on boot, when using an encrypted root
file system on LVM. Because it can't load the necessary modules, the
system does not allow me to enter the password to unlock my drive,
making the system unusable unless I boot an older kernel.

Output of lsblk:
------
NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
sda                   8:0    0 476,9G  0 disk  
├─sda1                8:1    0   512M  0 part  /boot/efi
├─sda4                8:4    0   300M  0 part  /boot
└─sda5                8:5    0 476,1G  0 part  
  └─sda6_crypt      254:0    0 476,1G  0 crypt 
    ├─Debian-Swap   254:1    0  14,9G  0 lvm   
    ├─Debian-System 254:2    0  78,6G  0 lvm   /
    └─Debian-Home   254:3    0 382,6G  0 lvm   /home
------

Part of the boot log. Other messages with different values for
"bits_offset" and "type_id" also show up, probably one for each module
that's trying to load.

------
  Volume group "Debian" not found
  Cannot process volume group Debian
BPF:* type_id=86261 bits_offset=960
BPF:
BPF:Invalid name
BPF:
BPF:* type_id=86261 bits_offset=960
BPF:
BPF:Invalid name
BPF:
modprobe: can't load module dm_mod (kernel/drivers/md/dm-mod.ko):
Invalid argument
BPF:* type_id=86261 bits_offset=960
BPF:
BPF:Invalid name
BPF:
cryptsetup: Waiting for encrypted source device UUID=[snip]...
------

-Martijn