From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Ben Greear <greearb@candelatech.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Hang loading initrd since last Friday.
Date: Wed, 3 May 2023 06:46:19 +0200 [thread overview]
Message-ID: <ebb280e4-d381-0bf8-d134-0318c5cfdf83@leemhuis.info> (raw)
In-Reply-To: <ZFHHh/m0pkOYIzo7@debian.me>
On 03.05.23 04:31, Bagas Sanjaya wrote:
> On Tue, May 02, 2023 at 02:03:33PM -0700, Ben Greear wrote:
>>
>> Pulling today's upstream 6.3+ tree, my system now hangs loading initrd.
Just to understand this properly: you mean after the boot loader said it
loaded the initramfs, not when the kernel starts using it?
>> Nothing useful is seen on
>> serial console after that. This was working late last week. Other older kernels boot OK, so
>> I think is is related to the kernel.
>
> What is your setup (especially kernel config)?
>
> Is v6.3 works for you? I haven't seen this regression on my computer
> using v6.3.
Ben, you just to be sure might want to check if a kernel image that
currently works still boots if you regenerate its initramfs: maybe the
initramfs generator or something it uses changed recently and is causing
your problem. I've seen a case or two where that was the case.
>> I have not yet started bisect, curious if this is already know problem.
> Certainly you should try bisection.
Yeah.
BTW: What kind of platform is this?
Ciao, Thorsten
next prev parent reply other threads:[~2023-05-03 4:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 21:03 Ben Greear
2023-05-03 2:31 ` Bagas Sanjaya
2023-05-03 4:46 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-05-03 23:49 ` Ben Greear
2023-05-04 16:38 ` Raghavendra K T
2023-05-04 16:44 ` Jens Axboe
2023-05-04 18:48 ` Raghavendra K T
2023-05-04 18:49 ` Jens Axboe
2023-05-04 17:22 ` Ben Greear
2023-05-04 17:59 ` Michael Kelley (LINUX)
2023-05-04 23:46 ` Ben Greear
2023-05-05 0:04 ` Michael Kelley (LINUX)
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=ebb280e4-d381-0bf8-d134-0318c5cfdf83@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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®