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:10 +0000 [thread overview]
Message-ID: <20240922-b218821c3-354fcfd0cded@bugzilla.kernel.org> (raw)
In-Reply-To: <20240922-b218821c0-26591b0a1008@bugzilla.kernel.org>
Thomas Haschka writes via Kernel.org Bugzilla:
I am using the gentoo patchset on the kernel, further patched in with camera drivers for the surface go 2.
None of these patches should touch the rstx_pci driver or carddriver directory.
I run the root filesystem on the SD card. To be more specific a
SanDisc 128GB A2 V30. Therefore the system fails once the sd-card does not respond.
The failure is probably rare for people not running a root filesystem on the SSD as the carddreader seems to work fine, booting the system, but seems to fail after about 10-15 minutes, of activity, as stated with dmesg showing the error message above:
mmc0: error -95 doing runtime resume
and the filesystem not responding anymore. The SD Card is ext4 formatted, without mounted with journaling turned off.
I will provide kernel configuration files for both 6.5.5 and 6.8.9 later that day, in the hope that it helps.
As said reverting to 6.5.5 works fine only yielding a
mmc0: cannot verify signal voltage switch
but I get this error since years, every other minute, on this system - also with different SD Cards, without any noticeable effect.
View: https://bugzilla.kernel.org/show_bug.cgi?id=218821#c3
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev 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 [this message]
2024-09-22 13:35 ` Thomas Haschka via Bugspray Bot
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-b218821c3-354fcfd0cded@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.