Bug 2124127
| Summary: | Regression booting Fedora on rockchip devices installed on PCIe NVME drives | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter Robinson <pbrobinson> |
| Component: | uboot-tools | Assignee: | Peter Robinson <pbrobinson> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | awilliam, dan, dennis, jean, jordan, kparal, nrevo, ole.d, pbrobinson, pwhalen, robatino |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedBlocker | ||
| Fixed In Version: | uboot-tools-2022.10-0.6.rc4.fc37 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-17 00:33:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2009539 | ||
|
Description
Peter Robinson
2022-09-04 22:26:28 UTC
To make things more interesting it works OK on older 5.17.x kernels and seems to regress in the kernel somewhere between there and 5.19.x Proposed as a Blocker for 37-beta by Fedora user pbrobinson using the blocker tracking app because: This stops Rockchip devices booting when the OS is on NVME drives. This is supported on devices such as the Pinebook Pro FEDORA-2022-c1d9e8daa9 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1d9e8daa9 Discussed during 2022-09-06 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2022-09-06/f37-blocker-review.2022-09-06-16.00.html . Accepted as a blocker as a violation of Basic criterion "All release-blocking images must boot in their supported configurations", on Peter's assurance that supported ARM systems are broken by this bug. FEDORA-2022-c1d9e8daa9 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c1d9e8daa9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1d9e8daa9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-c1d9e8daa9 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-c1d9e8daa9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1d9e8daa9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. During the F37 Beta Go/NoGo meeting, it was unclear whether this problem was fixed, and it was just assumed that it was. Since Beta is now out but we still need proper confirmation for this issue, moving to the Final milestone. Peter, can you verify this was fixed properly in Beta? Thanks! I'd ask Geoff, but not sure he has the relevant hardware. If uboot-tools-2022.10-0.5.rc4.fc37 was included it works (not near the HW this week). I think we can just go ahead and call this good then. That build definitely was in the Beta: https://dl.fedoraproject.org/pub/alt/stage/37_Beta-1.5/Everything/aarch64/os/Packages/u/ FEDORA-2022-c1d9e8daa9 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |