It looks like reverting 1bde9ecf018ee646b68258921bf0fa364afda38a fixes
suspend issues when writing devices to /sys/power/pm_test, but also
reverting 6c6bc1aee6a61fe7a98196794735849286761a4a fixes suspend issues
when using standard suspend/resume:

commit 6c6bc1aee6a61fe7a98196794735849286761a4a
Author: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
Date:   Thu Jun 13 23:59:45 2019 +0200

    PCI: PM: Skip devices in D0 for suspend-to-idle

    BugLink: https://bugs.launchpad.net/bugs/1808957

    Patchwork: https://patchwork.kernel.org/patch/10993697/

    Commit d491f2b75237 ("PCI: PM: Avoid possible suspend-to-idle issue")
    attempted to avoid a problem with devices whose drivers want them to
    stay in D0 over suspend-to-idle and resume, but it did not go as far
    as it should with that.

    Namely, first of all, the power state of a PCI bridge with a
    downstream device in D0 must be D0 (based on the PCI PM spec r1.2,
    sec 6, table 6-1, if the bridge is not in D0, there can be no PCI
    transactions on its secondary bus), but that is not actively enforced
    during system-wide PM transitions, so use the skip_bus_pm flag
    introduced by commit d491f2b75237 for that.

    Second, the configuration of devices left in D0 (whatever the reason)
    during suspend-to-idle need not be changed and attempting to put them
    into D0 again by force is pointless, so explicitly avoid doing that.

    Fixes: d491f2b75237 ("PCI: PM: Avoid possible suspend-to-idle issue")
    Reported-by: Kai-Heng Feng <kai.heng.f...@canonical.com>
    Signed-off-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
    Reviewed-by: Mika Westerberg <mika.westerb...@linux.intel.com>
    Tested-by: Kai-Heng Feng <kai.heng.f...@canonical.com>
    (cherry picked from commit 3e26c5feed2add218046ecf91bab3cfa9bf762a6)
    Signed-off-by: Kai-Heng Feng <kai.heng.f...@canonical.com>
    Acked-by: Timo Aaltonen <tjaal...@ubuntu.com>
    Acked-by: Stefan Bader <stefan.ba...@canonical.com>
    Signed-off-by: Kleber Sacilotto de Souza <kleber.so...@canonical.com>

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

Title:
  System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  After upgrading the Ubuntu kernel to version 5.0.0-21, the System76
  Oryx Pro (oryp5) fails to resume from suspend when using discrete
  NVIDIA graphics

  The issue can be created on this hardware by following these steps:
  - Install Ubuntu 18.04.2
  - Add the proposed updates: https://wiki.ubuntu.com/Testing/EnableProposed
  - Upgrade:
    sudo apt-get updatesudo apt-get dist-upgrade
  - Install 5.0 HWE kernel:
    sudo apt-get install linux-generic-hwe-18.04-edge
  - Install NVIDIA driver:
    sudo apt-get install nvidia-driver-430
  - Reboot:
    sudo reboot
  - Attempt suspend/resume cycle

  This occurred after upgrading the kernel from version 5.0.0-20.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  system76   1721 F.... pulseaudio
   /dev/snd/controlC0:  system76   1721 F.... pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  MachineType: System76 Oryx Pro
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-hwe-edge
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic 
root=UUID=10b5d457-8884-4b50-bd82-9b38e7f36564 ro
  ProcVersionSignature: Ubuntu 5.0.0-21.22~18.04.1-generic 5.0.15
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-21-generic N/A
   linux-backports-modules-5.0.0-21-generic  N/A
   linux-firmware                            1.173.9
  Tags:  bionic
  Uname: Linux 5.0.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2019
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp5
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: oryp5
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.08:bd05/07/2019:svnSystem76:pnOryxPro:pvroryp5:rvnSystem76:rnOryxPro:rvroryp5:cvnSystem76:ct10:cvroryp5:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp5
  dmi.sys.vendor: System76

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

Reply via email to