On Tue, Dec 11, 2018 at 11:23 AM Jonathan Toppins <jtopp...@redhat.com> wrote: > > bnxt_en 0000:19:00.0 (unregistered net_device) (uninitialized): hwrm > req_type 0x190 seq id 0x6 error 0xffff > > The message above is commonly seen when a newer driver is used on > hardware with older firmware. The issue is this message means nothing to > anyone except Broadcom. Reduce the message priority to info to not > confuse users as this message is really informative in nature. > > Signed-off-by: Jonathan Toppins <jtopp...@redhat.com> > --- > drivers/net/ethernet/broadcom/bnxt/bnxt.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c > b/drivers/net/ethernet/broadcom/bnxt/bnxt.c > index 5d21c14853ac..796cb0b139dc 100644 > --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c > +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c > @@ -3880,9 +3880,9 @@ static int bnxt_hwrm_do_send_msg(struct bnxt *bp, void > *msg, u32 msg_len, > *valid = 0; > rc = le16_to_cpu(resp->error_code); > if (rc && !silent) > - netdev_err(bp->dev, "hwrm req_type 0x%x seq id 0x%x error > 0x%x\n", > - le16_to_cpu(resp->req_type), > - le16_to_cpu(resp->seq_id), rc); > + netdev_info(bp->dev, "hwrm req_type 0x%x seq id 0x%x error > 0x%x\n", > + le16_to_cpu(resp->req_type), > + le16_to_cpu(resp->seq_id), rc); > return rc; > } >
I prefer to fix it by calling _hwrm_send_message_silent() for that particular message, which is known to be rejected harmlessly by some older firmware. Please let me know if you want to send the patch or you want me to send the patch. Thanks.
