Your message dated Wed, 19 Oct 2022 00:18:36 +0200
with message-id <[email protected]>
and subject line Re: Failure to load kernel modules at boot time
has caused the Debian Bug report #1014062,
regarding Failure to load kernel modules at boot time
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1014062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014062
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: system2
Version: 247.3-7
Dear Maintainers,
At boot time, linux produces a series of error messages stating that a
kernel module cannot be loaded.
Inspecting the output of journalctl, I find the following lines:
Jun 29 16:53:25 AREPPIM001 systemd-modules-load[218]: Failed to insert
module 'firewire_sbp2': Key was rejected by service
Jun 29 16:53:25 AREPPIM001 systemd[1]: systemd-modules-load.service:
Main process exited, code=exited, status=1/FAILURE
Jun 29 16:53:25 AREPPIM001 systemd[1]: systemd-modules-load.service:
Failed with result 'exit-code'.
Jun 29 16:53:25 AREPPIM001 systemd[1]: Failed to start Load Kernel Modules.
Jun 29 16:53:30 AREPPIM001 systemd-modules-load[442]: Failed to insert
module 'firewire_sbp2': Key was rejected by service
Jun 29 16:53:30 AREPPIM001 systemd[1]: systemd-modules-load.service:
Main process exited, code=exited, status=1/FAILURE
Jun 29 16:53:30 AREPPIM001 systemd[1]: systemd-modules-load.service:
Failed with result 'exit-code'.
Jun 29 16:53:30 AREPPIM001 systemd[1]: Failed to start Load Kernel Modules.
Jun 29 16:53:35 AREPPIM001 systemd-modules-load[458]: Failed to insert
module 'firewire_sbp2': Key was rejected by service
Jun 29 16:53:35 AREPPIM001 systemd-fsck[456]: /dev/sda7: clean,
10088/720896 files, 376406/2880512 blocks
Jun 29 16:53:35 AREPPIM001 systemd[1]: systemd-modules-load.service:
Main process exited, code=exited, status=1/FAILURE
Jun 29 16:53:35 AREPPIM001 systemd[1]: systemd-modules-load.service:
Failed with result 'exit-code'.
Jun 29 16:53:35 AREPPIM001 systemd[1]: Failed to start Load Kernel Modules.
All three attempts at loading the module firewire_sbp2 take place during
the same boot sequence.
The error was definitely introduced by Bullseye / Debian 11, since the
same machine under Buster / Debian 10 did not exhibit this behaviour:
Jun 21 16:06:42 AREPPIM001 kernel: firewire_ohci 0000:02:01.1: added
OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x2
Jun 21 16:06:42 AREPPIM001 kernel: firewire_core 0000:02:01.1: created
device fw0: GUID 314fc000300d2430, S400
Jun 21 16:06:42 AREPPIM001 systemd-modules-load[204]: Inserted module
'firewire_sbp2'
The machine is running Linux 5.10.0-15-686-pae #1 SMP Debian 5.10.120-1
(2022-06-09) i686 GNU/Linux.
Sincerely
Eduardo Casais
--- End Message ---
--- Begin Message ---
On Wed, 29 Jun 2022 17:20:17 +0200 Eduardo Casais
<[email protected]> wrote:
Package: system2
Version: 247.3-7
Dear Maintainers,
At boot time, linux produces a series of error messages stating that a
kernel module cannot be loaded.
Inspecting the output of journalctl, I find the following lines:
Jun 29 16:53:25 AREPPIM001 systemd-modules-load[218]: Failed to insert
module 'firewire_sbp2': Key was rejected by service
This looks like you are using secure boot and the module is unsigned
and/or the signing key was rejected.
systemd-modules-load is only the messenger here, not the source of the
problem.
Thus closing the bug report against systemd.
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
