Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Holger Kiehl <Holger.Kiehl@dwd.de>
To: Zhu Yanjun <yanjun.zhu@linux.dev>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
	 linux-rdma@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: failed to allocate device WQ
Date: Sat, 21 Dec 2024 13:16:25 +0000 (GMT)	[thread overview]
Message-ID: <2a65bcd8-1be1-c288-b42-e35b4c2e9fd@praktifix.dwd.de> (raw)
In-Reply-To: <7f0908c3-f730-4c5d-88d7-85677810082a@linux.dev>

[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]

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

  reply	other threads:[~2024-12-21 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 17:10 failed to allocate device WQ Holger Kiehl
2024-12-21  8:37 ` Zhu Yanjun
2024-12-21 13:16   ` Holger Kiehl [this message]
2024-12-25  5:11   ` Joe Klein
2024-12-24  9:47 ` Leon Romanovsky
2024-12-24 14:28   ` Holger Kiehl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2a65bcd8-1be1-c288-b42-e35b4c2e9fd@praktifix.dwd.de \
    --to=holger.kiehl@dwd.de \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yanjun.zhu@linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox