Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754877AbdIGI7Q (ORCPT <rfc822;w@1wt.eu>);
        Thu, 7 Sep 2017 04:59:16 -0400
Received: from mx2.suse.de ([195.135.220.15]:39816 "EHLO mx1.suse.de"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1754522AbdIGI7P (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 7 Sep 2017 04:59:15 -0400
Date: Thu, 7 Sep 2017 10:59:04 +0200
From: Borislav Petkov <bp@suse.de>
To: Andy Lutomirski <luto@kernel.org>
Cc: X86 ML <x86@kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/2] Fix resume failure due to PCID
Message-ID: <20170907085904.unjug5iv4rk5enye@pd.tnic>
References: <cover.1504752689.git.luto@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <cover.1504752689.git.luto@kernel.org>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1214
Lines: 42

On Wed, Sep 06, 2017 at 07:54:52PM -0700, Andy Lutomirski wrote:
> Patch 1 is the fix.  Patch 2 is a comment that would have kept me from
> chasing down a false lead.
> 
> I've tested patch 2 using CPU hotplug and suspend/resume.  I haven't
> tested hibernation or kexec because I don't know how.  (If I do
> systemctl hibernate on my laptop, it happily writes out a hiberation
> image somewhere and then it equally happily ignores it on the next
> boot.

Do you have this in cmdline?

        resume=         [SWSUSP]
                        Specify the partition device for software suspend
                        Format:
                        {/dev/<dev> | PARTUUID=<uuid> | <int>:<int> | <hex>}



> I don't know how to test kexec.)

You boot with something like this:

crashkernel=512M-2G:128M,2G-64G:256M,64G-:512M

Check dmesg to see whether it managed to reserve memory. Then you do:

# kexec --noefi -l bzImage --initrd=initrd.img --reuse-cmdline

# kexec -e

That last one loads it.

Anyway, something like that. I have this in my notes saying it worked at
some point.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--