From: David Heidelberg <david@ixit.cz>
To: Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [next-20260717] ufshcd issues on Pixel 3
Date: Mon, 20 Jul 2026 23:01:37 +0200 [thread overview]
Message-ID: <9124231d-879f-45b5-b3c7-ab0247799085@ixit.cz> (raw)
In-Reply-To: <fb3bf040-7049-40be-a7e0-54fa624f134d@ixit.cz>
On 19/07/2026 20:14, David Heidelberg wrote:
> Hello!
>
> With next-20260717 I'm receiving these errors on Pixel 3. Previous kernel was
> running there just fine (I think around next-20260703).
I can confirm also with Xiaomi Mi 8 (dipper) so I assume these issues are at
least sdm845-wide.
>
> Dropping the log here, in case someone encounter similar issue.
>
> David
> ---
>
> [ 38.963072] ufshcd-qcom 1d84000.ufshc: ufshcd_abort: Device abort task at tag 13
> [ 38.974926] sd 0:0:0:0: [sda] tag#13 CDB: opcode=0x28 28 00 00 24 bd 2c 00 00
> 4d 00
[...]
prev parent reply other threads:[~2026-07-20 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 18:14 [next-20260717] ufshcd issues on Pixel 3 David Heidelberg
2026-07-20 21:01 ` David Heidelberg [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=9124231d-879f-45b5-b3c7-ab0247799085@ixit.cz \
--to=david@ixit.cz \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-next@vger.kernel.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