From: Carsten Emde <C.Emde@osadl.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Asit Mallick <asit.k.mallick@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Linux 2.6.33.8
Date: Sat, 02 Apr 2011 11:14:53 +0200 [thread overview]
Message-ID: <4D96E90D.9000905@osadl.org> (raw)
In-Reply-To: <1301632555.4766.5.camel@marge.simson.net>
Mike,
> [..]
>> Bisecting from 2.6.33.7 to 2.6.33.8 revealed:
>> 74a6e0fd8fc216cfa5edcde4bd356a8972cbc74c is the first bad commit
>> commit 74a6e0fd8fc216cfa5edcde4bd356a8972cbc74c
>> Author: H. Peter Anvin<hpa@linux.intel.com>
>> Date: Fri Dec 10 23:57:04 2010 -0500
>>
>> x86, hotplug: Use mwait to offline a processor, fix the legacy case
>>
>> upstream ea53069231f9317062910d6e772cca4ce93de8c8
>> x86, hotplug: Use mwait to offline a processor, fix the legacy case
>
> The question would appear to be does mainline beyond this point exhibit
> the same symptom?
Unfortunately, I could not immediately try to reproduce the situation on
a more recent mainline kernel, since the box was freezing while enabling
the various services on any kernel >= 2.6.35.
After applying a workaround for this problem which may or may not be
related (https://lkml.org/lkml/2011/4/2/33), I was able to test more
recent kernels up to 2.6.39-rc1; they all show the same behavior.
Interestingly, the system only refuses to power down, if processor
frequency scaling was selected. The problem persisted, even if frequency
scaling was disabled by selecting userspace or performance
scaling_governor before halting the system.
CPU info:
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz
stepping : 2
This is the situation:
1. Without commit ea53069231f9317062910d6e772cca4ce93de8c8:
Everyting is fine. The system correctly powers off.
2. With commit ea53069231f9317062910d6e772cca4ce93de8c8:
a) Frequency scaling never enabled (acpi_cpufreq not loaded,
cpufreq_ondemand not loaded):
Everything is fine. The system correctly powers off.
b) Frequency scaling enabled (acpi_cpufreq loaded, cpufreq_ondemand
loaded) or
c) Frequency scaling enabled and disabled (acpi_cpufreq still loaded
since it cannot be removed easily, cpufreq_ondemand no longer
loaded) or
d) Frequency scaling enabled and disabled (acpi_cpufreq unloaded
with force, cpufreq_ondemand no longer loaded):
Not powering off, message:
ACPI: Preparing to enter system sleep state S5
Disabling non-boot CPUs ...
In a next step, I will debug arch/x86/kernel/smpboot.c to find out why
mwait_play_dead() returns when frequency scaling was not enabled and why
it does not after it was enabled.
Thanks,
-Carsten.
next prev parent reply other threads:[~2011-04-02 9:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 20:41 Linux 2.6.33.8 Greg KH
2011-03-21 20:41 ` Greg KH
2011-03-31 18:22 ` Carsten Emde
2011-04-01 4:35 ` Mike Galbraith
2011-04-02 9:14 ` Carsten Emde [this message]
2011-04-02 10:24 ` Alexander Holler
2011-04-02 11:27 ` Carsten Emde
2011-04-04 9:20 ` Alexander Holler
2011-04-02 21:08 ` Carsten Emde
2011-04-02 22:23 ` Thomas Gleixner
2011-04-02 7:33 ` Intel i7/X 980 freezes with CONFIG_INTEL_IDLE and frequency scaling Carsten Emde
2011-04-04 14:19 ` Carsten Emde
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=4D96E90D.9000905@osadl.org \
--to=c.emde@osadl.org \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@linux.intel.com \
--cc=asit.k.mallick@intel.com \
--cc=efault@gmx.de \
--cc=gregkh@suse.de \
--cc=hpa@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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