Comment 2 for bug 1905984

Looking through the journal further, I do see non-NVidia call traces such as:

Nov 27 09:43:52 surprise kernel: INFO: task qemu-system-x86:16736 blocked for more than 120 seconds.
Nov 27 09:43:52 surprise kernel: Tainted: P OEL 5.8.0-29-generic #31-Ubuntu
Nov 27 09:43:52 surprise kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 27 09:43:52 surprise kernel: qemu-system-x86 D 0 16736 1 0x00000320
Nov 27 09:43:52 surprise kernel: Call Trace:
Nov 27 09:43:52 surprise kernel: __schedule+0x212/0x5d0
Nov 27 09:43:52 surprise kernel: ? usleep_range+0x90/0x90
Nov 27 09:43:52 surprise kernel: schedule+0x55/0xc0
Nov 27 09:43:52 surprise kernel: schedule_timeout+0x10f/0x160
Nov 27 09:43:52 surprise kernel: ? do_sync_core+0x1d/0x20
Nov 27 09:43:52 surprise kernel: __wait_for_common+0xa8/0x150
Nov 27 09:43:52 surprise kernel: wait_for_completion+0x24/0x30
Nov 27 09:43:52 surprise kernel: __wait_rcu_gp+0x11b/0x120
Nov 27 09:43:52 surprise kernel: synchronize_rcu+0x67/0x70
Nov 27 09:43:52 surprise kernel: ? __call_rcu+0x250/0x250
Nov 27 09:43:52 surprise kernel: ? __bpf_trace_rcu_utilization+0x10/0x10
Nov 27 09:43:52 surprise kernel: account_event+0x1e8/0x1f0
Nov 27 09:43:52 surprise kernel: perf_event_alloc+0x77e/0x920
Nov 27 09:43:52 surprise kernel: ? kvm_perf_overflow+0x40/0x40 [kvm]
Nov 27 09:43:52 surprise kernel: perf_event_create_kernel_counter.part.0+0x21/0x160
Nov 27 09:43:52 surprise kernel: perf_event_create_kernel_counter+0xf/0x20
Nov 27 09:43:52 surprise kernel: pmc_reprogram_counter+0x105/0x190 [kvm]
Nov 27 09:43:52 surprise kernel: reprogram_gp_counter+0x194/0x210 [kvm]
Nov 27 09:43:52 surprise kernel: amd_pmu_set_msr+0x17d/0x190 [kvm_amd]
Nov 27 09:43:52 surprise kernel: kvm_pmu_set_msr+0x4e/0x60 [kvm]
Nov 27 09:43:52 surprise kernel: kvm_set_msr_common+0x4cc/0xf00 [kvm]
Nov 27 09:43:52 surprise kernel: svm_set_msr+0x39d/0x6e0 [kvm_amd]
Nov 27 09:43:52 surprise kernel: __kvm_set_msr+0x8a/0x150 [kvm]
Nov 27 09:43:52 surprise kernel: kvm_emulate_wrmsr+0x3c/0x120 [kvm]
Nov 27 09:43:52 surprise kernel: handle_exit+0x39a/0x420 [kvm_amd]
Nov 27 09:43:52 surprise kernel: ? kvm_set_cr8+0x22/0x40 [kvm]
Nov 27 09:43:52 surprise kernel: vcpu_enter_guest+0x862/0xd90 [kvm]
Nov 27 09:43:52 surprise kernel: ? kvm_apic_has_interrupt+0x41/0x80 [kvm]
Nov 27 09:43:52 surprise kernel: ? kvm_cpu_has_interrupt+0x7a/0x90 [kvm]
Nov 27 09:43:52 surprise kernel: ? kvm_vcpu_has_events+0x134/0x190 [kvm]
Nov 27 09:43:52 surprise kernel: vcpu_run+0x76/0x240 [kvm]
Nov 27 09:43:52 surprise kernel: kvm_arch_vcpu_ioctl_run+0x9f/0x2b0 [kvm]
Nov 27 09:43:52 surprise kernel: kvm_vcpu_ioctl+0x247/0x600 [kvm]
Nov 27 09:43:52 surprise kernel: ksys_ioctl+0x8e/0xc0
Nov 27 09:43:52 surprise kernel: __x64_sys_ioctl+0x1a/0x20
Nov 27 09:43:52 surprise kernel: do_syscall_64+0x49/0xc0
Nov 27 09:43:52 surprise kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Nov 27 09:43:52 surprise kernel: RIP: 0033:0x7fc2853b16d7
Nov 27 09:43:52 surprise kernel: Code: Bad RIP value.
Nov 27 09:43:52 surprise kernel: RSP: 002b:00007fc276220068 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Nov 27 09:43:52 surprise kernel: RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007fc2853b16d7
Nov 27 09:43:52 surprise kernel: RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000023
Nov 27 09:43:52 surprise kernel: RBP: 0000000000000000 R08: 0000564557831eb0 R09: 00000000ffffffe1
Nov 27 09:43:52 surprise kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 0000564557ba8ad0
Nov 27 09:43:52 surprise kernel: R13: 0000564556b5c040 R14: 00007fc289010000 R15: 0000000000000000