[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7368789d-e2a8-ff1c-f224-b9f1b7896877@amd.com>
Date: Fri, 5 May 2023 00:18:36 +0530
From: Raghavendra K T <raghavendra.kt@....com>
To: Jens Axboe <axboe@...nel.dk>, Ben Greear <greearb@...delatech.com>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Hang loading initrd since last Friday.
On 5/4/2023 10:14 PM, Jens Axboe wrote:
> On 5/4/23 10:38 AM, Raghavendra K T wrote:
>> 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
>
> Can you try and pull:
>
> git://git.kernel.dk/linux for-6.4/block
>
> into current -git and see if that works for you? There's a fix for that
> commit in there.
>
Jens, pulling for-6.4/block helped in my case.
Thank you :)
Powered by blists - more mailing lists