From: Carsten Emde <C.Emde@osadl.org>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Mike Galbraith <efault@gmx.de>, 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 13:27:20 +0200 [thread overview]
Message-ID: <4D970818.2020707@osadl.org> (raw)
In-Reply-To: <4D96F945.3030101@ahsoftware.de>
Alexander,
>> [..]
>> This is the situation:
>>
>> 1. Without commit ea53069231f9317062910d6e772cca4ce93de8c8:
>> Everything 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 ...
> I'm using a
> model name : Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz
This probably is not model 44; is it 26, 30 or 31?
> and can confirm some problem with power down, at least in 2.6.38.2.
> Sometimes I only see the powerdown message but the machine will stay on
> (and the fan starts getting louder).
>[..]
> Maybe it's a totally unrelated problem, but I thought it might be good
> to mention that I'm having a problem with powerdown in 2.6.38 too.
Yes, thank you,
Would you mind to completely disable processor frequency scaling and
check whether the powerdown problem goes away on your system as well? I
do not know which distro you are using, but on some systems "chkconfig
cpuspeed off; reboot" would do the job. When the system then reboots,
"halt" should correctly power off the system.
-Carsten.
next prev parent reply other threads:[~2011-04-02 11:31 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
2011-04-02 10:24 ` Alexander Holler
2011-04-02 11:27 ` Carsten Emde [this message]
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=4D970818.2020707@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=holler@ahsoftware.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