On Thu 07-12-17 08:55:08, Michal Hocko wrote: > On Wed 06-12-17 13:14:52, Michal Hocko wrote: > > On Mon 04-12-17 14:36:20, Linus Torvalds wrote: > > > On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki <r...@rjwysocki.net> > > > wrote: > > > > > > > > So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the > > > > systems I have tested, so it is probably safe to assume it to be > > > > broken everywhere. > > > > > > Oh, it's definitely not broken everywhere, because I use it myself, > > > and was traveling last week due to my mom's bday. > > > > > > HOWEVER. > > > > > > Some of the x86 work seems to have broken it for some configurations. > > > In particular, do you have a big "everything enabled" kernel config - > > > particularly lockdep and irqflags tracing enabled? > > > > > > Andy has a patch, but it hasn't made it to me yet (probably because > > > the x86 people are very busy with the kaiser work): > > > > > > https://lkml.org/lkml/2017/11/30/546 > > > > > > (also note his follow-up "fix the commit message" note, but that one > > > doesn't actually affect the code itself). > > > > merging tip/x86/urgent on top of your tree fixed this problem for me, > > but I am seeing something else > > [ 131.711412] ACPI: Preparing to enter system sleep state S3 > > [ 131.755328] ACPI: EC: event blocked > > [ 131.755328] ACPI: EC: EC stopped > > [ 131.755328] PM: Saving platform NVS memory > > [ 131.755344] Disabling non-boot CPUs ... > > [ 131.779330] IRQ 124: no longer affine to CPU1 > > [ 131.780334] smpboot: CPU 1 is now offline > > [ 131.804465] smpboot: CPU 2 is now offline > > [ 131.827291] IRQ 122: no longer affine to CPU3 > > [ 131.827292] IRQ 123: no longer affine to CPU3 > > [ 131.828293] smpboot: CPU 3 is now offline > > [ 131.830991] ACPI: Low-level resume complete > > [ 131.831092] ACPI: EC: EC started > > [ 131.831093] PM: Restoring platform NVS memory > > [ 131.831864] do_IRQ: 0.55 No irq handler for vector > > [ 131.831884] Enabling non-boot CPUs ... > > [ 131.831909] x86: Booting SMP configuration: > > [ 131.831910] smpboot: Booting Node 0 Processor 1 APIC 0x2 > > [ 131.832913] cache: parent cpu1 should not be sleeping > > [ 131.833058] CPU1 is up > > [ 131.833067] smpboot: Booting Node 0 Processor 2 APIC 0x1 > > [ 131.833864] cache: parent cpu2 should not be sleeping > > [ 131.833983] CPU2 is up > > [ 131.833995] smpboot: Booting Node 0 Processor 3 APIC 0x3 > > [ 131.834776] cache: parent cpu3 should not be sleeping > > [ 131.834923] CPU3 is up > > > > "No irq handler" part looks a bit scary (maybe related to lost affinity > > messages?) but the following messages look quite as well. Is this > > something known? The system seems to be up and running without any > > visible issues. > > Hmm, there is still something bad going on during resume. My laptop > haven't woken up from s2ram this morning. The screen was powered on > but the system hasn't come up.
It's been few days and I haven't seen this problem again. And I am doing s2ram all the time... -- Michal Hocko SUSE Labs
