mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: linux-pm@vger.kernel.org, "Len Brown" <len.brown@intel.com>,
	"Pavel Machek" <pavel@ucw.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>,
	x86@kernel.org, "Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: 3.10-rc1 system starts regular boot when waking from s2ram
Date: Fri, 17 May 2013 14:09:30 +0200	[thread overview]
Message-ID: <20130517120930.GD5048@dhcp22.suse.cz> (raw)
In-Reply-To: <1795910.x0krlBPTaf@vostro.rjw.lan>

On Fri 17-05-13 14:11:26, Rafael J. Wysocki wrote:
> On Friday, May 17, 2013 09:54:46 AM Michal Hocko wrote:
> > On Wed 15-05-13 11:56:08, Michal Hocko wrote:
> > > OK, I have bisected it to 78d77df7 (x86-64, init: Do not set NX bits on
> > > non-NX capable hardware). Reverting the patch on top of 3.10-rc1 fixes
> > > the issue for me and the machine resumes just fine.
> > > 
> > > Let's add involved people to the CC.
> > > 
> > > The original message with the confing and dmesg is bellow.
> > 
> > Anybody had chance to look at this? I am quite surprised that something
> > that is in init code might influence resume from suspend path. Or is it
> > just a side effect of some other changes in that area?
> > 
> > <goes and checks the latest 3.9 stable which has the backport of the patch>
> > 
> > Yes the latest stable is affected as well!
> 
> Well, I suppose there will be more response if you send a revert request to
> Linus.

Maybe the patch should be reverted in the stable tree right now - I am
not sure about all the consequences as from reading the changelog I do
not understand which bug the patch is supposed to fix.

I would like to understand why the patch breaks my setup though. Peter?

-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2013-05-17 12:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 16:01 Michal Hocko
2013-05-14 20:09 ` Rafael J. Wysocki
2013-05-15  8:01   ` Michal Hocko
2013-05-15  8:29     ` Pavel Machek
2013-05-15  9:05     ` Pavel Machek
2013-05-15  9:56 ` Michal Hocko
2013-05-17  7:54   ` Michal Hocko
2013-05-17 12:11     ` Rafael J. Wysocki
2013-05-17 12:09       ` Michal Hocko [this message]
2013-05-17 12:23         ` Rafael J. Wysocki
2013-05-17 12:30           ` Michal Hocko
2013-05-15 13:17 ` CONFIG_HYPERVISOR_GUEST=y {-- replace -- CONFIG_PARAVIRT_GUEST=y {= { # CONFIG_HYPERVISOR_GUEST is not set } Re: 3.10-rc1 system starts regular boot when waking from s2ram Fw: [PATCH 2/2] x86: Make Linux guest support optional Victor Miasnikov
2013-05-15 13:34   ` Michal Hocko
2013-05-15 13:44     ` Victor Miasnikov
2013-05-15 13:46       ` Michal Hocko
2013-05-15 14:05         ` CONFIG_HYPERVISOR_GUEST=y {-- replace -- CONFIG_PARAVIRT_GUEST=y {= { # CONFIG_HYPERVISOR_GUEST is not set } Re: 3.10-rc1 " Victor Miasnikov
2013-05-15 14:21           ` Borislav Petkov
2013-05-15 14:52             ` Victor Miasnikov
2013-05-15 17:34             ` Luck, Tony
2013-05-20 15:03 ` [PATCH] Revert "x86-64, init: Do not set NX bits on non-NX capable hardware" Michal Hocko
2013-05-20 15:58   ` H. Peter Anvin
2013-05-20 16:43     ` Michal Hocko
2013-05-20 17:21       ` Linus Torvalds
2013-05-20 18:13         ` H. Peter Anvin
2013-05-20 18:18           ` Linus Torvalds
2013-05-20 18:19             ` H. Peter Anvin
2013-05-20 18:23         ` Michal Hocko
2013-05-20 18:30           ` H. Peter Anvin
2013-05-20 18:31             ` Michal Hocko
2013-05-20 18:31             ` Linus Torvalds
2013-05-20 18:36               ` H. Peter Anvin
2013-05-20 18:42           ` [tip:x86/urgent] x86-64: Make early_pmd_flags __cpuinitdata tip-bot for H. Peter Anvin
2013-05-20 18:50           ` tip-bot for H. Peter Anvin

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=20130517120930.GD5048@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=fernando@oss.ntt.co.jp \
    --cc=hpa@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome