Hi everyone!
Has anyone experienced the case where certain processes in FS simulation after
boot are blocked by kernel crng init?
I'm using a kernel for ARM64 built from scratch using a buildroot recipe, and
the kernel crng init blocked the sample app i'm supposed to test out for like 7
simulated seconds which is quite a lot.
I looked it up on the net and it seems like reads to /dev/urandom should not
be blocking and would cause a "uninitialized urandom read" warning at best.
I've tried out the pre-built ARM image provided, and it displays such warnings,
but not on my own built system. Anyone has a solution for this? (I asked the
same question on gem5 Slack channel, and Professor Lowe-Power mentioned that
they kinda disabled the rng to do that, but I haven't really found a way
configure that in kconfig.)
Name: Zhang Zhiyuan
Phone: +86-17717877306
E-mail: 18300750...@fudan.edu.cn
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
