I don't know yet if related, but I also observed the following: syslog:May 21 17:25:27 ubuntu kernel: [ 0.000000] random: get_random_bytes called from start_kernel+0x99/0x4fd with crng_init=0 syslog:May 21 17:25:27 ubuntu kernel: [ 1.902484] random: lvm: uninitialized urandom read (4 bytes read)
Could the missing ttyS* have an effect on entropy ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in linux package in Ubuntu: Confirmed Bug description: kernel get stucks at boot if console=ttyS* is specified in the kernel cmdline and that serial HW isn't available on the system. Reproduced with: 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next (mainline) Removing the non-existent 'console=ttyS*' parameter fixes the situation. I tested it using KVM/qemu, but it has been brought to my attention that it was reproducible in VMware as well. I think it is safe to say that it is unlikely to be specifics to a certain virtualization technology type. Didn't test on baremetal yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
