linux-kernel - Re: 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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2a65bcd8-1be1-c288-b42-e35b4c2e9fd@praktifix.dwd.de>
Date: Sat, 21 Dec 2024 13:16:25 +0000 (GMT)
From: Holger Kiehl <Holger.Kiehl@....de>
To: Zhu Yanjun <yanjun.zhu@...ux.dev>
cc: Jason Gunthorpe <jgg@...pe.ca>, Leon Romanovsky <leon@...nel.org>, 
    linux-rdma@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: failed to allocate device WQ

On Sat, 21 Dec 2024, Zhu Yanjun wrote:

> 在 2024/12/20 18:10, Holger Kiehl 写道:
> > 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":
> >     kernel: -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
> 
> It is very possible that FW is not compatible with the driver. IMO, you can
> make tests with Mellanox OFED.
> 
Thanks, I did not know there was another driver.

I just had a look, but since I build my own kernels via 'make
binrpm-pkg' and then distribute them, this seems a to big hurdle to
overcome for me.

> If the driver is compatible with FW, this problem should disappear.
> 
Actually the firmware has always been 20.39.1002 and after the
problems appeared I have upgraded to 20.41.1000, hoping it will
solve the problem.

Regards,
Holger