Public bug reported:
SRU Justification:
[ Impact ]
Intel E810 NICs can report "can't open net device while reset is in
progress" (ice_open() returning -EBUSY) after resume from suspend. The
async PF reset scheduled by ice_resume() runs later in the service task;
userspace (e.g. NetworkManager) bringing the interface up in between hits
the -EBUSY path. Reproduced with irdma enabled, where the aux device probe
widens the race window.
[ Fix ]
Cherry-pick upstream commit c2816d613f388 ("ice: wait for reset completion
in ice_resume()"). It adds a best-effort 10s wait (matching
ice_devlink_info_get()) for the scheduled reset to finish before returning
from ice_resume(); reset normally completes in ~300ms.
Committed to: noble-linux-oem, resolute, resolute-linux-oem, stonking.
[ Test Plan ]
1. System with Intel E810 NIC.
2. Suspend, resume.
3. Verify no "can't open net device while reset is in progress" in dmesg
and link comes up reliably.
[ Where problems could occur ]
Suspend/resume path only; wait is best-effort with 10s timeout and an
error message on timeout rather than failing resume. Risk is low.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: In Progress
** Affects: linux-oem-6.17 (Ubuntu Noble)
Importance: Undecided
Status: In Progress
** Affects: linux (Ubuntu Resolute)
Importance: Undecided
Status: In Progress
** Affects: linux-oem-7.0 (Ubuntu Resolute)
Importance: Undecided
Status: In Progress
** Affects: linux (Ubuntu Stonking)
Importance: Undecided
Status: In Progress
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux-oem-6.17 (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Resolute)
Status: New => In Progress
** Changed in: linux-oem-7.0 (Ubuntu Resolute)
Status: New => In Progress
** Changed in: linux (Ubuntu Stonking)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2162803
Title:
ice: fix stale -EBUSY on resume of Intel E810
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162803/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
