Comment 13 for bug 1981658

I've hit this (or a very similar problem) on 2 different digital ocean droplets running 20.04 LTS . Unfortunately, what I could see of the console contained only the end of the panic report, but I've transcribed it by hand below (I have screenshots if the missing numbers are wanted). The RIP was exactly the same on both 20.04.4 LTS machines I have but slightly different than the one posted by the original filer of this bug:

    RIP: 0010:tcp_create_openreq_child+0x2fd/0x410

Here's what I got from the console:

    psmouse net_failover failover virtio_blk virtio_scsi floppy
    [ 6216.896076] CR2: 0000000000000008
    [ 6216.896830] ---[ end trace 13e3ec3bb3cc9e33 ]---
    [ 6216.897743] RIP: 0010:tcp_create_openreq_child+0x2fd/0x410
    [ 6216.896830] Code: 08 00 00 8b 83 18 01 00 00 48 89 de 4c 89 ef 49 c7 84 24 80
     08 00 00 00 00 00 00 41 89 84 24 c4 05 00 00 48 8b 83 f8 00 00 00 <48> 8b 40 08
     e8 9a d0 46 00 48 85 c0 41 0f b7 84 24 68 05 00 00 74
    [ 6216.902357] RSP: 0018:ffffa6de400b88888 EFLAGS: 00010246
    [ 6216.903497] RAX: ...
    [ 6216.... ] RDX: ...
    [ 6216.... ] RBP: ...
    [ 6216.... ] R10: ...
    [ 6216.... ] R13: ...
    [ 6216.... ] FS: ...
    [ 6216.... ] FS: ...
    [ 6216.... ] CS: ...
    [ 6216.... ] CR2: ...
    [ 6216.... ] DR0: ...
    [ 6216.... ] DR3: ...
    [ 6216.919380] Kernel panic - not syncing: Fatal exception in interrupt
     ]---

    $ uname -sr
    Linux 5.4.0-122-generic

Both droplets were using linux-image-virtual, and to avoid this problem, I reverted to 5.4.0-121 via grub-set-default.