On Mon, Jun 24, 2019 at 7:47 AM Jan Kratochvil <[email protected]> wrote: > > On Sun, 23 Jun 2019 22:11:55 +0200, Stefan Wahren wrote: > > Am 23.06.19 um 21:22 schrieb Jan Kratochvil: > > > So it looks as a Fedora-specific regression somewhere in the 5.0.x series. > > > > Please wait, i see that fc30 still uses this experimental cpufreq patch, > > which is very dangerous. > > > > https://src.fedoraproject.org/rpms/kernel/blob/f30/f/bcm2835-cpufreq-add-CPU-frequency-control-driver.patch > > > > Please try to remove this patch at first > > That's it! > e9086bdbaaa1f966291adc784f375cc3a24c5762 > kernel-5.1.12-300.nocpufreq.fc30.aarch64 PASS > https://koji.fedoraproject.org/koji/taskinfo?taskID=35768074 > > Only now I understand why it successfully proceeds with the whole boot and it > breaks by that error only after it becomes idle at the login screen. > sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware interrupt. > > I have seen now a discussion > https://github.com/lategoodbye/rpi-zero/issues/32 > there is some principial problem all drivers need an update for that frequency > scaling, so maybe sdhost-bcm2835 also still needs an update.
It's weird it only started causing issues late in the 5.0.x cycle as that driver hasn't changed for some time and we've shipped it for a couple of releases now (since June 2018). There's a different driver in the 5.2 rc series from 5.2.0-0.rc4.git2.1 and later builds, you might want to try rc5 https://koji.fedoraproject.org/koji/buildinfo?buildID=1288824 _______________________________________________ arm mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
