From: Bart Van Assche <bvanassche@acm.org>
To: Tj <tj.iam.tj@proton.me>, Peter Wang <peter.wang@mediatek.com>,
linux-next@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regression: scsi: ufs: core: Avoid IRQ thread wakeup during active UIC command
Date: Wed, 18 Mar 2026 10:49:34 -0700 [thread overview]
Message-ID: <f0e6452b-868f-4d57-b2cc-98daf16cdecd@acm.org> (raw)
In-Reply-To: <abmMptgPR581bPUS@mail.iam.tj>
On 3/17/26 10:17 AM, Tj wrote:
> #regzbot ^introduced: 6475cfb81fc4f6175b6d15d1c205a5168dc10b46
>
> I've had to revert this commit because it breaks UFS on Samsung Book2
> W737 sdm850. Below is transcribed from a blurry video so apologies if it
> is not exact:
>
> | BUG: Invalid wait context |
> ufshcd-qcom 1d84000.ufshc: uic cmd 0x1 with arg3 0x0 completion timeout
> 7.0.0-rc3-next-202603110sdm845 #103 Not tainted
> -----------------------------
> ufshcd-qcom 1d84000.ufshc: dme-get: attr-id 0x41 failed 0 retries
> swapper/0/0 is trying to lock:
> ffff000087ba4048 (shost->host_lock)(....)-(3:3). at: ufshcd_sl_intr+0x3dc/0x7a0
Thanks for having reported this. Is this perhaps the same issue as what
has been reported by Marek in
https://lore.kernel.org/linux-scsi/1f88b91c-59e6-4347-84c2-50b7cf106c47@samsung.com/?
I propose to revert commit 6475cfb81fc4 ("scsi: ufs: core: Avoid IRQ
thread wakeup during active UIC command") if a fix is not found before
the end of this week.
Bart.
prev parent reply other threads:[~2026-03-18 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 17:17 Regression: scsi: ufs: core: Avoid IRQ thread wakeup during active UIC command Tj
2026-03-18 17:49 ` Bart Van Assche [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=f0e6452b-868f-4d57-b2cc-98daf16cdecd@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=martin.petersen@oracle.com \
--cc=peter.wang@mediatek.com \
--cc=tj.iam.tj@proton.me \
/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