subject:"\[Kernel\-packages\] \[Bug 2045428\] Re\: AWS\: Set ENA_INTR_INITIAL_TX_INTERVAL

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2024-03-02 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-aws - 6.8.0-1001.1

---
linux-aws (6.8.0-1001.1) noble; urgency=medium

  * noble/linux-aws: 6.8.0-1001.1 -proposed tracker (LP: #2052774)

  * Packaging resync (LP: #1786013)
- debian.aws/dkms-versions -- update from kernel-versions (main/d2024.02.07)

  * AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64 (LP: #2045428)
- Revert "UBUNTU: SAUCE: net: ena: fix too long default tx interrupt
  moderation interval"

  * Miscellaneous Ubuntu changes
- [Packaging] remove custom ABI/retpoline check files
- [Config] update annotations after rebase to v6.8

  [ Ubuntu: 6.8.0-7.7 ]

  * noble/linux: 6.8.0-7.7 -proposed tracker (LP: #2052691)
  * update apparmor and LSM stacking patch set (LP: #2028253)
- SAUCE: apparmor4.0.0 [01/87]: LSM stacking v39: integrity: disassociate
  ima_filter_rule from security_audit_rule
- SAUCE: apparmor4.0.0 [02/87]: LSM stacking v39: SM: Infrastructure
  management of the sock security
- SAUCE: apparmor4.0.0 [03/87]: LSM stacking v39: LSM: Add the lsmblob data
  structure.
- SAUCE: apparmor4.0.0 [04/87]: LSM stacking v39: IMA: avoid label 
collisions
  with stacked LSMs
- SAUCE: apparmor4.0.0 [05/87]: LSM stacking v39: LSM: Use lsmblob in
  security_audit_rule_match
- SAUCE: apparmor4.0.0 [06/87]: LSM stacking v39: LSM: Add lsmblob_to_secctx
  hook
- SAUCE: apparmor4.0.0 [07/87]: LSM stacking v39: Audit: maintain an lsmblob
  in audit_context
- SAUCE: apparmor4.0.0 [08/87]: LSM stacking v39: LSM: Use lsmblob in
  security_ipc_getsecid
- SAUCE: apparmor4.0.0 [09/87]: LSM stacking v39: Audit: Update shutdown LSM
  data
- SAUCE: apparmor4.0.0 [10/87]: LSM stacking v39: LSM: Use lsmblob in
  security_current_getsecid
- SAUCE: apparmor4.0.0 [11/87]: LSM stacking v39: LSM: Use lsmblob in
  security_inode_getsecid
- SAUCE: apparmor4.0.0 [12/87]: LSM stacking v39: Audit: use an lsmblob in
  audit_names
- SAUCE: apparmor4.0.0 [13/87]: LSM stacking v39: LSM: Create new
  security_cred_getlsmblob LSM hook
- SAUCE: apparmor4.0.0 [14/87]: LSM stacking v39: Audit: Change context data
  from secid to lsmblob
- SAUCE: apparmor4.0.0 [15/87]: LSM stacking v39: Netlabel: Use lsmblob for
  audit data
- SAUCE: apparmor4.0.0 [16/87]: LSM stacking v39: LSM: Ensure the correct 
LSM
  context releaser
- SAUCE: apparmor4.0.0 [17/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_secid_to_secctx
- SAUCE: apparmor4.0.0 [18/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_lsmblob_to_secctx
- SAUCE: apparmor4.0.0 [19/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_inode_getsecctx
- SAUCE: apparmor4.0.0 [20/87]: LSM stacking v39: LSM: Use lsmcontext in
  security_dentry_init_security
- SAUCE: apparmor4.0.0 [21/87]: LSM stacking v39: LSM:
  security_lsmblob_to_secctx module selection
- SAUCE: apparmor4.0.0 [22/87]: LSM stacking v39: Audit: Create audit_stamp
  structure
- SAUCE: apparmor4.0.0 [23/87]: LSM stacking v39: Audit: Allow multiple
  records in an audit_buffer
- SAUCE: apparmor4.0.0 [24/87]: LSM stacking v39: Audit: Add record for
  multiple task security contexts
- SAUCE: apparmor4.0.0 [25/87]: LSM stacking v39: audit: multiple subject 
lsm
  values for netlabel
- SAUCE: apparmor4.0.0 [26/87]: LSM stacking v39: Audit: Add record for
  multiple object contexts
- SAUCE: apparmor4.0.0 [27/87]: LSM stacking v39: LSM: Remove unused
  lsmcontext_init()
- SAUCE: apparmor4.0.0 [28/87]: LSM stacking v39: LSM: Improve logic in
  security_getprocattr
- SAUCE: apparmor4.0.0 [29/87]: LSM stacking v39: LSM: secctx provider check
  on release
- SAUCE: apparmor4.0.0 [31/87]: LSM stacking v39: LSM: Exclusive secmark 
usage
- SAUCE: apparmor4.0.0 [32/87]: LSM stacking v39: LSM: Identify which LSM
  handles the context string
- SAUCE: apparmor4.0.0 [33/87]: LSM stacking v39: AppArmor: Remove the
  exclusive flag
- SAUCE: apparmor4.0.0 [34/87]: LSM stacking v39: LSM: Add mount opts blob
  size tracking
- SAUCE: apparmor4.0.0 [35/87]: LSM stacking v39: LSM: allocate mnt_opts 
blobs
  instead of module specific data
- SAUCE: apparmor4.0.0 [36/87]: LSM stacking v39: LSM: Infrastructure
  management of the key security blob
- SAUCE: apparmor4.0.0 [37/87]: LSM stacking v39: LSM: Infrastructure
  management of the mnt_opts security blob
- SAUCE: apparmor4.0.0 [38/87]: LSM stacking v39: LSM: Correct handling of
  ENOSYS in inode_setxattr
- SAUCE: apparmor4.0.0 [39/87]: LSM stacking v39: LSM: Remove lsmblob
  scaffolding
- SAUCE: apparmor4.0.0 [40/87]: LSM stacking v39: LSM: Allow reservation of
  netlabel
- SAUCE: apparmor4.0.0 [41/87]: LSM stacking v39: LSM: restrict
  security_cred_getsecid() to a single LSM
- SAUCE:

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2024-02-14 Thread Tim Gardner

** Tags removed: verification-needed-jammy-linux-aws-6.5
** Tags added: verification-done-jammy-linux-aws-6.5

-- 
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/2045428

Title:
  AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Released
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  An update from LP: #1853180 was carried forward to the Lunar 6.2 and
  Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.

  [Test Plan]

  AWS tested.

  [Regression potential]

  Network connections could exhibit adverse jitter times.

  [Other info]

  SF: #00372168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2024-02-13 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.04.1 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-jammy-linux-
aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.5'
to 'verification-failed-jammy-linux-aws-6.5'.


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-jammy-linux-aws-6.5-v2 
verification-needed-jammy-linux-aws-6.5

-- 
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/2045428

Title:
  AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Released
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  An update from LP: #1853180 was carried forward to the Lunar 6.2 and
  Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.

  [Test Plan]

  AWS tested.

  [Regression potential]

  Network connections could exhibit adverse jitter times.

  [Other info]

  SF: #00372168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2024-02-07 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-aws - 6.5.0-1013.13

---
linux-aws (6.5.0-1013.13) mantic; urgency=medium

  * mantic/linux-aws: 6.5.0-1013.13 -proposed tracker (LP: #2048354)

  * AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64 (LP: #2045428)
- Revert "UBUNTU: SAUCE: net: ena: fix too long default tx interrupt
  moderation interval"

  [ Ubuntu: 6.5.0-17.17 ]

  * mantic/linux: 6.5.0-17.17 -proposed tracker (LP: #2049026)
  * [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
anymore (LP: #2048919)
- [Config] Enable S390_UV_UAPI (built-in)

  [ Ubuntu: 6.5.0-16.16 ]

  * mantic/linux: 6.5.0-16.16 -proposed tracker (LP: #2048372)
  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log
- [Packaging] resync update-dkms-versions helper
- [Packaging] remove helper scripts
- [Packaging] update annotations scripts
- debian/dkms-versions -- update from kernel-versions (main/2024.01.08)
  * Add missing RPL P/U CPU IDs (LP: #2047398)
- drm/i915/rpl: Update pci ids for RPL P/U
  * Fix BCM57416 lost after resume (LP: #2047518)
- bnxt_en: Clear resource reservation during resume
  * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382)
- Revert "PCI: acpiphp: Reassign resources on bridge if necessary"
  * Update bnxt_en with bug fixes and support for Broadcom 5760X network
adapters (LP: #2045796)
- bnxt_en: use dev_consume_skb_any() in bnxt_tx_int
- eth: bnxt: move and rename reset helpers
- eth: bnxt: take the bit to set as argument of bnxt_queue_sp_work()
- eth: bnxt: handle invalid Tx completions more gracefully
- eth: bnxt: fix one of the W=1 warnings about fortified memcpy()
- eth: bnxt: fix warning for define in struct_group
- bnxt_en: Fix W=1 warning in bnxt_dcb.c from fortify memcpy()
- bnxt_en: Fix W=stringop-overflow warning in bnxt_dcb.c
- bnxt_en: Use the unified RX page pool buffers for XDP and non-XDP
- bnxt_en: Let the page pool manage the DMA mapping
- bnxt_en: Increment rx_resets counter in bnxt_disable_napi()
- bnxt_en: Save ring error counters across reset
- bnxt_en: Display the ring error counters under ethtool -S
- bnxt_en: Add tx_resets ring counter
- bnxt: use the NAPI skb allocation cache
- bnxt_en: Update firmware interface to 1.10.2.171
- bnxt_en: Enhance hwmon temperature reporting
- bnxt_en: Move hwmon functions into a dedicated file
- bnxt_en: Modify the driver to use hwmon_device_register_with_info
- bnxt_en: Expose threshold temperatures through hwmon
- bnxt_en: Use non-standard attribute to expose shutdown temperature
- bnxt_en: Event handler for Thermal event
- bnxt_en: Support QOS and TPID settings for the SRIOV VLAN
- bnxt_en: Update VNIC resource calculation for VFs
- Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN"
- eth: bnxt: fix backward compatibility with older devices
- bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI
- bnxt_en: Fix invoking hwmon_notify_event
- bnxt_en: add infrastructure to lookup ethtool link mode
- bnxt_en: support lane configuration via ethtool
- bnxt_en: refactor speed independent ethtool modes
- bnxt_en: Refactor NRZ/PAM4 link speed related logic
- bnxt_en: convert to linkmode_set_bit() API
- bnxt_en: extend media types to supported and autoneg modes
- bnxt_en: Fix 2 stray ethtool -S counters
- bnxt_en: Put the TX producer information in the TX BD opaque field
- bnxt_en: Add completion ring pointer in TX and RX ring structures
- bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info
- bnxt_en: Add completion ring pointer in TX and RX ring structures
- bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL
- bnxt_en: Refactor bnxt_tx_int()
- bnxt_en: New encoding for the TX opaque field
- bnxt_en: Refactor bnxt_hwrm_set_coal()
- bnxt_en: Support up to 8 TX rings per MSIX
- bnxt_en: Add helper to get the number of CP rings required for TX rings
- bnxt_en: Add macros related to TC and TX rings
- bnxt_en: Use existing MSIX vectors for all mqprio TX rings
- bnxt_en: Optimize xmit_more TX path
- bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx
- bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem()
- bnxt_en: Restructure context memory data structures
- bnxt_en: Add page info to struct bnxt_ctx_mem_type
- bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct
- bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function
- bnxt_en: Add support for new backing store query firmware API
- bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls
- bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct.
- bnxt_en: Modify TX ring indexing logic.
- bnxt_en: Modify RX ring indexing logic.
- bnxt_en: Modify the NAPI logic for the new P7 chips
- bnxt_en:

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2024-02-05 Thread Tim Gardner

** Tags removed: verification-needed-mantic-linux-aws
** Tags added: verification-done-mantic-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/2045428

Title:
  AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  An update from LP: #1853180 was carried forward to the Lunar 6.2 and
  Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.

  [Test Plan]

  AWS tested.

  [Regression potential]

  Network connections could exhibit adverse jitter times.

  [Other info]

  SF: #00372168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2024-01-16 Thread Ubuntu Kernel Bot

This bug is awaiting verification that the linux-aws/6.5.0-1013.13
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-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-mantic-linux-aws' to 'verification-failed-mantic-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-mantic-linux-aws-v2 
verification-needed-mantic-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/2045428

Title:
  AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  An update from LP: #1853180 was carried forward to the Lunar 6.2 and
  Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.

  [Test Plan]

  AWS tested.

  [Regression potential]

  Network connections could exhibit adverse jitter times.

  [Other info]

  SF: #00372168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2024-01-09 Thread Tim Gardner

** Changed in: linux-aws (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Changed in: linux-aws (Ubuntu Mantic)
   Status: In Progress => Fix Committed

-- 
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/2045428

Title:
  AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  Fix Committed
Status in linux-aws source package in Mantic:
  Fix Committed
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  An update from LP: #1853180 was carried forward to the Lunar 6.2 and
  Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.

  [Test Plan]

  AWS tested.

  [Regression potential]

  Network connections could exhibit adverse jitter times.

  [Other info]

  SF: #00372168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

2023-12-01 Thread Tim Gardner

https://lists.ubuntu.com/archives/kernel-team/2023-December/147391.html

** Description changed:

  SRU Justification
  
  [Impact]
  
- A stable update from LP: #1853180 was carried forward to the Lunar 6.2
- and Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
+ An update from LP: #1853180 was carried forward to the Lunar 6.2 and
+ Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.
  
  [Test Plan]
  
  AWS tested.
  
  [Regression potential]
  
  Network connections could exhibit adverse jitter times.
  
  [Other info]
  
  SF: #00372168

** Changed in: linux-aws (Ubuntu Noble)
   Status: In Progress => Fix Committed

-- 
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/2045428

Title:
  AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

Status in linux-aws package in Ubuntu:
  Fix Committed
Status in linux-aws source package in Lunar:
  In Progress
Status in linux-aws source package in Mantic:
  In Progress
Status in linux-aws source package in Noble:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  An update from LP: #1853180 was carried forward to the Lunar 6.2 and
  Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
  notice when the Jammy AWS kernel was forward ported. Commit
  05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
  interrupt moderation interval') from v5.5 set
  ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
  during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
  too long default tx interrupt moderation interval'). Reverting this
  patch will restore the AWS ENA driver to upstream default of 64.

  [Test Plan]

  AWS tested.

  [Regression potential]

  Network connections could exhibit adverse jitter times.

  [Other info]

  SF: #00372168

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

[Kernel-packages] [Bug 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64

8 matches

Site Navigation

Mail list logo

Footer information