Hi Phil, On Tue, Jun 7, 2022 at 10:47 AM Phil Elwell <phil@xxxxxxxxxxxxxxx> wrote: > Thanks for the quick response, but that doesn't work for me either. Let me say > again that I'm on a downstream kernel (rpi-5.15.y) so this may not be a > universal problem, but merging either of these fixing patches would be fatal for us. Alright, thanks. And I'm guessing you don't currently have a problem *without* either of the fixing patches, because your device tree doesn't use rng-seed. Is that right? In anycase, I sent in a revert to get all the static branch stuff out of stable -- https://lore.kernel.org/stable/20220607084005.666059-1-Jason@xxxxxxxxx/ -- so the "urgency" of this should decrease and we can fix this as normal during the 5.19 cycle. But with that said, I do want to get this fixed as soon as possible still. I'll be back at my desk tonight and will finally have access to real hardware again. Are you hitting this by loading a 32bit kernel on a raspi4? Or running a 32bit kernel on the raspi1? Or some other combo? Jason
