Which was fixed in 5.10 by:
commit 6246d7c9d15aaff0bc3863f67900c6a6e6be921b
Author: Bean Huo <bean...@micron.com>
Date: Wed Dec 2 21:23:20 2020 +0100
mmc: block: Fixup condition for CMD13 polling for RPMB requests
The CMD13 polling is needed for commands with R1B responses. In commit
a0d4c7eb71dd ("mmc: block: Add CMD13 polling for MMC IOCTLS with R1B
response"), the intent was to introduce this for requests targeted to the
RPMB partition. However, the condition to trigger the polling loop became
wrong, leading to unnecessary polling. Let's fix the condition to avoid
this.
Fixes: a0d4c7eb71dd ("mmc: block: Add CMD13 polling for MMC IOCTLS with R1B
response")
Cc: sta...@vger.kernel.org
Reported-by: Zhan Liu <zl...@micron.com>
Signed-off-by: Zhan Liu <zl...@micron.com>
Signed-off-by: Bean Huo <bean...@micron.com>
Link: https://lore.kernel.org/r/20201202202320.22165-1-huob...@gmail.com
Signed-off-by: Ulf Hansson <ulf.hans...@linaro.org>
Which we have in the latest 5.8 raspi kernel. I should always test the
latest kernel. Sigh.
** Changed in: linux-raspi (Ubuntu Groovy)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1917633
Title:
Card stuck in wrong state! card_busy_detect status: 0x700
Status in linux-raspi package in Ubuntu:
New
Status in linux-raspi source package in Groovy:
Invalid
Bug description:
Running sdtool from https://github.com/BertoldVdb/sdtool yields:
$ sudo ./sdtool /dev/mmcblk0 status
[+] Found RCA for /dev/mmcblk0: AAAA.
Error 110
[-] Failed to send command: Connection timed out
[ 43.004983] sdhost-bcm2835 3f202000.mmc: Card stuck in wrong state!
card_busy_detect status: 0x700
[ 43.102348] sdhost-bcm2835 3f202000.mmc: sdhost_busy_irq: intmask 00000440
[ 53.224992] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
interrupt.
[ 53.285006] sdhost-bcm2835 3f202000.mmc: __mmc_blk_ioctl_cmd: cmd error
-110
[ 63.465196] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
interrupt.
Tested both arm64 and armhf on 2B (armhf only), 3B, 3B+ and 4B.
Focal 5.4 seems to be OK.
Groovy 5.8 fails on:
- 2B armhf
- 3B+ armhf
- 4B arm64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1917633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
