[opensuse-bugs][Bug 1178856] New: modules from custom kernel won´t load
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 Bug ID: 1178856 Summary: modules from custom kernel won�t load Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: malte.gell@gmx.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- First, I used the "kernel" component for filing this issue, but I think this is a bug more somewhere in dracut/udev/systemd. Reproduce this: Take Leap 15.2 with current patches as of 16-nov-2020, take the current Leap kernel source which is linux-5.3.18-lp152.50 and take the Leap 15.2 kernel config from /boot/config-5.3.18-lp152.50-default in other words, use the standard Leap 15.2 kernel config and sources, no modifications and build the kernel. You get the same kernel as shipped with Leap 15.2 which is /boot/vmlinuz-5.3.18-lp152.50-default And now, when booting, the boot process will hang somewhere with this error: dracut-pre-udev modprobe Error could not insert dm_mod : Operation not permitted -------------------------------------------------------------------------------- This looks as you can�t build a kernel on Leap 15.2 with software versions as of 16-nov-2020. Maybe udev, systemd? The kernel built process just works fine, everything builds, mkinitrd ran fine, all modules built, no error. But, when booting, no modules can�t be loaded, boot hangs. I think building and booting a kernel from stable Leap versions should always work, don�t know if you would consider this critical. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 http://bugzilla.opensuse.org/show_bug.cgi?id=1178856#c1 --- Comment #1 from Malte Gell <malte.gell@gmx.de> --- Oh, want to add, this did not happen with previous Leap 15.2 kernel source linux-5.3.18-lp152.47 It just happened now with linux-5.3.18-lp152.50 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 http://bugzilla.opensuse.org/show_bug.cgi?id=1178856#c2 --- Comment #2 from Malte Gell <malte.gell@gmx.de> --- Occurs with and without secure boot enabled, seems not to be secure boot related -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlee@suse.com, | |tiwai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 http://bugzilla.opensuse.org/show_bug.cgi?id=1178856#c3 --- Comment #3 from Malte Gell <malte.gell@gmx.de> --- This bug did not occur with newer kernels like 5.9.8-3 taken from https://download.opensuse.org/repositories/Kernel:/stable/standard/ -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 http://bugzilla.opensuse.org/show_bug.cgi?id=1178856#c4 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs@opensuse.org |jlee@suse.com --- Comment #4 from Takashi Iwai <tiwai@suse.com> --- To be clear: you did kernel by yourself and hit the problem now? Then it's likely the recent kernel change that verifies the CodeSigning extended key. TW kernel still doesn't have it yet, so the problem doesn't appear, I suppose. Reassigned to Joey. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 http://bugzilla.opensuse.org/show_bug.cgi?id=1178856#c5 --- Comment #5 from Malte Gell <malte.gell@gmx.de> --- @Takashi Thanks for this hint. Do I understand correctly, a missing extendedKeyUsage codeSigning declaration in my certificate makes it unusable for module signing? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1178856 http://bugzilla.opensuse.org/show_bug.cgi?id=1178856#c6 --- Comment #6 from Malte Gell <malte.gell@gmx.de> --- Why don�t you add @echo >>$@ "extendedKeyUsage=codeSigning" to certs/Makefile? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com