[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <03a5e708-518f-4635-b42d-3d25974675d9@intel.com>
Date: Tue, 20 Feb 2024 13:52:54 -0700
From: Ahmed Zaki <ahmed.zaki@...el.com>
To: <intel-wired-lan@...ts.osuosl.org>, Tony Nguyen
<anthony.l.nguyen@...el.com>
CC: <netdev@...r.kernel.org>
Subject: Re: [PATCH iwl-net 0/2] Fixes for iavf reset path
On 2024-01-23 4:31 p.m., Ahmed Zaki wrote:
> A couple of fixes for iavf's reset issues that can happen in the early
> states (before configuring IRQs, queues, ..etc).
>
> Ahmed Zaki (2):
> iavf: fix reset in early states
> iavf: allow an early reset event to be processed
>
> drivers/net/ethernet/intel/iavf/iavf_main.c | 11 +++++++++++
> .../net/ethernet/intel/iavf/iavf_virtchnl.c | 18 ++++++++++++++++++
> 2 files changed, 29 insertions(+)
>
Stress testing is showing errors like:
[ 3193.412996] iavf 0000:b1:01.0: Unable to get VF config (-5)
[ 3197.115178] iavf 0000:b1:01.0: Admin queue command never completed
and
[ 3274.183144] iavf 0000:b1:01.0: Failed to init Admin Queue (-53)
more than we usually see. I will send a new version that better handles
these errors paths.
@tony, please drop from iwl next-queue for now.
Ahmed
Powered by blists - more mailing lists