Bug#1006346: cloud.debian.org: bullseye AMIs don't boot on Amazon EC2 Xen instances with Enhanced Networking
Control: reassign -1 src:linux
Control: tags -1 + upstream
> Amazon EC2 instance types with Enhanced Networking use the ixgbevf.ko
> driver. The current AMIs successfully probe the ixgbevf driver and spawn
> dhclient as expected, but dhclient appears to never receive a lease. Older
> AMIs do work on this class of instance.
Upstream commit 83dbf898a2d4 "PCI/MSI: Mask MSI-X vectors only on
success" seems to introduce a regression that breaks the "Enhanced
Networking" feature used on Amazon EC2 instances, which use PCI
passthrough access to Intel ethernet devices using the ixgbevf.ko
driver. Systems using this hardware seem to probe their network
hardware as usual, and don't log any errors to the console, but are
never able to communicate over the NIC.
Device details:
00:03.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)
Physical Slot: 3
Flags: bus master, fast devsel, latency 64
Memory at f3000000 (64-bit, prefetchable) [size=16K]
Memory at f3004000 (64-bit, prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: ixgbevf
Kernel modules: ixgbevf
The issue is present in Debian kernels in sid and experimental.
The patch has been backported to stable branches including those used in
our stable releaseѕ:
The 5.10.x (released with v5.10.88) is e5949933f313. Since bullseye is
currently using v5.10.92, it is impacted.
The 4.19.x branch (released with v4.19.222) is 12ae8cd1c7e9. Since
buster is still on v4.19.208, it is not yet impacted, but likely would
be with the next kernel update.
This issue has been reported elsewhere as well, for example Fedora
CoreOS at https://github.com/coreos/fedora-coreos-tracker/issues/1066
I have confirmed that reverting e5949933f313 from 5.10.x results in a
build that functions properly with this hardware on bullseye, but this
is probably not a reasonable thing to do generally.
noah
Reply to: