focal/linux-bluefield: 5.4.0-1035.38 -proposed tracker

Bug #1969372 reported by Luke Nowakowski-Krijger
36
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Automated-testing
Invalid
Medium
Unassigned
Boot-testing
Invalid
Medium
Unassigned
Certification-testing
Fix Released
Medium
Canonical Hardware Certification
Prepare-package
Fix Released
Medium
Zachary Tahenakos
Prepare-package-meta
Fix Released
Medium
Zachary Tahenakos
Prepare-package-signed
Fix Released
Medium
Zachary Tahenakos
Promote-signing-to-proposed
Invalid
Medium
Unassigned
Promote-to-proposed
Fix Released
Medium
Ubuntu Stable Release Updates Team
Promote-to-security
Fix Released
Medium
Andy Whitcroft
Promote-to-updates
Fix Released
Medium
Andy Whitcroft
Regression-testing
Invalid
Medium
Unassigned
Security-signoff
Fix Released
Medium
Steve Beattie
Sru-review
Fix Released
Medium
Andy Whitcroft
Stakeholder-signoff
Fix Released
Medium
Kernel SRU linux-bluefield Signoff
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux-bluefield (Ubuntu)
Focal
Fix Released
Medium
Unassigned

Bug Description

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
bugs-spammed: true
built:
  from: 4f85fe4ac0e01e96
  route-entry: 1
delta:
  promote-to-proposed:
  - signed
  - meta
  - main
  promote-to-security: []
  promote-to-updates:
  - meta
  - main
  - signed
  sru-review:
  - main
  - signed
  - meta
issue: KSRU-1899
kernel-stable-master-bug: 1968290
packages:
  main: linux-bluefield
  meta: linux-meta-bluefield
  signed: linux-signed-bluefield
phase: Complete
phase-changed: Wednesday, 11. May 2022 11:18 UTC
proposed-announcement-sent: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  main: 5.4.0-1035.38
  meta: 5.4.0.1035.36
  signed: 5.4.0-1035.38
~~:
  clamps:
    promote-to-proposed: 4f85fe4ac0e01e96
    self: 5.4.0-1035.38
    sru-review: 4f85fe4ac0e01e96

tags: added: kernel-release-tracking-bug-live
description: updated
tags: added: kernel-sru-cycle-2022.03.21-10
description: updated
description: updated
tags: added: kernel-sru-derivative-of-1968290
Changed in kernel-sru-workflow:
status: New → Confirmed
importance: Undecided → Medium
Changed in linux-bluefield (Ubuntu Focal):
importance: Undecided → Medium
Changed in kernel-sru-workflow:
status: Confirmed → Triaged
description: updated
Changed in kernel-sru-workflow:
status: Triaged → In Progress
tags: added: kernel-jira-issue-ksru-1899
description: updated
summary: - focal/linux-bluefield: <version to be filled> -proposed tracker
+ focal/linux-bluefield: 5.4.0-1035.38 -proposed tracker
description: updated
tags: added: kernel-jira-in-review
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
Andy Whitcroft (apw)
tags: added: kernel-signing-bot
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
description: updated
tags: removed: kernel-jira-in-review
description: updated
description: updated
Revision history for this message
Meriton Tuli (meriton) wrote :

Using Kernel 5.4.0-1035-bluefield, BlueField ATF version: v2.2(release):3.9.0-8-gb2194ee, BlueField UEFI version: 3.9.0-17-gbcbbade, mlxbf_gige 1.27 Verification Regression ran without any new Issues

description: updated
tags: added: verification-testing-passed
description: updated
Revision history for this message
Gavin Lin (gavin.lin) wrote :
description: updated
Revision history for this message
Luke Nowakowski-Krijger (lukenow) wrote :

I followed up on the linked bug report about the failure. Does not seem like a kernel issue but possibly an issue due to older firmware.

Revision history for this message
Gavin Lin (gavin.lin) wrote :

Unable to test enp3s0f0 and enp3s0f1 because of bug: https://bugs.launchpad.net/chelmsford/+bug/1969169
But this is not kernel issue and is expected, so marked this ct passed: https://bugs.launchpad.net/chelmsford/+bug/1969169/comments/22

description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (22.3 KiB)

This bug was fixed in the package linux-bluefield - 5.4.0-1035.38

---------------
linux-bluefield (5.4.0-1035.38) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1035.38 -proposed tracker (LP: #1969372)

  * mlxbf-gige: sync up with upstreamed version (LP: #1969233)
    - SAUCE: Revert "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
    - SAUCE: Revert "UBUNTU: SAUCE: mlxbf_gige: update driver version to 1.25"
    - SAUCE: Revert "UBUNTU: SAUCE: mlxbf_gige: clear valid_polarity upon open"
    - SAUCE: Revert "UBUNTU: SAUCE: mlxbf_gige: add interrupt counts to "ethtool
      -S""
    - SAUCE: Revert "UBUNTU: SAUCE: mlxbf-gige: add ethtool
      mlxbf_gige_set_ringparam"
    - SAUCE: Revert "UBUNTU: SAUCE: mlxbf-gige: add driver version"
    - mlxbf_gige: clear valid_polarity upon open
    - net: mellanox: mlxbf_gige: Replace non-standard interrupt handling
    - SAUCE: mlxbf-gige: add driver version
    - SAUCE: mlxbf_gige: add interrupt counts to "ethtool -S"
    - SAUCE: mlxbf-gige: add ethtool mlxbf_gige_set_ringparam
    - SAUCE: Fix OOB handling RX packets in heavy traffic

  * linux-bluefield: Fix build failure in mlxbf_gige (LP: #1969374)
    - gpiolib: acpi: Allow to find GpioInt() resource by name and index

linux-bluefield (5.4.0-1034.37) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1034.37 -proposed tracker (LP: #1968766)

  * Devlink wasn't enabled from common config (LP: #1968751)
    - [Config] Bluefield: Enable CONFIG_NET_DEVLINK
    - [Config] Bluefield: Enable dummy config options NET_VENDOR_BROADCOM and
      PAGE_POOL

linux-bluefield (5.4.0-1033.36) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1033.36 -proposed tracker (LP: #1967369)

  * Fix flow table lookup failure with no originating ifindex (LP: #1967892)
    - net/sched: act_ct: Fix flow table lookup failure with no originating ifindex

  * Fix OOB handling RX packets in heavy traffic (LP: #1964984)
    - SAUCE: Fix OOB handling RX packets in heavy traffic

  * Pass originating device to drivers offloading ct connection so devices will
    filter the tuples and offload them more efficiently (LP: #1960575)
    - net: openvswitch: Be liberal in tcp conntrack.
    - net/sched: act_ct: Fill offloading tuple iifidx
    - net: openvswitch: Fill act ct extension

  * Fix flow table lookup after ct clear or switching zones (LP: #1963948)
    - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones

  * CT: Offload only ASSURED connections (LP: #1961819)
    - net/sched: act_ct: Offload only ASSURED connections

  * Sync up gpio interrupt handling with upstreamed version (LP: #1965017)
    - Revert "UBUNTU: SAUCE: gpio-mlxbf2.c: Fix setting the gpio direction to
      output"
    - Revert "UBUNTU: SAUCE: gpio-mlxbf2.c: remove phy interrupt"
    - Revert "UBUNTU: SAUCE: gpio-mlxbf2: Cleanup and use generic gpio_irq_chip
      struct"
    - Revert "UBUNTU: SAUCE: gpio-mlxbf2.c: Support soft reset gpio interrupt"
    - Revert "UBUNTU: SAUCE: gpio-mlxbf2.c: fix spinlock bug and using
      uninitialized work"
    - Revert "UBUNTU: SAUCE: gpio: Add irq support for gpio-mlxbf2"
    - gpio: mlxbf2: remove unused inclu...

Changed in linux-bluefield (Ubuntu Focal):
status: New → Fix Released
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Workflow done!

All tasks have been completed and the bug is being set to Fix Released

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
tags: removed: kernel-release-tracking-bug-live
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.