DPDK usage discussions
 help / color / mirror / Atom feed
From: Pankaj Gupta <pankaj.gupta@broadcom.com>
To: users@dpdk.org
Cc: Rahul Bahadur <rahul.bahadur@broadcom.com>,
	 Jochen Behrens <jochen.behrens@broadcom.com>
Subject: DPDK 21.11 Mellanox ConnectX-5 Crash
Date: Mon, 6 Jan 2025 15:13:07 -0800	[thread overview]
Message-ID: <CAJXaessRP1X7s7xpfrFbFWMKg1W6zxjRk97SkgK=xC1k=88ByQ@mail.gmail.com> (raw)

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

Hi All,

Our customer has reported the core dump on Mellanox ConnectX-5 card. After
throwing the following error message, the application crashes. Customer is
using DPDK 21.11.


Does anyone from the NVIDIA team know if a similar issue was reported in
the past and has it been fixed?


Device with port_id=2 already stopped

mlx5_common: Failed to query event queue number.

Port 2 Tx queue 0 CQ creation failure.

mlx5_net: port 2 Tx queue allocation failed: Input/output error
-- 
Thanks
Pankaj Gupta

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #2: Type: text/html, Size: 4282 bytes --]

                 reply	other threads:[~2025-01-07 10:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJXaessRP1X7s7xpfrFbFWMKg1W6zxjRk97SkgK=xC1k=88ByQ@mail.gmail.com' \
    --to=pankaj.gupta@broadcom.com \
    --cc=jochen.behrens@broadcom.com \
    --cc=rahul.bahadur@broadcom.com \
    --cc=users@dpdk.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).