Just listing the patches/commits here directly for a better overview:
"net/mlx5: Fix failing fw tracer allocation on s390"
"net/mlx5: CT: Change idr to xarray to protect parallel tuple id allocation"
"net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns"
"net/mlx5: Kconfig: convert imply usage to weak dependency"
"net/mlx5e: Get the latest values from counters in switchdev mode"
But we would need to wait until they are accepted ...
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Description changed:
- Description will follow
+ Using the mlx5 device driver on Ubuntu 20.04 (beta), the
+ alloc_pages_nodemask code generates a stack trace when initializing a
+ device. The driver tries to allocate more contiguous memory than is
+ allowed by the platform specific FORCE_MAX_ZONEORDER setting.
+
+ FORCE_MAX_ZONEORDER on s390x: 9
+ FORCE_MAX_ZONEORDER on other platforms: 11 or more
+
+ This issue only occurs on ConnectX5 devices because the mlx5_fw_tracer
+ code is only used for physical functions.
+
+ A fix for this has recently been pulled into David Miller's net tree as part
of a series of Mellanox fixes:
+ https://lore.kernel.org/netdev/20200420213606.44292-1-sae...@mellanox.com/
+
+ It hasn't landed in Linus' tree yet though
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-z-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1874058
Title:
[UBUNTU 20.04] mlx5: alloc_pages_nodemask stack trace
Status in Ubuntu on IBM z Systems:
Incomplete
Status in linux package in Ubuntu:
New
Bug description:
Using the mlx5 device driver on Ubuntu 20.04 (beta), the
alloc_pages_nodemask code generates a stack trace when initializing a
device. The driver tries to allocate more contiguous memory than is
allowed by the platform specific FORCE_MAX_ZONEORDER setting.
FORCE_MAX_ZONEORDER on s390x: 9
FORCE_MAX_ZONEORDER on other platforms: 11 or more
This issue only occurs on ConnectX5 devices because the mlx5_fw_tracer
code is only used for physical functions.
A fix for this has recently been pulled into David Miller's net tree as part
of a series of Mellanox fixes:
https://lore.kernel.org/netdev/20200420213606.44292-1-sae...@mellanox.com/
It hasn't landed in Linus' tree yet though
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874058/+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
