All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgenii Shatokhin <eugene.shatokhin@yandex.ru>
To: Nathan Zimmer <nzimmer@sgi.com>
Cc: Mel Gorman <mgorman@suse.de>, Pekka Enberg <penberg@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [Bisected] Suspend-to-disk fails on a 32-bit x86 system since commit 92923ca
Date: Tue, 21 Mar 2017 16:13:58 +0300	[thread overview]
Message-ID: <58D12716.4040705@yandex.ru> (raw)

Hi,

It seems, there is a regression in the kernel that prevents 
suspend-to-disk from working properly on some x86 machines with 32-bit 
Linux systems (ROSA Linux, in this case).

With the mainline kernels 4.2 - 4.10, it takes more than 2 minutes from 
"systemctl hibernate" command till the system powers off. When I try to 
resume the system after that, the system hangs with black screen after 
"Image loading progress 100%" (no ssh access, no reaction to keyboard, 
etc.).

For comparison, it takes less than 10-15 seconds from "systemctl 
hibernate" command till the poweroff when I use kernel 4.1, and the 
system resumes OK then.

Hardware info: https://linux-hardware.org/index.php?probe=e6a06c64c7
Kernel config, just in case: http://pastebin.com/P8vb9qi6

The problem does not show up in a 64-bit system installed on the same 
machine.

Bisection points at the following commit as the first "bad" one:

commit 92923ca3aacef63c92dc297a75ad0c6dfe4eab37
Author: Nathan Zimmer <nzimmer@sgi.com>
Date:   Tue Jun 30 14:56:48 2015 -0700

     mm: meminit: only set page reserved in the memblock region

I reverted it and suspend-to-disk and resume now work OK when I use the 
mainline kernels 4.2 - 4.10.

For the kernels 4.8 - 4.10, I also had to disable CONFIG_RANDOMIZE_BASE 
but that is due to an unrelated issue, which I will report separately.

Regards,
Evgenii

                 reply	other threads:[~2017-03-21 13:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58D12716.4040705@yandex.ru \
    --to=eugene.shatokhin@yandex.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=nzimmer@sgi.com \
    --cc=penberg@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.