From: Ahmed Zaki <ahmed.zaki@intel.com>
To: <intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-net 0/2] Fixes for iavf reset path
Date: Tue, 20 Feb 2024 13:52:54 -0700 [thread overview]
Message-ID: <03a5e708-518f-4635-b42d-3d25974675d9@intel.com> (raw)
In-Reply-To: <20240123233140.309522-1-ahmed.zaki@intel.com>
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
prev parent reply other threads:[~2024-02-20 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 23:31 [Intel-wired-lan] [PATCH iwl-net 0/2] Fixes for iavf reset path Ahmed Zaki
2024-01-23 23:31 ` [Intel-wired-lan] [PATCH iwl-net 1/2] iavf: fix reset in early states Ahmed Zaki
2024-01-23 23:31 ` [Intel-wired-lan] [PATCH iwl-net 2/2] iavf: allow an early reset event to be processed Ahmed Zaki
2024-02-20 20:52 ` Ahmed Zaki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03a5e708-518f-4635-b42d-3d25974675d9@intel.com \
--to=ahmed.zaki@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox