Hi Geert, > So some of my local code on top must have impacted the behavior. Any change in temperature? Niklas and I wonder if it is thermal related. > > I am working on an issue where the SCC hangs, but this has to do with > > always providing the SCC clock (SDnH). I don't really see the connection > > of that to RuntimePM yet, though :/ > > Makes sense: this is consistent with the behavior when accessing > registers without enabling the corresponding module clock: it hangs. > So this can happen with other clocks, too. > One more reason not to delegate clock handling to a guest, as doing it > wrong can take down the host, too... You mean when it comes to virtualization? > > Can you test this simple workaround patch instead of the revert just so > > we get an idea if these issues are related? > > Thanks, applying your workaround on top of > renesas-drivers-2019-11-19-v5.4-rc8 fixes the issue. Ok, good to know thanks for testing. Currently, I wonder why reverting the NON_REMOVABLE workaround makes a difference. Maybe it is not temperature related but a some race with RPM? I am debugging in this direction now. But the lockup is still hard to trigger for me. Tried v5.4-rc8 + NON_REMOVABLE patch with no luck. Will try renesas-drivers next. > This fix is part of renesas/topic/sdhi-manual-calib, right? Yes. > And thus has been present in some renesas-drivers release, but was > dropped _before_ the 2019-10-15-v5.4-rc3 release. That would explain why it didn't show up before, right? And don't you have a Ebisu in your board farm, too? Luckily, I have one, too, now. It should be affected. Thanks for the pointers, Wolfram
Attachment:
signature.asc
Description: PGP signature
