Comment 4 for bug 1989258

I was booting a test system this afternoon and encountered the OOPS regularly so installed the test kernel on the system and rebooted the system multiple times and did not encounter the OOPS once.

Sep 15 00:01:48 bdmurray-test-virtio-rng kernel: [ 0.000000] Linux version 5.19.0-16-generic (ubuntu@ip-10-0-228-190) (x86_64-linux-gnu-gcc (Ubuntu 12.2.0-1ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.39) #16+arighi SMP PREEMPT_DYNAMIC Mon Sep 12 15:18:26 UTC 2022 (Ubuntu 5.19.0-16.16+arighi-generic 5.19.7)
Sep 15 00:01:48 bdmurray-test-virtio-rng kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-16-generic root=UUID=63a35cf8-4d22-4a79-a93d-eb178abc8c07 ro console=ttyS0

ubuntu@bdmurray-test-virtio-rng:~$ grep "Call Trace" /var/log/syslog
Sep 14 23:09:05 bdmurray-test-virtio-rng kernel: [ 242.903669] Call Trace:
Sep 14 23:09:05 bdmurray-test-virtio-rng kernel: [ 363.735838] Call Trace:
Sep 14 23:09:05 bdmurray-test-virtio-rng kernel: [ 484.568986] Call Trace:
Sep 14 23:42:50 bdmurray-test-virtio-rng kernel: [ 242.911193] Call Trace:
Sep 14 23:42:50 bdmurray-test-virtio-rng kernel: [ 363.736184] Call Trace:
Sep 14 23:42:50 bdmurray-test-virtio-rng kernel: [ 484.567867] Call Trace:
Sep 14 23:42:50 bdmurray-test-virtio-rng kernel: [ 605.399430] Call Trace:
Sep 14 23:42:50 bdmurray-test-virtio-rng kernel: [ 726.231456] Call Trace:
Sep 14 23:42:50 bdmurray-test-virtio-rng kernel: [ 847.063944] Call Trace:
Sep 14 23:42:50 bdmurray-test-virtio-rng kernel: [ 967.895641] Call Trace:

ubuntu@bdmurray-test-virtio-rng:~$ lsmod | grep rng
virtio_rng 16384 0
ubuntu@bdmurray-test-virtio-rng:~$ uname -a
Linux bdmurray-test-virtio-rng 5.19.0-16-generic #16+arighi SMP PREEMPT_DYNAMIC Mon Sep 12 15:18:26 UTC 2022 x86_64 x86_64 x86_64 GNU/Linu
x

So I think this is good to go.