On Tue, Nov 22, 2016 at 11:59 AM, Jesper Dangaard Brouer <jbro...@redhat.com> wrote: > > Hi Saeed, > > I'm seeing below dmesg errors, after pulling net-next at commit > e796f49d826aad, before I was not seeing these errors, where my tree was > based on top of commit 319b0534b95. > > mlx5_core 0000:02:00.1: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > mlx5_core 0000:02:00.1: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > mlx5_core 0000:02:00.0: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > mlx5_core 0000:02:00.0: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > mlx5_core 0000:02:00.1: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > mlx5_core 0000:02:00.1: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > mlx5_core 0000:02:00.0: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > mlx5_core 0000:02:00.0: mlx5_cmd_check:698:(pid 8788): ACCESS_REG(0x805) > op_mod(0x1) failed, status bad parameter(0x3), syndrome (0x6c4d48) > > > Listing my firmware version: > > $ ethtool -i mlx5p2 > driver: mlx5_core > version: 3.0-1 (January 2015) > firmware-version: 12.12.1240
Hi Jesper, Seems like this FW version doesn't support a new FW command introduced by "net/mlx5e: Expose PCIe statistics to ethtool" I suggest to upgrade FW, but if you don't know how to do it or in a hurry, please go ahead and revert " net/mlx5e: Expose PCIe statistics to ethtool" I will need to introduce a new capability bit as a permanent solution and a fix for the above patch. Thanks for the report, We will handle this.
