lkml.org 
[lkml]   [2015]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Subject[3.2-stable] Suspend regression after "x86, mm: Set NX across entire PMD at boot"
From
Date
Commit 45e2a9d4701d8c624d4a4bcdd1084eae31e92f58 ("x86, mm: Set NX across
entire PMD at boot") has been backported to many stable branches:

v3.10.62: 0b15c16c4f4a x86, mm: Set NX across entire PMD at boot
v3.12.35: 868b19cb0314 x86, mm: Set NX across entire PMD at boot
v3.14.26: 1a829c59816e x86, mm: Set NX across entire PMD at boot
v3.17.5: 6231385167e0 x86, mm: Set NX across entire PMD at boot
v3.2.65: a5c187d92d2c x86, mm: Set NX across entire PMD at boot
v3.13.11-ckt12: 3657489f7009 x86, mm: Set NX across entire PMD at boot
v3.16.7-ckt3: de32229b546e x86, mm: Set NX across entire PMD at boot

Unfortunately, in 3.2.65 suspend/resume stopped working on at least some
systems - specifically, the system would reboot when woken:

https://bugs.debian.org/774436 - Lenovo ThinkPad T530
https://bugs.debian.org/774461 - Lenovo ThinkPad X230
https://bugs.debian.org/774526 - ECS P4M900T-M2
https://bugs.debian.org/775059 - ASUS X201EP

I could reproduce this on my own ASUS P8Z68-V LX and was able to bisect
to the backport of this commit.

Assuming that this regression has not occurred on mainline or the other
branches, I will revert this patch for 3.2.y unless someone can point
out a missing dependency that I should apply.

Ben.

--
Ben Hutchings
One of the nice things about standards is that there are so many of them.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2015-01-11 01:41    [W:0.052 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site