[Kernel-packages] [Bug 1787256] Re: 4.15 Kernel PCI DPC/AER backport fixes from upstream

[Jonathan Derrick]

Hi Joseph

There's been chatter on linux-pci ml that a lot of these fixes weren't correct.
But at the very least, I (and customers) would like to see the DPC trigger 
changed to FATAL, commit:
commit 6927868e7ae929f037eea973c582b870808880b6
Author: Oza Pawandeep 
Date:   Thu May 17 16:44:18 2018 -0500

PCI/DPC: Disable ERR_NONFATAL handling by DPC



I'd be fine dropping the rest

-- 
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/1787256

Title:
  4.15 Kernel PCI DPC/AER backport fixes from upstream

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  In Ubuntu kernel version 4.15, Downstream Port Containment (DPC) is set too 
aggressively and will trigger DPC on NON-FATALs. In newer kernels it is set to 
trigger on FATALs.
  Additionally, the DPC will consume the interrupt before passing it on to AER 
for analysis.
  Finally, udev is not notified of device offline events by AER.

  In order to support PCI DPC and AER more effectively in 4.15, please
  backport the following commits from upstream. Most of these are either
  refactors or cleanups:

  856e1eb9bdd4bd703907925be112519ff65d991f
  aa6ca5a9d7d08bc151f9de6101fe466fae4255c0
  aa745effd0acb23ad832148c9a7cee1ba8616d18
  b604472d6f94f9749e19253e8f8bc15c31fdcecf
  9f5a70f18c5893a30d6c339adc48de43c57dd7e2
  7e9084b36740b2ec263ea35efb203001f755e1d8
  d25e28e8d2451ff5ebbf5cdaf2fc280cf8c26c13
  3ecac020d6dd09259414f423b577347ebee9f533
  2e28bc84cf6eecd3759d7ae723bb0f5f09becf76
  f252d0621a1102a66aa833f09531a3baec261288
  e76d596aef0caa7296e42e29a0a81bc4155807df
  6927868e7ae929f037eea973c582b870808880b6
  0b91439d35550f585b49e8933fda68663ba03bb2
  b09803b5e546d553aebbb017ff30b8a54d81d1de
  ad4050dcda135548477c1b04909f9ebd0b9e17ba
  010caed4ccb624be619e22f9708c47f6b5c5a05c

  I've attached a backport series I've done myself

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787256/+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 1745508] Re: Please backport vmd suspend/resume patches to 16.04 hwe

[Jonathan Derrick]

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

-- 
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/1745508

Title:
  Please backport vmd suspend/resume patches to 16.04 hwe

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == SRU Justification ==

  This bug was opened to request commit e2b1820bd5d0 be backported from 4.14 to
  the 4.13 kernel in Artful.  Without this patch, servers with VMD enabled 
  run into issues suspending and resuming.

  Commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f is in mainline as of
  v4.14-rc1.


  [Fixes]
  commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
  Author: Scott Bauer 
  Date:   Fri Aug 11 14:54:32 2017 -0600
  PCI: vmd: Free up IRQs on suspend path

  [Impact]
  Without this patch, servers with VMD enabled may run into issues suspending 
and resuming

  [Test Case]
  Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.

  [Regression Potential]
  Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745508/+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 1745508] Re: Please backport vmd suspend/resume patches to 16.04 hwe

[Jonathan Derrick]

Hi Joseph

Sorry for the delay. Everything in this lp looks good with your kernel.

Thanks again!

-- 
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/1745508

Title:
  Please backport vmd suspend/resume patches to 16.04 hwe

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  Can you please backport VMD suspend/resume fixes from 4.14 to current
  4.13 HWE?

  [Fixes]
  commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
  Author: Scott Bauer 
  Date:   Fri Aug 11 14:54:32 2017 -0600
  PCI: vmd: Free up IRQs on suspend path

  [Impact] 
  Without this patch, servers with VMD enabled may run into issues suspending 
and resuming

  [Test Case]
  Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.

  [Regression Potential] 
  Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745508/+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 1745508] [NEW] Please backport vmd suspend/resume patches to 16.04 hwe

[Jonathan Derrick]

Public bug reported:

Can you please backport VMD suspend/resume fixes from 4.14 to current
4.13 HWE?

[Fixes]
commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
Author: Scott Bauer 
Date:   Fri Aug 11 14:54:32 2017 -0600
PCI: vmd: Free up IRQs on suspend path

[Impact] 
Without this patch, servers with VMD enabled may run into issues suspending and 
resuming

[Test Case]
Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.

[Regression Potential] 
Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1745508

Title:
  Please backport vmd suspend/resume patches to 16.04 hwe

Status in linux package in Ubuntu:
  New

Bug description:
  Can you please backport VMD suspend/resume fixes from 4.14 to current
  4.13 HWE?

  [Fixes]
  commit e2b1820bd5d0962d6f271b0d47c3a0e38647df2f
  Author: Scott Bauer 
  Date:   Fri Aug 11 14:54:32 2017 -0600
  PCI: vmd: Free up IRQs on suspend path

  [Impact] 
  Without this patch, servers with VMD enabled may run into issues suspending 
and resuming

  [Test Case]
  Typically this manifests by having many other devices having acquired IRQ 
resources competing with VMD. Without the patch, the server may fail to suspend 
when it can't move the IRQs to core 0 because of the lack of IRQs available on 
core 0.

  [Regression Potential] 
  Low. This only affects one component of one arch and affects the non-typical 
use-case of suspending a server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745508/+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