Thread (4 messages) 4 messages, 2 authors, 2020-11-30

Re: NETDEV WATCHDOG: s1p1 (bnxt_en): transmit queue 2 timed out

From: Michael Chan <michael.chan@broadcom.com>
Date: 2020-11-29 07:07:21

On Wed, Nov 25, 2020 at 11:39 AM Marc Smith [off-list ref] 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.

Attachments

  • smime.p7s [application/pkcs7-signature] 4166 bytes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help