From: Daniel J Blueman <daniel@quora.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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: [7.1-rc1 BUG] System hang when reading clock controller sysfs 'registers' files
Date: Sat, 2 May 2026 14:40:30 +0800 [thread overview]
Message-ID: <CAMVG2su+V5fcZ9LOC0Qm3bpfnhpbmQdJackc7-RvfztDL_dajw@mail.gmail.com> (raw)
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".
Thanks,
Dan
-- [1]
/sys/kernel/debug/regmap/100000.clock-controller/registers
/sys/kernel/debug/regmap/1fc0000.clock-controller/registers
/sys/kernel/debug/regmap/3d90000.clock-controller/registers
/sys/kernel/debug/regmap/6b6c000.clock-controller-lpass-audio-csr/registers
/sys/kernel/debug/regmap/6ea0000.clock-controller-lpass-tcsr/registers
/sys/kernel/debug/regmap/aaf0000.clock-controller/registers
/sys/kernel/debug/regmap/af00000.clock-controller/registers
/sys/kernel/debug/regmap/dummy-clock-controller@0x0000000001fc0000/registers
--
Daniel J Blueman
next reply other threads:[~2026-05-02 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 6:40 Daniel J Blueman [this message]
2026-05-04 7:49 ` [7.1-rc1 BUG] System hang when reading clock controller sysfs 'registers' files Konrad Dybcio
2026-05-05 14:54 ` Krzysztof Kozlowski
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=CAMVG2su+V5fcZ9LOC0Qm3bpfnhpbmQdJackc7-RvfztDL_dajw@mail.gmail.com \
--to=daniel@quora.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.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