All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Haschka via Bugspray Bot <bugbot@kernel.org>
To: linux-mmc@vger.kernel.org, ulf.hansson@linaro.org
Subject: Re: RTS522A fails with "mmc: error -95 doing runtime resume" on Microsoft Surface Go 2
Date: Sun, 22 Sep 2024 13:35:11 +0000	[thread overview]
Message-ID: <20240922-b218821c4-637a3f6d7112@bugzilla.kernel.org> (raw)
In-Reply-To: <20240922-b218821c0-26591b0a1008@bugzilla.kernel.org>

Thomas Haschka writes via Kernel.org Bugzilla:

The problem starts already at kernel 6.6, at least at 6.6.52

I also tried to modify: 

drivers/mmc/core/core.c

essentially reverting it back to it's 6.5.5 state:

diff linux-6.5.5-gentoo/drivers/mmc/core/core.c linux-6.6.52-gentoo/drivers/mmc/core/core.c 
554c554,556
<       mmc_wait_for_cmd(host, &cmd, 0);
---
>       mmc_wait_for_cmd(host, &cmd, MMC_CMD_RETRIES);
> 
>       mmc_poll_for_busy(host->card, MMC_CQE_RECOVERY_TIMEOUT, true,
>       MMC_BUSY_IO);
562c564
<       err = mmc_wait_for_cmd(host, &cmd, 0);
---
>       err = mmc_wait_for_cmd(host, &cmd, MMC_CMD_RETRIES);
564a567,569
> 
>       if (err)
>               err = mmc_wait_for_cmd(host, &cmd, MMC_CMD_RETRIES);

doing this I was semi successful, as

mmc0: error -95 doing runtime resume

still showed up, but after around 1 minute of waiting the driver seemed to have recovered and continued working, until failing again a few minutes later. Which causes large long stalls on when trying to use the card.

View: https://bugzilla.kernel.org/show_bug.cgi?id=218821#c4
You can reply to this message to join the discussion.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)


  parent reply	other threads:[~2024-09-22 13:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 13:35 RTS522A fails with "mmc: error -95 doing runtime resume" on Microsoft Surface Go 2 Thomas Haschka via Bugspray Bot
2024-09-22 13:35 ` The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot
2024-09-22 13:35   ` The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot
2024-10-08 14:55     ` Ulf Hansson
2024-09-22 13:35 ` Thomas Haschka via Bugspray Bot
2024-09-22 13:35 ` Thomas Haschka via Bugspray Bot [this message]
2024-09-22 13:35 ` Thomas Haschka via Bugspray Bot
2024-09-22 13:35 ` Thomas Haschka via Bugspray Bot
2024-09-24 12:30 ` Thomas Haschka via Bugspray Bot
2024-12-31  9:05 ` Thomas Haschka via Bugspray Bot
2024-12-31  9:05 ` Thomas Haschka via Bugspray Bot
2025-01-02  6:30 ` Adrian Hunter via Bugspray Bot
2025-02-21 13:40 ` Thomas Haschka via Bugspray Bot
2025-02-21 15:00 ` Thomas Haschka via Bugspray Bot
2025-03-11 12:55 ` Adrian Hunter via Bugspray Bot
2025-03-12 12:45   ` Ulf Hansson
2025-03-13 11:05 ` Thomas Haschka via Bugspray Bot
2025-03-13 13:34   ` Ulf Hansson
2025-03-13 11:05 ` Thomas Haschka 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=20240922-b218821c4-637a3f6d7112@bugzilla.kernel.org \
    --to=bugbot@kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.