-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, Oct 10, 2016 at 03:35:54PM -0600, Trammell Hudson wrote: > I'm having a problem with S3 resume on this Skylake CPU not correctly > bringing the i915 graphics back online. When it goes to sleep, Xen prints: > > (XEN) Disabling non-boot CPUs ... > (XEN) Broke affinity for irq 1 > (XEN) Broke affinity for irq 9 > (XEN) Broke affinity for irq 17 > (XEN) Broke affinity for irq 24 > (XEN) Broke affinity for irq 51 > (XEN) Broke affinity for irq 121 > (XEN) Broke affinity for irq 16 > (XEN) Broke affinity for irq 20 > (XEN) Broke affinity for irq 34 > (XEN) Entering ACPI S3 state. > > And I confirm from the EC that the platform goes into a S3 state: > > [650.711078 HC 0x8e] > [650.711713 HC 0x8a] > [650.712188 HC 0x8b] > [650.713065 event clear 0x00001000] > [650.713419 ACPI query = 13] > [650.713970 ACPI query = 0] > [650.945016 LPC RESET# asserted] > [650.945570 power state 3 = S0, in 0x003b] > [650.946019 power state 8 = S0->S3, in 0x003b] > [650.946614 chipset -> S3] > [650.946902 power state 2 = S3, in 0x003b] > > Upon coming out of sleep I see coreboot do an orderly transition into Xen, > the screen backlight comes on, but nothing is drawn on the screen. > Linux and Xen print a few messages to the console (depending on the > log level): > > (XEN) CPU0 CMCI LVT vector (0xf9) already installed > (XEN) Thermal LVT vector (0xfa) already installed > (XEN) Finishing wakeup from ACPI S3 state. > (XEN) Enabling non-boot CPUs ... > [ 694.232046] ACPI: Low-level resume complete > [ 694.232214] ACPI : EC: EC started > [ 694.232214] PM: Restoring platform NVS memory > [ 694.232470] Enabling non-boot CPUs ... > [ 694.237912] installing Xen timer for CPU 1 > [ 694.237935] cpu 1 spinlock event irq 128 > [ 694.240754] cache: parent cpu1 should notbe sleeping > [ 694.240839] CPU1 is up > [ 694.248932] installing Xen timer for CPU 2 > [ 694.248947] cpu 2 spinlock event irq 135 > [ 694.251840] cache: parent cpu2 should not be sleeping > [ 694.251908] CPU2 is up > [ 694.259935] installing Xen timer for CPU 3 > [ 694.259949] cpu 3 spinlock event irq 142 > [ 694.262819] cache: parent cpu3 should not be sleeping > [ 694.262884] CPU3 is up > [ 694.262886] ACPI: Waking up from system sleep state S3 > [ 694.284903] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI > [ 694.285011] PM: noirq resume of devices complete after 21.965 msecs > [ 694.289837] PM: early resume of devices complete after 4.773 msecs > [ 694.291471] rtc_cmos 00:02: System wakeup disabled by ACPI > [ 694.308765] tpm_tis 00:06: A TPM error (38) occurred continue selftest > [ 694.577983] usb 1-7: reset high-speed USB device number 3 using xhci_hcd > [ 695.817091] [drm] RC6 on > [ 695.852808] PM: resume of devices complete after 1562.967 msecs > [ 700.974239] Restarting tasks ... done. > [ 701.112259] audit: type=1130 audit(1476131868.711:160): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > [ 701.686614] audit: type=1131 audit(1476131869.286:161): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=systemd-suspend comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > [ 704.089237] audit: type=1131 audit(1476131871.688:162): pid=1 uid=0 > auid=4294967295 ses=4294967295 msg='unit=qubes-suspend comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > If I send an apshutdown command to the EC, the xscreensaver window > appears for a few seconds before the platform is halted. This is > a little bit of irony from Intel, I assume. > > And, as a further bit of frustration, it occasionally resumes > correctly depending on some parameters that I haven't figured out.
I assume it works fine on bare-metal Linux, right? What kernel version there? Maybe 4.4.14 is too old? - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJX/BU6AAoJENuP0xzK19cs6A4IAITlhCkQra1O0XP2Atuqcu6L xgPH0quQfWVv1ACFsedycue5R0pK+l1DqLxGojHJBT10O8yLl9i70AaVJ7Yu2q2H OgMmKT/G+tLbCV6nQkGSccYdXHF43ES/ueff8grYeSa68RRmvtYtOrtXHPjDqZDF JfEkSJ50+HVeJ+IGAsyQJwX2eE0SmAQgyY9i9uDGs8ppyJYSIZpBPPwMiqbAfecX 3iyxu9Wy9Q/NoF358e6SbVHrElm8tmoLPYmwG28pK+CDuQReI6+LWzYGIngZS0x/ omDJYMf+4p1yBQxOUtKhFhDIaNckRXJCvvDNwjLxjvfp3tjN8mkUG+bC0yt1tC4= =Zbj2 -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/20161010222459.GA15776%40mail-itl. For more options, visit https://groups.google.com/d/optout.
