[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
$ git tag --contains dae55b6 Ubuntu-4.17.0-6.7 Ubuntu-4.17.0-6.7 And released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
Since dae55b6 is tagged with v4.17-rc1~78^2~13 and we have 4.17 in cosmic proposed, I change 'linux (Ubuntu)' to Fix Committed. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
The requested commit is in Bionic as of Ubuntu-4.15.0-23.25~80: 25dbc82 s390/qdio: don't retry EQBS after CCQ 96 The requested commit is in Xenial as of Ubuntu-4.4.0-128.154~221: e26f413 s390/qdio: don't retry EQBS after CCQ 96 ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
** No longer affects: linux (Ubuntu Trusty) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
Per the commit message for commit dae55b6fef5, the requested patch is
also needed in Trusty and Xenial:
Fixes: 25f269f17316 ("[S390] qdio: EQBS retry after CCQ 96")
Cc: #v3.2+
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Joseph Salisbury
(jsalisbury)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1781535
Title:
qdio: don't retry EQBS after CCQ 96
Status in Ubuntu on IBM z Systems:
Triaged
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781535] Re: qdio: don't retry EQBS after CCQ 96
Is this bionic only or does this also affect other Ubuntu releases? ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781535 Title: qdio: don't retry EQBS after CCQ 96 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
