All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	William Grant <william.grant@canonical.com>
Subject: Re: 4.16 regression: s2ram broken on non-PAE i686
Date: Wed, 28 Feb 2018 09:59:43 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1802280959180.1886@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAM6Zs0WTjWW+Lw3ws_iAH-K1dJgd5r9s0oC=u4TgEFUyC5bxig@mail.gmail.com>

Woody,

On Tue, 27 Feb 2018, Woody Suwalski wrote:

> There is a problem with s2ram on 4.16, and it has now been propagated
> to 4.15 and 4.14 stable updates.
> 
> It originates from
> 
> commit 62c00e6122a6b5aa7b1350023967a2d7a12b54c9
> Author: William Grant <william.grant@canonical.com
> <mailto:william.grant@canonical.com>>
> Date:   Tue Jan 30 22:22:55 2018 +1100
> 
>     x86/mm: Fix overlap of i386 CPU_ENTRY_AREA with FIX_BTMAP
> 
> s2ram works OK on PAE kernels, breaks badly on non-PAE. I do not think
> that the problem can be duplicated in VMPlayer, but it is 100%
> reproducible on a "real" hardware.
> System goes to sleep OK, but when woken - it reboots the PC.
> 
> The issue is tracked in Bugzilla bug 198763
> [https://bugzilla.kernel.org/show_bug.cgi?id=198763]

Thanks for digging into this so far. Can you please provide dmesg output
from a PAE=y and PAE=n kernel after boot?

Thanks,

	tglx

  reply	other threads:[~2018-02-28  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 12:54 Woody Suwalski
2018-02-28  8:59 ` Thomas Gleixner [this message]
2018-02-28 10:46   ` Woody Suwalski
2018-02-28 21:20     ` Thomas Gleixner
2018-03-01  2:45       ` Woody Suwalski
2018-03-01  7:35         ` Thomas Gleixner
2018-03-01  8:51       ` [tip:x86/pti] x86/cpu_entry_area: Sync cpu_entry_area to initial_page_table tip-bot for Thomas Gleixner
2018-03-01  9:31         ` Ingo Molnar

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=alpine.DEB.2.21.1802280959180.1886@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terraluna977@gmail.com \
    --cc=william.grant@canonical.com \
    --cc=x86@kernel.org \
    --subject='Re: 4.16 regression: s2ram broken on non-PAE i686' \
    /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

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.