[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1e7dcb2c31beb3ea884879235fb70270fb483731.camel@mediatek.com>
Date: Tue, 5 Aug 2025 07:39:28 +0000
From: Peter Wang (王信友) <peter.wang@...iatek.com>
To: "beanhuo@...ron.com" <beanhuo@...ron.com>, "avri.altman@....com"
<avri.altman@....com>, "neil.armstrong@...aro.org"
<neil.armstrong@...aro.org>, "quic_cang@...cinc.com" <quic_cang@...cinc.com>,
"quic_nitirawa@...cinc.com" <quic_nitirawa@...cinc.com>,
"quic_nguyenb@...cinc.com" <quic_nguyenb@...cinc.com>, "bvanassche@....org"
<bvanassche@....org>, "quic_ziqichen@...cinc.com"
<quic_ziqichen@...cinc.com>, "luca.weiss@...rphone.com"
<luca.weiss@...rphone.com>, "konrad.dybcio@....qualcomm.com"
<konrad.dybcio@....qualcomm.com>, "quic_rampraka@...cinc.com"
<quic_rampraka@...cinc.com>, "junwoo80.lee@...sung.com"
<junwoo80.lee@...sung.com>, "mani@...nel.org" <mani@...nel.org>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>
CC: "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
Tze-nan Wu (吳澤南) <Tze-nan.Wu@...iatek.com>,
"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
"manivannan.sadhasivam@...aro.org" <manivannan.sadhasivam@...aro.org>,
"alim.akhtar@...sung.com" <alim.akhtar@...sung.com>,
"James.Bottomley@...senPartnership.com"
<James.Bottomley@...senPartnership.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] scsi: ufs: core: Don't perform UFS clkscale if host
asyn scan in progress
On Tue, 2025-08-05 at 14:03 +0800, Ziqi Chen wrote:
>
> Hi Peter,
>
> I saw you raised a ACK change to revert this whole change on branch
> Android16-6.12. Without this change, you will meet stuck issue during
> stability reboot test due to request queue quiesce and unquiesce
> mismatch.
>
> This lockdep print just a warning, and as per my analysis before,
> This
> is a misjudgment. But stuck/crash issue is a real issue which has
> real
> instance.
>
> Can you abort your reverting change?
>
>
> BRs,
> Ziqi
Hi Ziqi,
The lockdep warning remains a problem that impacts the
functionality of lockdep. Furthermore, the lockdep issue
is consistently reproducible, unlike the stuck/crash issue,
which is rare and only occurred after the clock scale code
had been in use for several years.
Therefore, I recommend ACK reverting first and then merging
the fixed patch together.
Thanks.
Peter
Powered by blists - more mailing lists