Bug 2014182 - RK3399 - SPL: failed to boot from all boot devices
Summary: RK3399 - SPL: failed to boot from all boot devices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: uboot-tools
Version: 35
Hardware: aarch64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F35FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2021-10-14 15:21 UTC by Paul Whalen
Modified: 2021-10-18 23:47 UTC (History)
10 users (show)

Fixed In Version: uboot-tools-2021.10-2.fc35
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 23:47:18 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Paul Whalen 2021-10-14 15:21:14 UTC 
Description of problem:

Attempting to boot the Firefly2(rk3399) from spl fails with the following error:


U-Boot SPL 2021.10 (Oct 04 2021 - 00:00:00 +0000)
1:19 PM Trying to boot from MMC1
1:19 PM Card did not respond to voltage select! : -110
1:19 PM spl: mmc init failed with error: -95
1:19 PM SPL: failed to boot from all boot devices
1:19 PM ### ERROR ### Please RESET the board ###

Version-Release number of selected component (if applicable):
uboot-tools-2021.10-1.fc35

Also tried uboot-tools-2021.07-2.fc35 which failed with the same error. 

Additional info:
Working uboot-tools-2021.04-3.fc35
Comment 1 Peter Robinson 2021-10-14 15:22:52 UTC 
Yes, confirmed this is also an issue on at least the Rock960 too. Sigh!
Comment 2 Fedora Blocker Bugs Application 2021-10-14 15:24:26 UTC 
Proposed as a Blocker for 35-final by Fedora user pbrobinson using the blocker tracking app because:

 In testing it seems that we've regressed on a number of Rockchip devices, I'm guessing it's actually all rk3399 devices inc the Pinebook Pro. These are blocking devices for aarch64 and IoT.
Comment 3 Peter Robinson 2021-10-14 15:25:25 UTC 
Think I've bisected to the problematic patch. A revert seems quite straight forward, just testing on all my rk3399 devices.
Comment 4 Peter Robinson 2021-10-14 16:11:01 UTC 
The revert has tested good on the Rock960 and firefly3399. Going to test a Pinebook Pro build too, I need to take that to pieces and recover that from a previous failed update so it'll take a little longer.
Comment 5 Adam Williamson 2021-10-15 16:24:00 UTC 
+3 in https://pagure.io/fedora-qa/blocker-review/issue/548 , marking accepted blocker.
Comment 6 Fedora Update System 2021-10-18 06:29:55 UTC 
FEDORA-2021-f1470cb733 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f1470cb733
Comment 7 Fedora Update System 2021-10-18 15:56:08 UTC 
FEDORA-2021-f1470cb733 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f1470cb733`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f1470cb733

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2021-10-18 23:47:18 UTC 
FEDORA-2021-f1470cb733 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.