[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170907085904.unjug5iv4rk5enye@pd.tnic>
Date: Thu, 7 Sep 2017 10:59:04 +0200
From: Borislav Petkov <bp@...e.de>
To: Andy Lutomirski <luto@...nel.org>
Cc: X86 ML <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 0/2] Fix resume failure due to PCID
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)
--
Powered by blists - more mailing lists