Hi Jan,
Am 24.06.2019 um 08:47 schrieb Jan Kratochvil:
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.
this problem only exists for Peter's patch. The latest approach V4 by
Nicolas only touches the ARM clock. So sdhost-bcm2835 doesn't need the
downstream workaround.
Stefan
Thanks,
Jan
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/arm@xxxxxxxxxxxxxxxxxxxxxxx
