From: Aleksander Trofimowicz <alex@n90.eu>
To: Mark Bloch <mbloch@nvidia.com>
Cc: netdev@vger.kernel.org
Subject: Re: [bug] failed to enable eswitch SRIOV in mlx5_device_enable_sriov()
Date: Mon, 10 Jul 2023 20:10:12 +0000 [thread overview]
Message-ID: <87ilarpl4p.fsf@n90.eu> (raw)
In-Reply-To: <9c25971b-78e9-956f-95a5-38e688240ef6@nvidia.com>
Hi Mark,
Mark Bloch <mbloch@nvidia.com> writes:
> On 10/07/2023 18:25, Aleksander Trofimowicz wrote:
>>
>> I've noticed a regression in the mlx5_core driver: defining VFs via
>> /sys/bus/pci/devices/.../sriov_numvfs is no longer possible.
>>
>> Upon a write call the following error is returned:
>>
>>
>> Jul 10 11:07:44 server kernel: mlx5_core 0000:c1:00.0: mlx5_cmd_out_err:803:(pid 1097): QUERY_HCA_CAP(0x100) op_mod(0x40) failed, status bad parameter(0x3), syndrome (0x5add95), err(-22)
>> Jul 10 11:07:44 server kernel: mlx5_core 0000:c1:00.0: mlx5_device_enable_sriov:82:(pid 1097): failed to enable eswitch SRIOV (-22)
>> Jul 10 11:07:44 server kernel: mlx5_core 0000:c1:00.0: mlx5_sriov_enable:168:(pid 1097): mlx5_device_enable_sriov failed : -22
>>
>
> This should fix the issue:
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/drivers/net/ethernet/mellanox/mlx5/core/eswitch.c?id=6496357aa5f710eec96f91345b9da1b37c3231f6
>
Indeed, it should. Thanks for pointing the fix out.
--
Kind regards,
Aleksander Trofimowicz
prev parent reply other threads:[~2023-07-10 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 15:25 [bug] failed to enable eswitch SRIOV in mlx5_device_enable_sriov() Aleksander Trofimowicz
2023-07-10 15:57 ` Mark Bloch
2023-07-10 20:10 ` Aleksander Trofimowicz [this message]
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=87ilarpl4p.fsf@n90.eu \
--to=alex@n90.eu \
--cc=mbloch@nvidia.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.