From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Ben Dooks" <ben.dooks@codethink.co.uk>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Bin Meng <bmeng.cn@gmail.com>
Subject: Re: [PATCH] hw/sd: print bad s->arglen in unexpected response
Date: Wed, 23 Jul 2025 18:30:39 +0200 [thread overview]
Message-ID: <f20200a3-1391-45d9-961d-df2fc5996341@linaro.org> (raw)
In-Reply-To: <197dd05a-eda5-44e0-9592-b886e953086f@codethink.co.uk>
Hi Ben,
On 23/7/25 16:55, Ben Dooks wrote:
> I am currently trying to track down two errors with mmc-spi.
>
> The first looks like u-boot is sending a couple of CMDs (9, 10)
> in the wrong state (currently this works however with a real SD
> card) so I have a tmp-fix in to just ignore the two checks in
> these and u-boot is now working.
>
> I'm also getting multiple versions of linux failing with QEMU10
> on Debian/testing and my own close to the current git tree with
> Linux and CMD13...
>
> [ 0.579845] EXT4-fs (mmcblk0): INFO: recovery required on readonly
> filesystem
> [ 0.580222] EXT4-fs (mmcblk0): write access will be enabled during
> recovery
> ssi_sd: error: Unexpected response to cmd 13, arglen=16
> ssi_sd: error: Unexpected response to cmd 13, arglen=16
> ssi_sd: error: Unexpected response to cmd 13, arglen=16
> ssi_sd: error: Unexpected response to cmd 13, arglen=16
CMD13's arg len should be 2 in SSI mode.
> Then the system stops working.
>
> Systems are riscv sifive_u and my own cva6 machine
Do you mind sharing a reproducer?
Even better if contributed as a functional test :)
(see tests/functional/test_arm_sx1.py for example).
Regards,
Phil.
next prev parent reply other threads:[~2025-07-23 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 9:05 [PATCH] hw/sd: print bad s->arglen in unexpected response Ben Dooks
2025-07-23 12:46 ` Alex Bennée
2025-07-23 13:38 ` Peter Maydell
2025-07-23 14:55 ` Ben Dooks
2025-07-23 16:30 ` Philippe Mathieu-Daudé [this message]
2025-07-24 9:45 ` Ben Dooks
2025-07-24 10:32 ` Ben Dooks
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=f20200a3-1391-45d9-961d-df2fc5996341@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=ben.dooks@codethink.co.uk \
--cc=bmeng.cn@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).