[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <daaff866-b5f6-4fa8-a35b-8172d9ab9929@nvidia.com>
Date: Mon, 8 Jan 2024 15:50:09 +0200
From: Gal Pressman <gal@...dia.com>
To: Aishwarya TCV <aishwarya.tcv@....com>, Saeed Mahameed <saeed@...nel.org>,
Tariq Toukan <tariqt@...dia.com>
Cc: Saeed Mahameed <saeedm@...dia.com>, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Eric Dumazet <edumazet@...gle.com>,
Mark Brown <broonie@...nel.org>, Suzuki K Poulose <suzuki.poulose@....com>
Subject: Re: [net-next 08/15] net/mlx5e: Create single netdev per SD group
On 08/01/2024 15:36, Aishwarya TCV wrote:
>
>
> On 21/12/2023 00:57, Saeed Mahameed wrote:
>> From: Tariq Toukan <tariqt@...dia.com>
>>
>> Integrate the SD library calls into the auxiliary_driver ops in
>> preparation for creating a single netdev for the multiple devices
>> belonging to the same SD group.
>>
>> SD is still disabled at this stage. It is enabled by a downstream patch
>> when all needed parts are implemented.
>>
>> The netdev is created only when the SD group, with all its participants,
>> are ready. It is later destroyed if any of the participating devices
>> drops.
>>
>> Signed-off-by: Tariq Toukan <tariqt@...dia.com>
>> Reviewed-by: Gal Pressman <gal@...dia.com>
>> Signed-off-by: Saeed Mahameed <saeedm@...dia.com>
>> ---
>
> Hi Tariq,
>
>
> Currently when booting the kernel against next-master(next-20240108)
> with Arm64 on Marvell Thunder X2 (TX2), the kernel is failing to probe
> the network card which is resulting in boot failures for our CI (with
> rootfs over NFS). I can send the full logs if required. Most other
> boards seem fine.
>
> A bisect (full log below) identified this patch as introducing the
> failure. Bisected it on the tag "mlx5-updates-2023-12-20" at repo
> "https://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git/".
>
> This works fine on Linux 6.7-rc5
Thanks Aishwarya!
We just stumbled upon this internally as well, I assume you are using a
(very) old firmware version?
If it's the same issue we should have a fix coming soon.
Powered by blists - more mailing lists