From: bugzilla-daemon@kernel.org
To: linux-rdma@vger.kernel.org
Subject: [Bug 219453] New: BCM57416 error in bnxt_re
Date: Fri, 01 Nov 2024 11:17:01 +0000 [thread overview]
Message-ID: <bug-219453-11804@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219453
Bug ID: 219453
Summary: BCM57416 error in bnxt_re
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Infiniband/RDMA
Assignee: drivers_infiniband-rdma@kernel-bugs.osdl.org
Reporter: mapengyu@gmail.com
Regression: No
Created attachment 307113
--> https://bugzilla.kernel.org/attachment.cgi?id=307113&action=edit
bnxt_re cmd error
After 6.3 kernel include bnxt_re driver for bnxt_en.
The kernel show CallTrace when bootup:
Tested on 6.12-rc5 today, there is still some error, but CallTrace is gone.
[ 5.531490] bnxt_en 0000:82:00.0: QPLIB: cmdq[0x8]=0xf status 0x3
[ 5.531497] bnxt_en 0000:82:00.0 bnxt_re0: Failed to register fence-MR
[ 5.531615] bnxt_en 0000:82:00.0 bnxt_re0: Failed to create Fence-MR
[ 5.531694] bnxt_en 0000:82:00.0: QPLIB: cmdq[0xa]=0x9 status 0x3
[ 5.531702] bnxt_en 0000:82:00.0 bnxt_re0: Failed to create HW CQ
[ 5.531706] infiniband bnxt_re0: Couldn't create ib_mad CQ
[ 5.531709] infiniband bnxt_re0: Couldn't open port 1
[ 5.531872] infiniband bnxt_re0: Device registered with IB successfully
It could be related to firmware.
Log attached.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2024-11-01 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 11:17 bugzilla-daemon [this message]
2024-11-01 11:21 ` [Bug 219453] BCM57416 error in bnxt_re bugzilla-daemon
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=bug-219453-11804@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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;
as well as URLs for NNTP newsgroup(s).