On Mon, Jun 26, 2023 at 03:15:08PM +0000, Sami Korkalainen wrote: > On Sunday, June 25th, 2023 at 22.21, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > Sami - can you try to revert the revert: > > > > git revert 69cbeb61ff9093a9155cb19a36d633033f71093a > > > > but then additionally in drivers/firmware/efi/efi.c, just change the > > > > static DECLARE_WORK(work, refresh_nv_rng_seed); > > schedule_work(&work); > > > > in refresh_nv_rng_seed_notification() to be something like > > > > static DECLARE_DELAYED_WORK(work, refresh_nv_rng_seed); > > schedule_delayed_work(&work, 120*HZ); > > > > to make the work fire two minutes after boot? > > > > The question then being: > > > > (a) does that fix the boot for you (maybe it's the schedule_work > > itself that confused things, however unlikely that sounds) > > > > (b) if it does boot, do you notice something happening two minutes > > after booting? > > I did that and: > (a) It does boot fine with this change. Interesting! And after around 4 minutes, you don't see any stall warnings in your dmesg? > (b) I don't notice anything happening at two minutes after booting. I > can see there is a random-seed file located in EFI partition, but it > does not change two minutes after boot (but it is different each > boot). That's an unrelated file. This has to do with EFI variables.
