From: Matthias Hopf <mhopf@suse.de>
To: Matthieu CASTET <castet.matthieu@free.fr>,
Lin Ming <ming.m.lin@intel.com>, Oliver Neukum <oneukum@suse.de>,
rjw@sisk.pl
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Denys Vlasenko <vda.linux@googlemail.com>,
Michal Marek <mmarek@suse.cz>, Yinghai Lu <yinghai@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Borislav Petkov <bp@alien8.de>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Siarhei Liakh <sliakh.lkml@gmail.com>,
Xuxian Jiang <jiang@cs.ncsu.edu>,
Dave Airlie <airlied@redhat.com>, Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [REGRESSION] S3 resume on SandyBridge doesn't work with NX protection (5bd5a45)
Date: Wed, 19 Jan 2011 18:37:11 +0100 [thread overview]
Message-ID: <20110119173710.GA1331@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Git commit 5bd5a45 in Linus' tree "x86: Add NX protection for kernel data"
apparently breaks resume on SandyBridge machines. This is supposed to be
fixed with commit 691513f "x86: Resume trampoline must be executable",
but even git master (v2.6.38-rc1) shows the same symptoms.
After suspend to S3, the machine doesn't resume upon wakeup, but boots
normally instead. Reverting git commits 691513f, 84e1c6b, and especially
5bd5a45 (trivial except for a single hunk) makes resume work again.
lspci -vvv output is attached.
(for internal reference: machine NUE874)
Matthias
--
Matthias Hopf <mhopf@suse.de> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de
Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
[-- Attachment #2: lspci.txt.gz --]
[-- Type: application/x-gzip, Size: 3328 bytes --]
next reply other threads:[~2011-01-19 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 17:37 Matthias Hopf [this message]
2011-01-19 19:04 ` [REGRESSION] S3 resume on SandyBridge doesn't work with NX protection (5bd5a45) H. Peter Anvin
2011-01-19 22:06 ` matthieu castet
2011-01-20 13:47 ` Matthias Hopf
[not found] ` <1295535954.4d384f524c8f0@imp.free.fr>
2011-01-20 15:59 ` Matthias Hopf
[not found] ` <4D38A697.3040308@free.fr>
2011-01-20 21:25 ` H. Peter Anvin
2011-01-21 22:17 ` matthieu castet
2011-01-21 22:30 ` H. Peter Anvin
2011-01-25 14:07 ` castet.matthieu
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=20110119173710.GA1331@suse.de \
--to=mhopf@suse.de \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=castet.matthieu@free.fr \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=fweisbec@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jiang@cs.ncsu.edu \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=oneukum@suse.de \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=sliakh.lkml@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vda.linux@googlemail.com \
--cc=x86@kernel.org \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).