From: Raslan Darawsheh <rasland@nvidia.com>
To: Panagiotis Famelis <pfamelis@ubitech.eu>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: mlx5_common failed errno=121
Date: Thu, 18 Aug 2022 07:39:31 +0000 [thread overview]
Message-ID: <BYAPR12MB307875273C8D5A5519EEEB49CF6D9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CALcf-zbtAf_bHRD93bVrexxnjysGZQbHtFJ=YU4gtOWdUjV9CA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi Panagiotis,
Can you check if this will solve this issue?
http://patches.dpdk.org/project/dpdk/patch/20220710160244.2934-1-getelson@nvidia.com/
Kindest regards,
Raslan Darawsheh
From: Panagiotis Famelis <pfamelis@ubitech.eu>
Sent: Wednesday, August 17, 2022 10:54 AM
To: dev@dpdk.org
Subject: mlx5_common failed errno=121
Hello,
I am trying to run p4-dpdk-target (https://github.com/p4lang/p4-dpdk-target), with DPDK version 22.07.0-rc2 (the one provided by the p4-dpdk-target). However, when I run the bf_switchd I get the following error, by the dpdk driver:
"""
mlx5_common: DevX read access NIC register=0X9055 failed errno=121 status=0x3 syndrome=0x54e3a9
mlx5_common: DevX create q counter set failed errno=121 status=0x2 syndrome=0x8975f1
"""
The same error appears when running dpdk-testpmd (by the above DPDK version).
The NIC is an NVIDIA/ Mellanox Connect-X 5. I have also tested with DPDK version 21.11.0 and it doesn't show this error and works correctly.
Do you have any suggestions on what that particular error might be and how to fix it?
It seems like it tries to read a wrong register, but I am not sure.
Thank you for your help.
Best Regards,
Panagiotis Famelis.
[-- Attachment #2: Type: text/html, Size: 4584 bytes --]
next prev parent reply other threads:[~2022-08-18 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 7:53 Panagiotis Famelis
2022-08-18 7:39 ` Raslan Darawsheh [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-29 8:16 Panagiotis Famelis
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=BYAPR12MB307875273C8D5A5519EEEB49CF6D9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=pfamelis@ubitech.eu \
/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).