From: Aaron Ma <aaron.ma@canonical.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Richard Cochran <richardcochran@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Dan Nowlin <dan.nowlin@intel.com>,
Brett Creeley <brett.creeley@intel.com>,
Jacob Keller <jacob.e.keller@intel.com>,
intel-wired-lan@lists.osuosl.org (moderated list:INTEL ETHERNET
DRIVERS)
Subject: [PATCH 0/5] ice: fix reset and suspend paths
Date: Mon, 19 Oct 2026 18:51:50 +0800 [thread overview]
Message-ID: <20261019105155.3793063-1-aaron.ma@canonical.com> (raw)
These fixes address failures seen while validating reset
recovery and suspend/resume on a system with two E830 PFs and
two E810 PFs, with KASAN enabled. With several PFs probing,
downloading DDP packages and rebuilding after resets at the
same time, the logs filled up with:
ice 0000:38:00.0: Control Send Queue Writeback timeout.
ice 0000:38:00.0: Failed to get VLAN mode, status -5
ice 0000:38:00.0: Pkg download failed: err -5 off 267124737 inf 96
ice 0000:38:00.0: package load failed, -12
ice 0000:38:00.0: probe with driver ice failed with error -5
ice 0000:c8:00.1: clear PF configuration failed -5
ice 0000:c8:00.0: Rebuild failed, unload and reload driver
Patch 2 has no Fixes tag on purpose; it is a prerequisite for
patch 3, so stable backports of patch 3 must include patch 2.
Aaron Ma (5):
ice: check the full PF reset polling limit
ice: retain the adapter throughout hardware initialization and
teardown
ice: scope global configuration lock to the adapter
ice: clear DVM boost table before scanning package hints
ice: quiesce PTP periodic work before system suspend
drivers/net/ethernet/intel/ice/ice_adapter.c | 2 +
drivers/net/ethernet/intel/ice/ice_adapter.h | 6 ++
drivers/net/ethernet/intel/ice/ice_common.c | 65 +++++++++++++-------
drivers/net/ethernet/intel/ice/ice_common.h | 3 +-
drivers/net/ethernet/intel/ice/ice_ddp.c | 8 +--
drivers/net/ethernet/intel/ice/ice_main.c | 37 ++++++-----
6 files changed, 80 insertions(+), 41 deletions(-)
--
2.53.0
next reply other threads:[~2026-10-19 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 10:51 Aaron Ma [this message]
2026-10-19 10:51 ` [PATCH 1/5] ice: check the full PF reset polling limit Aaron Ma
2026-10-19 11:28 ` Temerkhanov, Sergey
2026-10-19 11:30 ` Przemek Kitszel
2026-10-19 10:51 ` [PATCH 2/5] ice: retain the adapter throughout hardware initialization and teardown Aaron Ma
2026-10-19 11:29 ` Temerkhanov, Sergey
2026-10-20 9:24 ` Przemek Kitszel
2026-10-19 10:51 ` [PATCH 3/5] ice: scope global configuration lock to the adapter Aaron Ma
2026-10-19 10:51 ` [PATCH 4/5] ice: clear DVM boost table before scanning package hints Aaron Ma
2026-10-19 10:51 ` [PATCH 5/5] ice: quiesce PTP periodic work before system suspend Aaron Ma
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=20261019105155.3793063-1-aaron.ma@canonical.com \
--to=aaron.ma@canonical.com \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=brett.creeley@intel.com \
--cc=dan.nowlin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
/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