Re: System boot failure related to commit 'irqdomain: Switch to per-domain locking'

[Bingbu Cao]

On 2/27/23 7:02 PM, Johan Hovold wrote:
> On Mon, Feb 27, 2023 at 06:46:05PM +0800, Bingbu Cao wrote:
>>
>> Hi, Johan and Zyngier, 
>>
>> I am using a Dell XPS laptop(Intel Processor) just update my
>> Linux kernel to latest tag 6.2.0, and then I see that the kernel
>> cannot boot successfully, it reported:
>> --------------------------------------------
>> Gave up waiting for root file system device. Common problems:
>>  - Boot args (cat /proc/cmdline)
>>    - Check rootdelay= (did the system wait long enough?)
>>  - Missing modules (cat /proc/modules; ls /dev)
>>
>> ALERT! UUID=xxxxxxx does not exist. Dropping to shell!
>> --------------------------------------------
>>
>> And then it drop into initramfs shell, I try to use 'blkid' to
>> get block devices information, but it showed nothing.
>>
>> I also tried add 'rootdelay' and 'rootwait' in bootargs, but it did
>> not work.
>>
>> I am sure that my previous kernel 6.2.0-rc4 work normally, so I
>> did some bisect and found the commit below cause the failure on
>> my system:
>>
>> 9dbb8e3452ab irqdomain: Switch to per-domain locking
> 
> This commit is not in 6.2.0, so I assume you're using a build of Linus's
> master branch (i.e. what will become 6.3-rc1)?

Yes, I am using Linus's master branch, the HEAD is d2980d8d8265.

> 
>> I really have no idea why it cause my problem, but I see just
>> reverting this commit really help me.
>>
>> Do you have any idea?
> 
> Is there anything suspicious in dmesg (e.g. any new warnings or stack
> dumps)?

No crash, just the initramfs warning message I mentioned above.

> 
> One issue with the above commit that affects some systems (e.g. using
> xen virtualisation) has been reported and fixed already. Could you try
> applying the following and see if that helps?
> 
> 	https://lore.kernel.org/all/20230223083800.31347-1-jgross@xxxxxxxx/
>

Thanks, I will try and come back.

> Johan
> 

-- 
Best regards,
Bingbu Cao