From: Alexander Holler <holler@ahsoftware.de>
To: Carsten Emde <C.Emde@osadl.org>
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: Mon, 04 Apr 2011 11:20:53 +0200 [thread overview]
Message-ID: <4D998D75.1080903@ahsoftware.de> (raw)
In-Reply-To: <4D970818.2020707@osadl.org>
Hello,
Am 02.04.2011 13:27, schrieb Carsten Emde:
>> 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?
Model 30, stepping 5. HT is enabled.
>> 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.
I'm currently using F13, always with the latest stable vanilla kernel
from kernel.org. No cpufreq-daemons or similiar are involved, just the
governor "ondemand".
In regard to more detailed testing I can't say when I will find the time
to do that. I'm using this machine regulary and the problem occurs only
seldom (maybe 1 out of 5 shutdowns). So git bisect or similiar generic
tests aren't very practical.
I will try to add some print statements, I assume
native_machine_power_off() and stuff afterwards are the candidates where
to do that.
Regards,
Alexander
next prev parent reply other threads:[~2011-04-04 9:21 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
2011-04-04 9:20 ` Alexander Holler [this message]
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=4D998D75.1080903@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=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