[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACKFLinLofP3Ck03Vvs82_z4mhAfincF_qGFL=dKXKXOJTksdg@mail.gmail.com>
Date: Thu, 17 Aug 2023 00:08:28 -0700
From: Michael Chan <michael.chan@...adcom.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Jinpu Wang <jinpu.wang@...os.com>, netdev <netdev@...r.kernel.org>
Subject: Re: [RFC] bnxt_en TX timeout detected, starting reset task, flapping
link after
On Wed, Aug 16, 2023 at 8:01 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Wed, 16 Aug 2023 20:51:25 +0200 Jinpu Wang wrote:
> > Hi Michael, and folks on the list.
>
> It seems you meant to CC Michael.. adding him now.
> I don't recall anything like this. Could be a bad system...
I agree that it could be a bad NIC or a bad system.
>
> > kern.info: Aug 15 12:22:32 ps502b-104 kernel: [326009.251006] bnxt_en
> > 0000:45:00.0 eth0: [0]: tx{fw_ring: 0 prod: 1e7 cons: 1e4}
TX ring 0 is timing out with prod ahead of cons.
> > kern.info: Aug 15 12:22:32 ps502b-104 kernel: [326009.251015] bnxt_en
> > 0000:45:00.0 eth0: [2]: tx{fw_ring: 2 prod: af cons: 9b}
TX ring 2 is also timing out.
> > kern.info: Aug 15 12:22:32 ps502b-104 kernel: [326009.251022] bnxt_en
> > 0000:45:00.0 eth0: [4]: tx{fw_ring: 4 prod: d4 cons: d2}
Same for TX ring 4.
> > kern.info: Aug 15 12:22:32 ps502b-104 kernel: [326009.251027] bnxt_en
> > 0000:45:00.0 eth0: [6]: tx{fw_ring: 6 prod: 63 cons: 120}
TX ring 6 is ahead by a lot.
> > kern.err: Aug 15 12:23:33 ps502b-104 kernel: [326019.874938] bnxt_en
> > 0000:45:00.0 eth0: Resp cmpl intr err msg: 0x51
> > kern.err: Aug 15 12:23:33 ps502b-104 kernel: [326019.884991] bnxt_en
> > 0000:45:00.0 eth0: hwrm_ring_free type 1 failed. rc:fffffff0 err:0
This means that during reset, we're timing out when trying to free the
TX ring (type 1). There are exactly 4 of these type 1 ring free
errors, probably matching the 4 TX rings that timed out. There are
also 7 type 2 (RX ring) errors. This makes some sense because by
default there are usually 2 RX rings sharing the same MSIX with 1 TX
ring. So 7 out of 8 RX rings associated with the TX rings also failed
to be freed.
> >
> > I checked git history, but can't find any bugfix related to it. The
> > internet tells me it could be a
> > firmware bug, but I can't find firmware from Broadcom site or supermicro site.
> >
I will have someone reach out to you to help with newer firmware. Thanks.
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4209 bytes)
Powered by blists - more mailing lists