[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGtf3iaH3+QQBvU2Po3DMCGd2tUeYzqhHR-SGBbH8_1u1LRAmw@mail.gmail.com>
Date: Thu, 20 Mar 2025 18:21:43 +0200
From: Kamil Zaripov <zaripov-kamil@...ide.ai>
To: Pavan Chebbi <pavan.chebbi@...adcom.com>
Cc: netdev@...r.kernel.org, Michael Chan <michael.chan@...adcom.com>,
Andrew Gospodarek <andrew.gospodarek@...adcom.com>
Subject: Re: bnxt_en: Incorrect tx timestamp report
> It's not clear to me if you are facing this issue when the PHC is
> shared between multiple hosts or if you are running a single host NIC.
I think that BCM57502 works in single host mode but I'm not sure: it
is ADLINK's Ampere Altra Developer Platform and maybe BMC can see this
NIC as well. But all actions over PHC are performed from CPU only.
> In the cases where a PHC is shared across multiple hosts, the driver
> identifies such a configuration and switches to non-real time PHC
> access mode.
Is it possible to understand in which access mode the driver works with PHC?
> https://web.git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/broadcom/bnxt?id=85036aee1938d65da4be6ae1bc7e5e7e30b567b9
> If you are using a configuration like the multi host, can you please
> make sure you have this patch?
We are using upstream Linux v6.6.39 which includes
85036aee1938d65da4be6ae1bc7e5e7e30b567b9 commit.
> Let me know if you are not in the multi-host config. Do post the
> ethtool -i output to help know the firmware version.
Here is output of this command for the first port of this NIC:
$ ethtool -i enP2s1f0np0
driver: bnxt_en
version: 6.6.39
firmware-version: 224.0.110.0/pkg 224.1.60.0
expansion-rom-version:
bus-info: 0002:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
Powered by blists - more mailing lists