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.
>> Please try to remove this patch at first
> That's it!
> e9086bdbaaa1f966291adc784f375cc3a24c5762 kernel-5.1.12-300.nocpufreq.fc30.aarch64
> 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
> 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
Yes, and we've already moved to the other driver in rawhide given that
is going upstream. I wanted it to bake there for some time. The other
driver, while known to be far from perfect, has worked fine without a
single reported issue until now. We've carried that patch since 4.17
RC series, and it's saved me from the complaint of "The Raspberry Pi
so slow on Fedora" which I use to get anywhere from 30 to 100 times a
week (yes, I use to log them) and verbal abuse, and once physical
abuse, so I'm not going to apologise for a single problem on a 10 year
old SD card which enabled me to work on other things in my spare time.
We will move the stable releases to the new driver too. I'm yet
undecided whether this is on the 5.1.x series or when Fedora rebases
to 5.2 at around the 5.2.3 time frame, that driver is quite new and
has only been in rawhide for 10 days.