From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: davidgow@google.com, rmoar@google.com, brendanhiggins@google.com,
skhan@linuxfoundation.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [6.3][regression] after commit 7170b7ed6acbde523c5d362c8978c60df4c30f30 my system stuck in initramfs forever
Date: Sat, 25 Feb 2023 19:55:27 +0500 [thread overview]
Message-ID: <CABXGCsNruNKfx3d1dpneRUvn3dCqv_bM93TdJsCLeRYiP3qYaA@mail.gmail.com> (raw)
In-Reply-To: <9f682c4d-e7b7-5e23-84f5-cea4fdac2085@leemhuis.info>
On Sat, Feb 25, 2023 at 7:22 PM Thorsten Leemhuis <linux@leemhuis.info> wrote:
>
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
> On 25.02.23 14:51, Mikhail Gavrilov wrote:
> > new kernel release cycle returning with new bugs
> > Today my system got stuck in initramfs environment after updating to
> > commit d2980d8d826554fa6981d621e569a453787472f8.
> >
> > I still do not understand how to configure the network inside the
> > initramfs environment to grab the logs.
> > Since an attempt to rebuild the initramfs with all modules (dracut
> > --no-hostonly --force) leads to the stuck initramfs environment and
> > impossible entering into initramfs console.
>
> Do you see any error messages? I have problems since Friday morning as
> well (stuck in Fedora's initramfs) and see a lot of BPF warnings like
> "BPF: invalid name" and "failed to validate module". Was able to do a
> screenshot:
>
> https://www.leemhuis.info/files/misc/Screenshot_ktst-f36-x86-64_2023-02-24_07:53:14.png
>
I also seen such messages
https://freeimage.host/i/img-1475.HMPL26l
And if initramfs is configured without --no-hostonly I even could
enter in emergency mode.
https://freeimage.host/i/img-1480.HMPsZ3N
But the module for my Keychrone K1 keyboard couldn't be loaded :(
P.S.: I also use Fedora Rawhide.
--
Best Regards,
Mike Gavrilov.
next prev parent reply other threads:[~2023-02-25 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 13:51 Mikhail Gavrilov
2023-02-25 14:22 ` Thorsten Leemhuis
2023-02-25 14:55 ` Mikhail Gavrilov [this message]
2023-02-25 15:53 ` Thorsten Leemhuis
2023-02-26 1:11 ` David Gow
2023-02-26 6:02 ` Thorsten Leemhuis
2023-02-26 7:31 ` David Gow
2023-02-27 8:21 ` Thorsten Leemhuis
2023-02-26 9:05 ` Mikhail Gavrilov
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=CABXGCsNruNKfx3d1dpneRUvn3dCqv_bM93TdJsCLeRYiP3qYaA@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=rmoar@google.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®