[Bug 1200461] New: Dracut locks computer, fails to generate initrd file
http://bugzilla.opensuse.org/show_bug.cgi?id=1200461 Bug ID: 1200461 Summary: Dracut locks computer, fails to generate initrd file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: mfdemicco@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 859545 --> http://bugzilla.opensuse.org/attachment.cgi?id=859545&action=edit Photo of screen at moment of freeze When I update to kernel 5.18.1-1 or 5.18.2.1, Dracut locks up my system requiring a power button reboot when creating the initrd file. I also tried installing the latest version of Tumbleweed to another partition, and the installation locked up the computer about 50% into the installation with no creation of the initrd file. The computer freezes at: Dracut: *** Including module: kernel-modules *** When I look in my /boot folder, everything for the kernel is created except for the initrd file I've done a search and can't find anyone that has the same problem. The system runs file with the older kernel 5.17.4-1. I have a legacy BIOS system. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200461
http://bugzilla.opensuse.org/show_bug.cgi?id=1200461#c2
--- Comment #2 from Mike DeMicco
http://bugzilla.opensuse.org/show_bug.cgi?id=1200461
http://bugzilla.opensuse.org/show_bug.cgi?id=1200461#c3
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1200461
http://bugzilla.opensuse.org/show_bug.cgi?id=1200461#c71
Mike DeMicco
(In reply to Franck Bui from comment #58)
or maybe simply try to dump the config attribute with dd once with "bs=4096" and once with "bs=4097" ?
This was buried and not tested, right? But it still makes sense to test...
i.e. is there any difference: strace dd if=config bs=4096 of=/dev/null # should not hang strace dd if=config bs=4097 of=/dev/null # might hang ?
config is the same you passed to cat.
Neither of those commands causes a hang. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com