[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1007144: linux-image-cloud-amd64: Network doesn't come up on AWS Xen-based EC2 instances (ex c4.large)



Control: tags -1 + moreinfo

Hi,

On Sat, Mar 12, 2022 at 01:21:23AM +0000, Reilly Brogan wrote:
> Package: linux-image-cloud-amd64
> Severity: important
> 
> Dear Maintainer,
> 
> We recently noticed that instances using linux-image-5.10.0-11-amd64 and
> newer and using Xen-based EC2 instances (such as m4.large, c4.large etc)
> wouldn't join our Kubernetes clusters. We eventually figured out that
> this was a kernel-related issue as older AMIs using an older kernel were
> able to join the cluster.
> 
> When this issue occurs the AWS console log for the instance doesn't show
> any errors except that it's noticeable that the instance doesn't get an
> IP address and is therefore not able to bootstrap itself.
> 
> I bisected this issue and it was introduced in kernel 5.10.88 as commit
> e5949933f313c9e2c30ba05b977a047148b5e38c "PCI/MSI: Mask MSI-X vectors
> only on success", thus present in linux-image-5.10.0-11-amd64 which uses
> the 5.10.92 kernel (and all newer versions of the package).
> 
> I recommend reverting this commit in Bullseye and Buster (the
> aforementioned commit is also in the 4.19 tree) and working with
> upstream to get it fixed.
> 
> How to reproduce:
> 1. Start any recent AMD64 AMI (such as one from
>   https://wiki.debian.org/Cloud/AmazonEC2Image/Bullseye) on a c4.large
>   instance
> 2. Attempt to SSH to the instance (which will hang)
> 3. Observe in the AWS console logs that the instance did not receive an
> IP address)

Can you report this issue to upstream?

Regards,
Salvatore


Reply to: