From: Adrian Hunter <adrian.hunter@intel.com>
To: raoul via Bugspray Bot <bugbot@kernel.org>,
<ulf.hansson@linaro.org>, <ben.chuang@genesyslogic.com.tw>,
<victor.shih@genesyslogic.com.tw>, <linux-mmc@vger.kernel.org>
Subject: Re: UHS2 init fail
Date: Mon, 23 Jun 2025 11:26:39 +0300 [thread overview]
Message-ID: <0159771a-8e3b-4be3-99f8-b660830560f6@intel.com> (raw)
In-Reply-To: <20250622-b220103c2-e5b82e240db0@bugzilla.kernel.org>
On 22/06/2025 09:40, raoul via Bugspray Bot wrote:
> raoul writes via Kernel.org Bugzilla:
>
> With kernel 6.15.3 and the latest linux-firmware (20250613), same sd card, I'm seeing this now:
>
> [ 396.669202] mmc0: UHS2 Lane sync fail in 150ms.
...
> [ 396.679712] mmc0: failed to initial phy for UHS-II!
There are 3 patches that make all these messages debug-only.
The patches are queued for 6.17 but can be found in linux-next (1)
or mmc tree 'next' branch (2).
6f3a2f9fd8161cb6a04d982ab1027321f7c8709c mmc: sdhci-uhs2: Adjust some error messages and register dump for SD UHS-II card
757611fc4bc52d9e2986e54df1d12c914e2da08c mmc: sdhci: Add a helper function for dump register in dynamic debug mode
790dc30477f2dec029a47ca536bc945557541395 mmc: core: Adjust some error messages for SD UHS-II cards
(1) https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(2) https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git next
> [ 396.925968] mmc0: new UHS-I speed SDR104 SDXC card at address 59b4
> [ 396.947290] mmcblk0: mmc0:59b4 ED2S5 119 GiB
> [ 396.948374] mmcblk0: p1
IIRC the card was not a UHS-II card, so initializing
UHS-I is success. The messages may be ignored, but
will not appear from 6.17 onward.
>
> View: https://bugzilla.kernel.org/show_bug.cgi?id=220103#c2
> You can reply to this message to join the discussion.
next prev parent reply other threads:[~2025-06-23 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 9:10 UHS2 init fail raoul via Bugspray Bot
2025-05-13 7:23 ` Adrian Hunter
2025-06-22 6:40 ` raoul via Bugspray Bot
2025-06-23 8:26 ` Adrian Hunter [this message]
2025-06-24 10:27 ` Ulf Hansson
2025-06-23 15:05 ` raoul via Bugspray Bot
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=0159771a-8e3b-4be3-99f8-b660830560f6@intel.com \
--to=adrian.hunter@intel.com \
--cc=ben.chuang@genesyslogic.com.tw \
--cc=bugbot@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=victor.shih@genesyslogic.com.tw \
/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