Public bug reported:
Description: qdio: don't retry EQBS after CCQ 96
Symptom: Queue stalls, over-/underreporting of buffer errors.
Problem: Immediate retry of EQBS after CCQ 96 means that we
potentially misreport the state of buffers inspected
during the first EQBS call.
Solution: On CCQ 96, first process the discovered state.
Afterwards, higher-level code will eventually trigger an
EQBS/inspection of the remaining buffers. Their state is
now processed independently from the state that was
discovered during the first EQBS.
Upstream-ID: dae55b6fef58530c13df074bcc182c096609339e
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-169726 severity-high
targetmilestone-inin1804
** Tags added: architecture-s39064 bugnameltc-169726 severity-high
targetmilestone-inin1804
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781535
Title:
qdio: don't retry EQBS after CCQ 96
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781535/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
