Wed, Oct 09, 2019 at 06:55:45AM CEST, vasundhara-v.vo...@broadcom.com wrote:
>On Mon, Oct 7, 2019 at 3:26 PM Jiri Pirko wrote:
>>
>> Fri, Aug 30, 2019 at 05:54:57AM CEST, michael.c...@broadcom.com wrote:
>> >From: Vasundhara Volam
>> >
>> >Create new FW devlink_health_reporter, to know the curren
On Mon, Oct 7, 2019 at 3:26 PM Jiri Pirko wrote:
>
> Fri, Aug 30, 2019 at 05:54:57AM CEST, michael.c...@broadcom.com wrote:
> >From: Vasundhara Volam
> >
> >Create new FW devlink_health_reporter, to know the current health
> >status of FW.
> >
> >Command example and output:
> >$ devlink health sh
Fri, Aug 30, 2019 at 05:54:57AM CEST, michael.c...@broadcom.com wrote:
>From: Vasundhara Volam
>
>Create new FW devlink_health_reporter, to know the current health
>status of FW.
>
>Command example and output:
>$ devlink health show pci/:af:00.0 reporter fw
>
>pci/:af:00.0:
> name fw
>
From: Vasundhara Volam
Create new FW devlink_health_reporter, to know the current health
status of FW.
Command example and output:
$ devlink health show pci/:af:00.0 reporter fw
pci/:af:00.0:
name fw
state healthy error 0 recover 0
FW status: Healthy; Reset count: 1
Cc: Jiri Pi
