Hi Andrej - Thanks for the bug report and sorry for the trouble.

The 5.3.0-22 kernel had a bunch of changes in addition to the Intel related security fixes. Lets start by ruling some things out.

I'd like for you to *separately* try two different kernel command-line parameters.

The first is "mitigations=off" which is an easy way to disable both of the Intel CPU related security fixes that landed in 5.3.0-22 in addition to all the pre-existing issues. This doesn't disable the i915 graphics driver security fixes but I don't suspect that those are the problem here.

If that doesn't work, remove "mitigations=off" and try "dis_ucode_ldr" which disables the kernel's microcode loader to rule out a faulty CPU microcode.

If that doesn't work, please try combining the two options and report back the results.

It is important to note that both options are dangerous and leave your system vulnerable to known CPU security flaws. They should only be used temporarily for testing purposes.

Also, do you perhaps use full disk encryption with LUKS/dm-crypt?

Finally, I suspect that your issue is actually TPM related but I'd like to rule out the security fixes and microcode updates first. I see the following TPM related errors in your kernel logs:

[    7.104690] tpm_tis STM7308:00: 2.0 TPM (device-id 0x0, rev-id 78)
[    7.105311] tpm tpm0: tpm_try_transmit: send(): error -5
[    7.105344] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
...
[    8.598278] Call Trace:
[    8.598898]  <IRQ>
[    8.599497]  dump_stack+0x63/0x8a
[    8.600127]  __report_bad_irq+0x3a/0xaf
[    8.600768]  note_interrupt.cold+0xb/0x61
[    8.601397]  handle_irq_event_percpu+0x73/0x80
[    8.602020]  handle_irq_event+0x3b/0x5a
[    8.602657]  handle_fasteoi_irq+0x9c/0x150
[    8.603292]  handle_irq+0x20/0x30
[    8.603946]  do_IRQ+0x50/0xe0
[    8.604591]  common_interrupt+0xf/0xf
[    8.605201]  </IRQ>
[    8.605832] RIP: 0010:cpuidle_enter_state+0xc5/0x420
[    8.606458] Code: ff e8 ef 8a 83 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 22 e1 89 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18
[    8.607134] RSP: 0018:ffffa40a4010be38 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffde
[    8.607835] RAX: ffff954b1036b340 RBX: ffffffffb555a700 RCX: 000000000000001f
[    8.608531] RDX: 0000000000000000 RSI: 000000004041a68b RDI: 0000000000000000
[    8.609225] RBP: ffffa40a4010be78 R08: 0000000200650069 R09: 000000007fffffff
[    8.609948] R10: ffff954b1036a0e4 R11: ffff954b1036a0c4 R12: ffff954b10376500
[    8.610674] R13: 0000000000000001 R14: 0000000000000001 R15: ffff954b10376500
[    8.611382]  ? cpuidle_enter_state+0xa1/0x420
[    8.612089]  cpuidle_enter+0x2e/0x40
[    8.612820]  call_cpuidle+0x23/0x40
[    8.613542]  do_idle+0x1eb/0x280
[    8.614230]  cpu_startup_entry+0x20/0x30
[    8.614940]  start_secondary+0x168/0x1c0
[    8.615653]  secondary_startup_64+0xa4/0xb0
[    8.616379] handlers:
[    8.617089] [<00000000382c6122>] tis_int_handler
[    8.617815] Disabling IRQ #31

We've seen quite a few TPM related issues with 5.3 and these two changes, which landed in 5.3.0-22, look related:

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan/commit/?id=f8595e0ab193dcb7840cd74690c6728ac6ca9dc1
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan/commit/?id=dd0bf321c5ea7ef5755e7e68d5e5b61010ad2ef9