From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
To: Nathan Fontenot <nfont@linux.vnet.ibm.com>, netdev@vger.kernel.org
Cc: jallen@linux.vnet.ibm.com
Subject: Re: [PATCH net-next 2/2] ibmvnic: Update firmware error reporting with cause string
Date: Mon, 6 Aug 2018 23:34:55 -0500 [thread overview]
Message-ID: <cf3e9849-d862-3fab-0788-200d2a16df7d@linux.vnet.ibm.com> (raw)
In-Reply-To: <4c6e57db-b5b7-fa9d-d3ef-9016dfe0be21@linux.vnet.ibm.com>
On 08/06/2018 10:48 PM, Nathan Fontenot wrote:
>
> On 08/06/2018 09:39 PM, Thomas Falcon wrote:
>> Print a string instead of the error code. Since there is a
>> possibility that the driver can recover, classify it as a
>> warning instead of an error.
>>
>> Signed-off-by: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
>> ---
>> drivers/net/ethernet/ibm/ibmvnic.c | 34
>> ++++++++++++++++++++++++++++++----
>> 1 file changed, 30 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/ibm/ibmvnic.c
>> b/drivers/net/ethernet/ibm/ibmvnic.c
>> index 109e4a58efad..dafdd4ade705 100644
>> --- a/drivers/net/ethernet/ibm/ibmvnic.c
>> +++ b/drivers/net/ethernet/ibm/ibmvnic.c
>> @@ -3825,15 +3825,41 @@ static void
>> handle_query_ip_offload_rsp(struct ibmvnic_adapter *adapter)
>> ibmvnic_send_crq(adapter, &crq);
>> }
>>
>> +static const char *ibmvnic_fw_err_cause(u16 cause)
>> +{
>> + switch (cause) {
>> + case ADAPTER_PROBLEM:
>> + return "adapter problem";
>> + case BUS_PROBLEM:
>> + return "bus problem";
>> + case FW_PROBLEM:
>> + return "firmware problem";
>> + case DD_PROBLEM:
>> + return "device driver problem";
>> + case EEH_RECOVERY:
>> + return "EEH recovery";
>> + case FW_UPDATED:
>> + return "firmware updated";
>> + case LOW_MEMORY:
>> + return "low Memory";
>> + default:
>> + return "unknown";
>> + }
>> +}
>> +
>> static void handle_error_indication(union ibmvnic_crq *crq,
>> struct ibmvnic_adapter *adapter)
>> {
>> struct device *dev = &adapter->vdev->dev;
>> + u16 cause;
>> +
>> + cause = be16_to_cpu(crq->error_indication.error_cause);
>>
>> - dev_err(dev, "Firmware reports %serror, cause %d\n",
>> - crq->error_indication.flags
>> - & IBMVNIC_FATAL_ERROR ? "FATAL " : "",
>> - be16_to_cpu(crq->error_indication.error_cause));
>> + dev_warn_ratelimited(dev,
>> + "Firmware reports %serror, cause: %s. Starting
>> recovery...\n",
>
> ^^^^^^^
>
> You're going to want a space between after the %s here.
>
> -Nathan
>
It does look odd at first glance, but there is a space after "FATAL" below.
Thanks,
Tom
>> + crq->error_indication.flags
>> + & IBMVNIC_FATAL_ERROR ? "FATAL " : "",
>> + ibmvnic_fw_err_cause(cause));
>>
>> if (crq->error_indication.flags & IBMVNIC_FATAL_ERROR)
>> ibmvnic_reset(adapter, VNIC_RESET_FATAL);
>>
next prev parent reply other threads:[~2018-08-07 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 2:39 [PATCH net-next 0/2] ibmvnic: Update firmware error reporting Thomas Falcon
2018-08-07 2:39 ` [PATCH net-next 1/2] ibmvnic: Remove code to request error information Thomas Falcon
2018-08-07 2:39 ` [PATCH net-next 2/2] ibmvnic: Update firmware error reporting with cause string Thomas Falcon
2018-08-07 3:48 ` Nathan Fontenot
2018-08-07 4:34 ` Thomas Falcon [this message]
2018-08-07 19:46 ` [PATCH net-next 0/2] ibmvnic: Update firmware error reporting David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf3e9849-d862-3fab-0788-200d2a16df7d@linux.vnet.ibm.com \
--to=tlfalcon@linux.vnet.ibm.com \
--cc=jallen@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nfont@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox