From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Daniel J Blueman <daniel@quora.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
Taniya Das <taniya.das@oss.qualcomm.com>,
Abel Vesa <abel.vesa@oss.qualcomm.com>,
Imran Shaik <imran.shaik@oss.qualcomm.com>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: [7.1-rc1 BUG] System hang when reading clock controller sysfs 'registers' files
Date: Tue, 5 May 2026 16:54:20 +0200 [thread overview]
Message-ID: <c2e4c958-fb89-47da-bbd1-87871374d812@kernel.org> (raw)
In-Reply-To: <d58b8c6a-c837-4bec-8ffb-dd9d7b12906b@oss.qualcomm.com>
On 04/05/2026 09:49, Konrad Dybcio wrote:
> On 5/2/26 8:40 AM, Daniel J Blueman wrote:
>> On a Qualcomm X1 Hamoa-based Lenovo Slim7x with upstream 7.1-rc1, when
>> reading any of the /sys/kernel/debug/regmap/*clock*/registers files
>> [1] (which could happen inadvertently with grep), we see a complete
>> and immediate system hang.
>>
>> If this relates to clock/power gating, it could be avoided by
>> inhibiting that prior to the read. It also reproduces when booted with
>> "clk_ignore_unused pd_ignore_unused".
>
> Does this attempt to read the entire regmap-ped address space of the
> device?
>
> If so, that's probably ""intended"", since there are TZ-only (and other
> forms of secure) registers sprinkled throughout the range
Yep. See also commit d81901a5406e ("clk: qcom: dispcc-sm8750: Allow
dumping regmap").
We might need something similar for all other devices.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-05-05 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 6:40 [7.1-rc1 BUG] System hang when reading clock controller sysfs 'registers' files Daniel J Blueman
2026-05-04 7:49 ` Konrad Dybcio
2026-05-05 14:54 ` Krzysztof Kozlowski [this message]
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=c2e4c958-fb89-47da-bbd1-87871374d812@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=daniel@quora.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=imran.shaik@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=taniya.das@oss.qualcomm.com \
--cc=vladimir.zapolskiy@linaro.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