Bug 2404622

Summary: Problems with CMA allocation on low end Raspberry Pis
Product: [Fedora] Fedora Reporter: Peter Robinson <pbrobinson>
Component: bcm283x-firmwareAssignee: Peter Robinson <pbrobinson>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 43CC: awilliam, kparal, pbrobinson, pwhalen
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: AcceptedFreezeException
Fixed In Version: bcm283x-firmware-20250820-2.0641c5b.fc44 bcm283x-firmware-20250820-2.0641c5b.fc43 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-10-23 23:54:00 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: 245418, 2324226    

Description Peter Robinson 2025-10-16 20:52:02 UTC
In a previous release we had issues with GPU drivers not having enough memory and we fixed that for RPi4 generations by setting the CMA for those devices to 256Mb.

It seems we have a regression, either in the firmware or in the config file where all RPi devices are assigned 256Mb of CMA.

This is fine for devices with 1Gb+ of RAM but causes issues for devices with 512Mb of RAM such as the 3A+ or the Zero2W because 256Mb isn't enough to fit the kernel+initrd to boot.

The issue with either the config file or firmware needs to be bisected and fixed.

Comment 1 Adam Williamson (Red Hat non-Fedora) 2025-10-16 20:57:34 UTC
Proposing as a Final FE, this is obviously the kinda thing we should fix on the release images if possible.

Comment 2 Fedora Update System 2025-10-17 14:59:39 UTC
FEDORA-2025-3f0ba9e1da (bcm283x-firmware-20250820-2.0641c5b.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-3f0ba9e1da

Comment 3 Fedora Update System 2025-10-17 15:03:39 UTC
FEDORA-2025-3f0ba9e1da (bcm283x-firmware-20250820-2.0641c5b.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Peter Robinson 2025-10-17 15:09:01 UTC
I think I have this fixed.

Comment 5 Fedora Update System 2025-10-17 15:18:16 UTC
FEDORA-2025-05499ee7a9 (bcm283x-firmware-20250820-2.0641c5b.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-05499ee7a9

Comment 6 Fedora Update System 2025-10-18 01:41:25 UTC
FEDORA-2025-05499ee7a9 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-05499ee7a9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-05499ee7a9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Kamil Páral 2025-10-20 09:07:03 UTC
Accepted as a freeze exception in https://pagure.io/fedora-qa/blocker-review/issue/1994

Comment 8 Fedora Update System 2025-10-23 23:54:00 UTC
FEDORA-2025-05499ee7a9 (bcm283x-firmware-20250820-2.0641c5b.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.