From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Johan Hovold <johan@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
johan+linaro@kernel.org, hsinyi@chromium.org, maz@kernel.org
Subject: Re: System boot failure related to commit 'irqdomain: Switch to per-domain locking'
Date: Mon, 27 Feb 2023 19:25:08 +0800 [thread overview]
Message-ID: <fff4df7a-1c19-72e4-c9ab-aeed27b9bc6d@linux.intel.com> (raw)
In-Reply-To: <Y/yNxQADtJJLFY5W@hovoldconsulting.com>
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@suse.com/
>
Thanks, I will try and come back.
> Johan
>
--
Best regards,
Bingbu Cao
next prev parent reply other threads:[~2023-02-27 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 10:46 System boot failure related to commit 'irqdomain: Switch to per-domain locking' Bingbu Cao
2023-02-27 11:02 ` Johan Hovold
2023-02-27 11:25 ` Bingbu Cao [this message]
2023-02-27 12:47 ` Johan Hovold
2023-02-28 0:45 ` Marc Zyngier
2023-03-01 11:17 ` Bingbu Cao
2023-03-01 14:46 ` Marc Zyngier
2023-03-02 8:55 ` Bingbu Cao
2023-03-02 9:02 ` Johan Hovold
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=fff4df7a-1c19-72e4-c9ab-aeed27b9bc6d@linux.intel.com \
--to=bingbu.cao@linux.intel.com \
--cc=hsinyi@chromium.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.