In recent time we started putting the bcm2835-dma in the initrd because it offered a substancial bump in performance but it seems this has caused as many issues as the performance bump it provides including non booting devices. This should be dropped until the problems are worked out. It affects both the Raspberry Pi 2 and 3 in a number of situations that aren't fully known yet.
This has been submitted as an update, seems bodhi hasn't updated the bug https://bodhi.fedoraproject.org/updates/FEDORA-2017-6139efd06a
Proposed as a Blocker for 26-alpha by Fedora user pbrobinson using the blocker tracking app because: Raspberry Pi is a key ARMv7 platform device. Fix is in place so shouldn't slip, doesn't impact other ARM devices or the rest of the distro
(In reply to Fedora Blocker Bugs Application from comment #2) > Proposed as a Blocker for 26-alpha by Fedora user pbrobinson using the > blocker tracking app because: > > Raspberry Pi is a key ARMv7 platform device. Fix is in place so shouldn't > slip, doesn't impact other ARM devices or the rest of the distro Peter, could you identify which criterion on https://fedoraproject.org/wiki/Fedora_26_Alpha_Release_Criteria you feel this is violating? Otherwise, this sounds more like a Freeze Exception request.
Some users are reporting a kernel oops on the Raspberry Pi 3, a supported hardware platform. Citing criteria "Release-blocking ARM disk images must boot to the initial-setup utility."
It seems pretty harmless; I'm in favor of granting it at LEAST an FE and getting it into the compose that's about to kick off.
(In reply to Stephen Gallagher from comment #5) > It seems pretty harmless; I'm in favor of granting it at LEAST an FE and > getting it into the compose that's about to kick off. That should have read: "The fix seems pretty harmless"
+1 FE since the change won't impact other things.
+1 FE
+1 FE/blocker , change is self contained
+1 blocker for me, if Pi 3 is a supported ARM platform and this breaks boot on it, seems pretty straightforward.
Discussed during the 2017-03-27 blocker review meeting: [1] The decision was made to classify this bug as an AcceptedBlocker as it violates the following Alpha criteria: "All release-blocking images must boot in their supported configurations." [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-03-27/f26-blocker-review.2017-03-27-16.01.txt
bcm283x-firmware-20170324-1.76fc4dd.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-6139efd06a
bcm283x-firmware-20170324-1.76fc4dd.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
clearing needinfo