Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751840AbdLFMbE (ORCPT ); Wed, 6 Dec 2017 07:31:04 -0500 Received: from mblankhorst.nl ([141.105.120.124]:35724 "EHLO mblankhorst.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750989AbdLFMbD (ORCPT ); Wed, 6 Dec 2017 07:31:03 -0500 Subject: Re: Linux 4.15-rc2: Regression in resume from ACPI S3 To: Michal Hocko , Linus Torvalds Cc: "Rafael J. Wysocki" , Andy Lutomirski , Linux Kernel Mailing List , the arch/x86 maintainers References: <168050887.sZlTFXWCmO@aspire.rjw.lan> <20171206121452.GA6320@dhcp22.suse.cz> From: Maarten Lankhorst Message-ID: Date: Wed, 6 Dec 2017 13:31:00 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171206121452.GA6320@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2689 Lines: 60 Op 06-12-17 om 13:15 schreef Michal Hocko: > On Mon 04-12-17 14:36:20, Linus Torvalds wrote: >> On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki 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. Another reproducer for https://bugzilla.kernel.org/show_bug.cgi?id=198033 ? Symptoms are similar.. ~Maarten