linux-kernel - failed to allocate device WQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <8328f0ab-fbd8-5d43-fbb3-f2954ccbd779@praktifix.dwd.de>
Date: Fri, 20 Dec 2024 17:10:32 +0000 (GMT)
From: Holger Kiehl <Holger.Kiehl@....de>
To: Jason Gunthorpe <jgg@...pe.ca>, Leon Romanovsky <leon@...nel.org>
cc: linux-rdma@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>
Subject: failed to allocate device WQ

Hello,

since upgrading from kernel 6.10 to 6.11 (also 6.12) one Infiniband
card sometimes hits this error:

   kernel: workqueue: Failed to create a rescuer kthread for wq "ipoib_wq": -EINTR
   kernel: ib0: failed to allocate device WQ
   kernel: mlx5_1: failed to initialize device: ib0 port 1 (ret = -12)
   kernel: mlx5_1: couldn't register ipoib port 1; error -12

The system has two cards:

   41:00.0 Infiniband controller: Mellanox Technologies MT28908 Family [ConnectX-6]
   c4:00.0 Infiniband controller: Mellanox Technologies MT28908 Family [ConnectX-6]

If that happens one cannot use that card for TCP/IP communication. It does
not always happen, but when it does it always happens with the second
card mlx5_1. Never with mlx5_0. This happens on four different systems.

Any idea what I can do to stop this from happening?

Regards,
Holger

PS: Firmware for both cards is 20.41.1000