RPi5 has troubles booting when faster memory access is enabled

[igorpecovnik]

Description

Lets (temporally) disable this feature as it doesn't work well and wait until things are fixed upstream / research problem deeper some other day.

How Has This Been Tested?

• Rpi5 boots with rpi4 image

Checklist:

• My changes generate no new warnings

[pyavitz]

I'm not against this; but at the end of the day this is a benefit loss. If there is an easy way to disable the ramlog service on these imgs, until one figures out why it isn't compat with 16k page size, I would go that road.

With that said you are only losing a 7+% performance increase in random memory accesses. Not sure many people are gonna even notice.

[igorpecovnik]

If there is an easy way to disable the ramlog service

ramlog is not doing anything extraordinary. I would suspect this trouble will surface up somewhere else. Yeah, we loose some performance, but we get full functionality ... so I hope this gets enabled back soon. We just need to monitor what is going on. Nothing apparent on quick scan of https://github.com/raspberrypi/linux/issues