The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Raghavendra K T <raghavendra.kt@amd.com>
To: Ben Greear <greearb@candelatech.com>,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>
Subject: Re: Hang loading initrd since last Friday.
Date: Thu, 4 May 2023 22:08:31 +0530	[thread overview]
Message-ID: <835c3de6-7460-226c-96e7-839aeef6064e@amd.com> (raw)
In-Reply-To: <f12a8f23-5aac-b615-300c-38001b9583c2@candelatech.com>

On 5/4/2023 5:19 AM, Ben Greear wrote:
> On 5/2/23 21:46, Linux regression tracking (Thorsten Leemhuis) wrote:
>> 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?
> 
> I am bisecting...it appears to be .config related.  If I skip enabling 
> things
> during bisect, then I do not see the problem.  But I copied my original 
> buggy .config
> into an otherwise good kernel commit, and now it fails.  I'm manually 
> bisecting
> the .config settings....
> 
> Thanks,
> Ben
> 

Hello Ben,

(CCing Jens here)

I was facing same issue too. Surprising I did not hit the same on the
guest VM.

After bisecting, found that Reverting
[9f4107b07b17b5ee68af680150f91227bea2df6f] block: store 
bdev->bd_disk->fops->submit_bio state in bdev

Helped me to boot back the system. Can you please confirm

Thanks
- Raghu

>>
>>>>   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
>>
> 


  reply	other threads:[~2023-05-04 16:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 21:03 Hang loading initrd since last Friday Ben Greear
2023-05-03  2:31 ` Bagas Sanjaya
2023-05-03  4:46   ` Linux regression tracking (Thorsten Leemhuis)
2023-05-03 23:49     ` Ben Greear
2023-05-04 16:38       ` Raghavendra K T [this message]
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=835c3de6-7460-226c-96e7-839aeef6064e@amd.com \
    --to=raghavendra.kt@amd.com \
    --cc=axboe@kernel.dk \
    --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