From: Jack Wang <jinpu.wang@ionos.com>
To: linux-rdma@vger.kernel.org
Cc: leon@kernel.org, jgg@ziepe.ca
Subject: [PATCH 0/2] bugfix for ipoib
Date: Mon, 20 Nov 2023 21:34:59 +0100 [thread overview]
Message-ID: <20231120203501.321587-1-jinpu.wang@ionos.com> (raw)
We run into queue timeout often with call trace as such:
NETDEV WATCHDOG: ib0.beef (): transmit queue 26 timed out
Call Trace:
call_timer_fn+0x27/0x100
__run_timers.part.0+0x1be/0x230
? mlx5_cq_tasklet_cb+0x6d/0x140 [mlx5_core]
run_timer_softirq+0x26/0x50
__do_softirq+0xbc/0x26d
asm_call_irq_on_stack+0xf/0x20
ib0.beef: transmit timeout: latency 10 msecs
ib0.beef: queue stopped 0, tx_head 0, tx_tail 0, global_tx_head 0, global_tx_tail 0
The last two message repeated for days.
After cross check with Mellanox OFED, I noticed some bugfix are missing in
upstream, hence I take the liberty to send them out.
Thx!
Jack Wang (2):
ipoib: Fix error code return in ipoib_mcast_join
ipoib: Add tx timeout work to recover queue stop situation
drivers/infiniband/ulp/ipoib/ipoib.h | 4 +++
drivers/infiniband/ulp/ipoib/ipoib_ib.c | 26 ++++++++++++++-
drivers/infiniband/ulp/ipoib/ipoib_main.c | 33 +++++++++++++++++--
.../infiniband/ulp/ipoib/ipoib_multicast.c | 1 +
4 files changed, 61 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-20 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 20:34 Jack Wang [this message]
2023-11-20 20:35 ` [PATCH 1/2] ipoib: Fix error code return in ipoib_mcast_join Jack Wang
2023-11-20 20:35 ` [PATCH 2/2] ipoib: Add tx timeout work to recover queue stop situation Jack Wang
2023-11-21 4:20 ` kernel test robot
2023-11-21 8:21 ` kernel test robot
2023-11-21 0:16 ` [PATCH 0/2] bugfix for ipoib Jason Gunthorpe
2023-11-21 13:02 ` Jinpu Wang
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=20231120203501.321587-1-jinpu.wang@ionos.com \
--to=jinpu.wang@ionos.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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