From: "Doug Smythies" <dsmythies@telus.net>
To: 'Viresh Kumar' <viresh.kumar@linaro.org>,
"'Rafael J. Wysocki'" <rafael@kernel.org>,
'Saravana Kannan' <skannan@codeaurora.org>
Cc: Doug Smythies <dsmythies@telus.net>, linux-pm@vger.kernel.org
Subject: System will not suspend with highest numbered CPU offline [REGRESSION][BISECTED]
Date: Thu, 3 Sep 2015 14:40:43 -0700 [thread overview]
Message-ID: <001401d0e691$302127b0$90637710$@net> (raw)
As of, or about, Kernel 4.2RC1 if I take my highest numbered
CPU offline (7 in my case), the system will not suspend.
The issue persists through Kernel 4.2.
This is on my test computer with an i7-2600K.
I do not normally use suspend on this computer,
but was doing so while working on a bug report.
The kernel was bisected, and the result was:
$ git bisect bad
87549141d516aee71d511138e27117c41e8aef68 is the first bad commit
commit 87549141d516aee71d511138e27117c41e8aef68
Author: Viresh Kumar <viresh.kumar@linaro.org>
Date: Wed Jun 10 02:13:21 2015 +0200
cpufreq: Stop migrating sysfs files on hotplug
See also several e-mails with the above subject line
between June 8th and 10th.
With any other combination of taking CPUs offline,
not including CPU 7, suspend seems to work properly.
Since I sometimes mess up using git bisect, and end
up at some random result, the conclusion was double
checked manually:
87549141d516aee71d511138e27117c41e8aef68 has the issue.
11e584cfb8a9d2226151fd39bfa74d09e575f72d (the previous commit) does not have the issue.
next reply other threads:[~2015-09-03 21:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 21:40 Doug Smythies [this message]
2015-09-04 14:59 ` System will not suspend with highest numbered CPU offline [REGRESSION][BISECTED] Rafael J. Wysocki
2015-09-04 14:42 ` Viresh Kumar
2015-09-04 18:41 ` Doug Smythies
2015-09-04 22:26 ` Rafael J. Wysocki
2015-09-04 23:05 ` Doug Smythies
2015-09-05 0:22 ` Rafael J. Wysocki
2015-09-05 1:41 ` Rafael J. Wysocki
2015-09-05 2:34 ` Doug Smythies
2015-09-05 7:46 ` Doug Smythies
2015-09-05 8:14 ` Viresh Kumar
2015-09-07 13:32 ` Rafael J. Wysocki
2015-09-08 2:40 ` Viresh Kumar
2015-09-11 20:43 ` Saravana Kannan
2015-09-11 21:30 ` Rafael J. Wysocki
2015-09-11 22:07 ` Saravana Kannan
2015-10-11 9:47 ` Viresh Kumar
2015-10-12 19:43 ` Saravana Kannan
2015-10-13 3:47 ` Viresh Kumar
2015-10-13 19:23 ` Saravana Kannan
2015-09-07 13:07 ` Rafael J. Wysocki
2015-09-07 14:03 ` Doug Smythies
2015-09-07 20:35 ` Rafael J. Wysocki
2015-09-04 15:26 ` Doug Smythies
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='001401d0e691$302127b0$90637710$@net' \
--to=dsmythies@telus.net \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=skannan@codeaurora.org \
--cc=viresh.kumar@linaro.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.