[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACKFLikcVv0VrC1CX+BWKGM9n6J+nOSkJcB97m3RpxqO0svJCA@mail.gmail.com>
Date: Sat, 28 Nov 2020 23:04:46 -0800
From: Michael Chan <michael.chan@...adcom.com>
To: Marc Smith <msmith626@...il.com>
Cc: Netdev <netdev@...r.kernel.org>
Subject: Re: NETDEV WATCHDOG: s1p1 (bnxt_en): transmit queue 2 timed out
On Wed, Nov 25, 2020 at 11:39 AM Marc Smith <msmith626@...il.com> wrote:
> [17879.279213] bnxt_en 0000:01:09.0 s1p1: TX timeout detected,
> starting reset task!
> [17883.075299] bnxt_en 0000:01:09.0 s1p1: Resp cmpl intr err msg: 0x51
> [17883.075302] bnxt_en 0000:01:09.0 s1p1: hwrm_ring_free type 1
> failed. rc:fffffff0 err:0
> [17886.957100] bnxt_en 0000:01:09.0 s1p1: Resp cmpl intr err msg: 0x51
> [17886.957103] bnxt_en 0000:01:09.0 s1p1: hwrm_ring_free type 2
> failed. rc:fffffff0 err:0
> [17890.843023] bnxt_en 0000:01:09.0 s1p1: Resp cmpl intr err msg: 0x51
> [17890.843025] bnxt_en 0000:01:09.0 s1p1: hwrm_ring_free type 2
> failed. rc:fffffff0 err:0
These messages could be caused by IRQ issues or firmware issues. It
seems that one IRQ vector that is shared by 1 TX ring (type 1) and 2
RX rings (type 2) is not getting the interrupt. It caused the
original TX timeout and the interrupt issue persisted during the
recovery to free these rings.
> firmware-version: 214.0.191.0
This firmware is about 2 years old. I'll have someone get back to you
on how to upgrade and what version to upgrade to.
Thanks.
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4166 bytes)
Powered by blists - more mailing lists