If it doesn't require an instance to break S2I, that suggests something in our daemon after all.
I wouldn't think we'd be doing anything low-level enough to cause this, though… -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1840484 Title: linux-oem 4.15 can not suspend to idle XPS-13-9380 Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: it somehow s2i failed, from message , it seems the s2i process be blocked by thunderbolt device. dmesg: [193139.391652] pciehp 0000:04:04.0:pcie204: pcie_do_write_cmd: no response from device [193139.391703] pciehp 0000:04:01.0:pcie204: pcie_do_write_cmd: no response from device [193141.012736] PM: noirq suspend of devices failed [193141.772467] ath10k_pci 0000:02:00.0: Unknown eventid: 118809 [193141.775359] ath10k_pci 0000:02:00.0: Unknown eventid: 90118 [193141.872317] thunderbolt 0000:05:00.0: control channel starting... Not sure is it relative that I hot plug out WD19 docking before suspend. reproduce rate: random ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1045-oem 4.15.0-1045.50 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 17 00:02:08 2019 InstallationDate: Installed on 2019-08-11 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1840484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : email@example.com Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp