Bug 2342785 - After dwarves update, I can't anymore boot custome builded kernel with debug config
Summary: After dwarves update, I can't anymore boot custome builded kernel with debug ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dwarves
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Arnaldo Carvalho de Melo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-29 12:16 UTC by Mikhail
Modified: 2026-06-08 16:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-06-08 16:40:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The photo of boot screen (1.21 MB, image/jpeg)
2025-01-29 12:18 UTC, Mikhail
no flags Details
kernel config (273.17 KB, text/plain)
2025-02-03 20:11 UTC, Mikhail
no flags Details

Description Mikhail 2025-01-29 12:16:56 UTC
After dwarves update, I can't anymore boot custome builded kernels

Here https://docs.fedoraproject.org/en-US/quick-docs/kernel-build-custom/ is described how to build a custom kernel for testing patches and bisecting.

Usually I run this sequence of commands:
1) For building
make clean && make -j32 bzImage && make -j32 modules
2) For installing
sudo make modules_install && sudo make install

With dwarves-1.29-1.fc42.x86_64 the builded kernel always unbootable; instead, the kernel stuck with the messages "failed to validate module ..."

The last workable version of dwarves is 1.27-3.fc42

Reproducible: Always

Comment 1 Mikhail 2025-01-29 12:18:26 UTC
Created attachment 2074329 [details]
The photo of boot screen

Comment 2 Mikhail 2025-02-03 20:11:17 UTC
Created attachment 2075032 [details]
kernel config

Comment 3 Aoife Moloney 2025-02-26 13:49:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 4 Fedora Release Engineering 2026-05-06 12:25:15 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2026-06-08 16:40:26 UTC
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27.

Fedora Linux 42 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.