This bug is awaiting verification that the linux-aws/6.8.0-1020.22
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-aws' to 'verification-done-noble-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-noble-linux-aws' to 'verification-failed-noble-linux-aws'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-aws-v2 
verification-needed-noble-linux-aws

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2085159

Title:
  [AWS]  Fix interrupt mappings which are set to a bad default after
  certain ENI operations

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Focal:
  Fix Committed
Status in linux-aws source package in Jammy:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Committed
Status in linux-aws source package in Oracular:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]
  Interrupt mapping is set to a bad default after certain ENI operations

  After using ethtool to update the (rx) ring buffer settings on an ENI,
  the interrupt CPU affinity for all tx-rx queues is reset to a bad
  default - CPU 0-31 - even if the ENI is on a different CPU socket
  (NUMA node). Another operation that causes the interrupt mapping to be
  reset to CPU 0-31 is moving an interface to a network namespace.

  [Fix]

  ENA driver version 2.12.3g. They mentioned that this commit in the ENA
  code looks like it addresses the bug: https://github.com/amzn/amzn-
  drivers/commit/ed7754cdf6ca0d4fb3d76906abc17718cc3ffa23

  It's included starting in driver version 2.12.0.

  I have back ported the patch from the AWS OOT driver, as well as any
  existing prerequisites needed.

  [Test Plan]

  I have tested this, as has AWS.

  [Where problems could occur]

  As this is an Ubuntu Sauce patch, if these changes make their was into
  the stable trees, or any patches touching this area of code,  they may
  cause merge conflicts, or changes in behaviour which are unexpected.

  
  [Other]
  SF# f00396266

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2085159/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to