Thu, May 02, 2019 at 04:56:59AM CEST, xiyou.wangc...@gmail.com wrote:
>Although devlink health report does a nice job on reporting TX
>timeout and other NIC errors, unfortunately it requires drivers
>to support it but currently only mlx5 has implemented it.
>Before other drivers could catch up, it is useful to have a
>generic tracepoint to monitor this kind of TX timeout. We have
>been suffering TX timeout with different drivers, we plan to
>start to monitor it with rasdaemon which just needs a new tracepoint.
>
>Sample output:
>
>  ksoftirqd/1-16    [001] ..s2   144.043173: net_dev_xmit_timeout: dev=ens3 
> driver=e1000 queue=0
>
>Cc: Eran Ben Elisha <era...@mellanox.com>
>Cc: Jiri Pirko <j...@mellanox.com>
>Signed-off-by: Cong Wang <xiyou.wangc...@gmail.com>

Useful. Thanks!

Acked-by: Jiri Pirko <j...@mellanox.com>

Reply via email to