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 for Android: free password hash cracker in your pocket

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

Message-ID: <219fb7a-5991-ada0-941c-29fd55f7df8@praktifix.dwd.de>
Date: Tue, 24 Dec 2024 14:28:37 +0000 (GMT)
From: Holger Kiehl <Holger.Kiehl@....de>
To: Leon Romanovsky <leon@...nel.org>
cc: Jason Gunthorpe <jgg@...pe.ca>, linux-rdma@...r.kernel.org, 
    linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: failed to allocate device WQ

On Tue, 24 Dec 2024, Leon Romanovsky wrote:

> On Fri, Dec 20, 2024 at 05:10:32PM +0000, Holger Kiehl wrote:
> > 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?
> 
> It is not related to the FW but to how your system loads kernel modules.
> 
> This merged PR in rdma-core probably fixes it.
> * Ensure RDMA service loads modules in initrd - https://ofcsg2dvf1.dwd.de/fmlurlsvc/?fewReq=:B:JVE3PDk0Nyt7MD8jPStkaTA9PDc9PCt+ZGpjbHl4f2gwPDk5OT5ubm5rNG47OD9raDQ1aGtrbzQ9azhvbD47Pm44OGxoaD5oOyt5MDw6Pjg9Pj47NT0rfGRpMDlPQjRgPXpvPT48Pz0+IDlPQjRgPXpuPT48Pz0+K39ufXkwRWJhamh/I0ZkaGVhTWl6aSNpaCtuMDg/K2VpYTA9&url=https%3a%2f%2fgithub.com%2flinux-rdma%2frdma-core%2fpull%2f1481 
> 
Yes, applying those I could no longer reproduce the problem. After
reboot both cards are now always detected.

Thank you very much for the hint!

Regards,
Holger