From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux5.15: boot process _seems_ stuck at "loading initramfs ..."
Date: Fri, 12 Nov 2021 11:09:37 +0100 [thread overview]
Message-ID: <20211112100937.KI0E-qDiJlaMTD-WjongAXyoDxihR5bn7sxHTod_aQ8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34035@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/34035#issuecomment-966979648
Comment:
Indeed.
If it matters, I'm using `booster` initramfs generator (it's currently a pr in void), but from the forum post, it seems at least also mkinitcpio also has it, not sure about dracut.
I wonder if this new config option triggers some previously hidden kernel bug or race condition..
Would it be possible to disable it just for 5.15.2, to see if this is the culprit, without me recompiling void's kernel :) ?
next prev parent reply other threads:[~2021-11-12 10:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 19:46 [ISSUE] " leahneukirchen
2021-11-11 19:47 ` leahneukirchen
2021-11-12 10:09 ` dkwo [this message]
2021-11-12 12:35 ` leahneukirchen
2021-11-12 13:34 ` leahneukirchen
2021-11-12 16:32 ` chili-b
2021-11-12 16:40 ` leahneukirchen
2021-11-12 17:56 ` dkwo
2021-11-12 18:04 ` leahneukirchen
2021-11-12 18:28 ` dkwo
2021-11-12 18:41 ` dkwo
2021-11-12 18:44 ` leahneukirchen
2021-11-12 18:48 ` zdykstra
2021-11-12 18:52 ` newbluemoon
2021-11-12 18:58 ` newbluemoon
2021-11-12 19:44 ` [ISSUE] [CLOSED] " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211112100937.KI0E-qDiJlaMTD-WjongAXyoDxihR5bn7sxHTod_aQ8@z \
--to=dkwo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).