Ubuntu
linux-aws-5.13 package

  1. Bug #1978475
  2. Comment #7

Comment 7 for bug 1978475

Revision history for this message
Sebastian Neumann (basti-megamorf+ubuntu-com) wrote :

Okay, I updated to the latest kernel 5.13.0-1031-aws and the problem doesn't seem to be present anymore:

sudo apt update
apt list --upgradable
apt-transport-https/focal-updates 2.0.9 all [upgradable from: 2.0.8]
apt-utils/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
apt/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
cloud-init/focal-updates 22.2-0ubuntu1~20.04.2 all [upgradable from: 22.2-0ubuntu1~20.04.1]
intel-microcode/focal-updates 3.20220510.0ubuntu0.20.04.1 amd64 [upgradable from: 3.20210608.0ubuntu0.20.04.1]
libapt-pkg6.0/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
linux-aws/focal-updates,focal-security 5.13.0.1031.35~20.04.25 amd64 [upgradable from: 5.13.0.1029.32~20.04.24]
linux-headers-aws/focal-updates,focal-security 5.13.0.1031.35~20.04.25 amd64 [upgradable from: 5.13.0.1029.32~20.04.24]
linux-image-aws/focal-updates,focal-security 5.13.0.1031.35~20.04.25 amd64 [upgradable from: 5.13.0.1029.32~20.04.24]
linux-libc-dev/focal-updates,focal-security 5.4.0-120.136 amd64 [upgradable from: 5.4.0-117.132]

# uname -a
Linux ip-10-0-69-193 5.13.0-1031-aws #35~20.04.1-Ubuntu SMP Mon Jun 13 22:30:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

I was able to confirm this on two affected hosts.