public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Sudeep Holla <sudeep.holla@arm.com>, Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	LKML <linux-kernel@vger.kernel.org>,
	devicetree@vger.kernel.org, rafael.j.wysocki@intel.com,
	jonathanh@nvidia.com, ulf.hansson@linaro.org
Subject: Re: Kernel crash on boot, arm64 VM
Date: Tue, 3 Jun 2025 08:40:25 +0930	[thread overview]
Message-ID: <d7383d29-516d-4643-aaac-dfd930ec896e@suse.com> (raw)
In-Reply-To: <20250602-solid-coot-of-karma-cfea5e@sudeepholla>



在 2025/6/2 21:42, Sudeep Holla 写道:
> On Mon, Jun 02, 2025 at 11:35:22AM +0100, Will Deacon wrote:
>> [+Sudeep]
>>
> 
> Thanks for adding me.
> 
>> On Mon, Jun 02, 2025 at 10:00:38AM +0930, Qu Wenruo wrote:
>>> It looks like there is a regression related to the device tree/acpi parsing
>>> in the latest upstream kernel branch.
>>
>> I've kept the crash log below, but I suspect this is due to the __free()
>> cleanup path in dt_idle_state_present(), introduced recently by
>> 5836ebeb4a2b ("cpuidle: psci: Avoid initializing faux device if no DT
>> idle states are present").

Reverting works, thanks a lot!

>>
> 
> Hi Qu,
> 
> Do you also have this commit ?
> 
> 39cdf87a97fd ("cpuidle: psci: Fix uninitialized variable in dt_idle_state_present()")

Not yet, the branch I'm using is from btrfs' development branch, which 
is slightly older than the upstream.
(The base commit is a56baa225308 ("Merge tag 'for-6.16-tag' of 
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux"))


Just tried upstream, which also fixed the problem.

So I guess it's really the same problem.
Sorry for the noise.

I'll just notify the btrfs community to rebase the development branch

And thank you both for pointing out the proper fix.

Thanks,
Qu

> 
> Just trying to see if it is same issue or if this something else even
> with the above commit included.
> 

  reply	other threads:[~2025-06-02 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-02  0:30 Kernel crash on boot, arm64 VM Qu Wenruo
2025-06-02 10:35 ` Will Deacon
2025-06-02 12:12   ` Sudeep Holla
2025-06-02 23:10     ` Qu Wenruo [this message]
2025-06-03  9:25       ` Sudeep Holla

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=d7383d29-516d-4643-aaac-dfd930ec896e@suse.com \
    --to=wqu@suse.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sudeep.holla@arm.com \
    --cc=ulf.hansson@linaro.org \
    --cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox