From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next v2 1/1] bnx2x: Collect the device debug information during Tx timeout. Date: Mon, 28 May 2018 22:53:34 -0400 (EDT) Message-ID: <20180528.225334.242677960304384954.davem@davemloft.net> References: <20180524115751.5284-1-sudarsana.kalluru@cavium.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: sudarsana.kalluru@cavium.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:48852 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965500AbeE2Cxf (ORCPT ); Mon, 28 May 2018 22:53:35 -0400 In-Reply-To: <20180524115751.5284-1-sudarsana.kalluru@cavium.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Sudarsana Reddy Kalluru Date: Thu, 24 May 2018 04:57:51 -0700 > Tx-timeout mostly happens due to some issue in the device. In such cases, > debug dump would be helpful for identifying the cause of the issue. > This patch adds support to spill debug data during the Tx timeout. Here > bnx2x_panic_dump() API is used instead of bnx2x_panic(), since we still > want to allow the Tx-timeout recovery a chance to succeed. > > > Changes from previous version: > ------------------------------- > v2: Fixed a coding error. > > Please consider applying this to "net-next". > > Signed-off-by: Sudarsana Reddy Kalluru Applied, thank you.