From: Brian Masney <bmasney@redhat.com>
To: Elliot Berman <quic_eberman@quicinc.com>
Cc: Shazad Hussain <quic_shazhuss@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Eric Chanudet <echanude@redhat.com>,
Prasad Sodagudi <psodagud@quicinc.com>,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: sa8755p ufs ice bug: gcc_ufs_phy_ice_core_clk status stuck at 'off'
Date: Mon, 15 Jan 2024 10:47:02 -0500 [thread overview]
Message-ID: <ZaVTdlyhuKFvpz3D@x1> (raw)
In-Reply-To: <37ff80b1-62fa-45ce-b181-955cc887d47d@quicinc.com>
On Tue, Jan 09, 2024 at 01:56:30PM -0800, Elliot Berman wrote:
> Things have been a bit more reliable for me after adding the power-domains.
>
> Are you getting stuck at the same spot or somewhere else?
>
> I've been looking at a similar issue to [1], so I wonder if maybe you're
> facing that instead.
>
> [1]: https://lore.kernel.org/linux-arm-msm/20240104101735.48694-1-laura.nao@collabora.com/T/#m39f7c80b59c750ee4c0082474c5c15b6055927ef
I had some time Friday to setup some automation to bisect this.
Unfortunately, I can't reproduce the hang on a sa8775p with the
upstream ARM64 defconfig on linux-next-20240112. I can reproduce it
using Fedora's arm64 defconfig with the same version of linux-next.
We have a lab move going on this week and our sa8775p boards will be
unavailable. I'll start a bisect with the Fedora config once our boards
are available again.
Brian
prev parent reply other threads:[~2024-01-15 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 2:09 sa8755p ufs ice bug: gcc_ufs_phy_ice_core_clk status stuck at 'off' Brian Masney
2024-01-08 18:14 ` Shazad Hussain
2024-01-08 20:50 ` Brian Masney
2024-01-08 23:35 ` Elliot Berman
2024-01-09 21:44 ` Brian Masney
2024-01-09 21:56 ` Elliot Berman
2024-01-09 23:45 ` Brian Masney
2024-01-15 15:47 ` Brian Masney [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=ZaVTdlyhuKFvpz3D@x1 \
--to=bmasney@redhat.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=echanude@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=psodagud@quicinc.com \
--cc=quic_eberman@quicinc.com \
--cc=quic_shazhuss@quicinc.com \
/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