On 2022-06-18 11:25:39 [+0200], Mike Galbraith wrote: > I haven't done any digging to see why this now happens where it > previously did not. I don't see where interrupts have been disabled but they have been. The printk path should yell earlier but did not the crng path is kind of late and I don't see anything obvious in between. Sebastian
