From: Andreas Schwab <schwab@suse.de>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: u-boot@lists.denx.de, E Shattow <lucent@gmail.com>,
Minda Chen <minda.chen@starfivetech.com>
Subject: Re: 2025.01-rc2 fails to boot on VisionFive2
Date: Mon, 02 Dec 2024 11:33:22 +0100 [thread overview]
Message-ID: <mvmplmaml1p.fsf@suse.de> (raw)
In-Reply-To: <7610b940-63ae-4b52-a71e-555b2d2db35e@canonical.com> (Heinrich Schuchardt's message of "Thu, 21 Nov 2024 18:21:22 +0100")
On Nov 21 2024, Heinrich Schuchardt wrote:
> That ls works does not mean that the file system is not corrupted.
This obviously has nothing to do with the file system:
StarFive # load mmc 1 0x40200000 efi/boot/bootriscv64.efi
167936 bytes read in 14 ms (11.4 MiB/s)
StarFive # load mmc 1 0x100000000 efi/boot/bootriscv64.efi
mmc fail to send stop cmd
Error reading cluster
Failed to load 'efi/boot/bootriscv64.efi'
StarFive # load mmc 1 0x40200000 efi/boot/bootriscv64.efi
** fs_devread read error - block
** fs_devread read error - block
Can't set block device
Only a reset can revive the MMC interface.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-12-02 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 10:31 2025.01-rc2 fails to boot on VisionFive2 Andreas Schwab
2024-11-21 16:00 ` Heinrich Schuchardt
2024-11-21 16:22 ` Andreas Schwab
2024-11-21 17:21 ` Heinrich Schuchardt
2024-11-21 21:42 ` E Shattow
2024-12-02 10:33 ` Andreas Schwab [this message]
2024-12-02 11:06 ` E Shattow
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=mvmplmaml1p.fsf@suse.de \
--to=schwab@suse.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=lucent@gmail.com \
--cc=minda.chen@starfivetech.com \
--cc=u-boot@lists.denx.de \
/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