All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dimitrios Apostolou <jimis@gmx.net>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Alex Chiang <achiang@hp.com>, Len Brown <lenb@kernel.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Yinghai Lu <yinghai@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd)
Date: Tue, 12 Jan 2010 16:07:34 -0800	[thread overview]
Message-ID: <20100112160734.89ee6b11.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1001100251210.1334@localhost.localdomain>

On Sun, 10 Jan 2010 03:05:38 +0200 (EET)
Dimitrios Apostolou <jimis@gmx.net> wrote:

> On Sat, 9 Jan 2010, Arjan van de Ven wrote:
> 
> > On Sun, 10 Jan 2010 02:32:11 +0200 (EET)
> > Dimitrios Apostolou <jimis@gmx.net> wrote:
> >
> >> On Sat, 9 Jan 2010, Arjan van de Ven wrote:
> >>
> >>> On Sun, 10 Jan 2010 01:55:42 +0200 (EET)
> >>> Dimitrios Apostolou <jimis@gmx.net> wrote:
> >>>
> >>>> L8400B series Notebook PC
> >>>
> >>> can you try this patch?
> >>>
> >>
> >> OK I'm compiling a new kernel right now but that will take a while, I
> >> only have access to old hardware at the moment... What exactly this
> >> patch does?
> >>
> >
> > basically it appears that your machine, when the kernel asks for C2,
> > exits C2 immediately again.
> >
> > The old algorithm somehow caught this and stopped asking for C2 most of
> > the time; the new algorithm doesn't see any activity and asks for C2
> > again.
> >
> > What the patch does is tell the kernel to just not use C2 at all...
> 
> Indeed, in the past powertop always showed my processor idling in C1 
> state, and I wondered why it never entered C2. :-)
> 
> So thanks for the patch, I guess it works, and my bet is that this 
> case applies to L8400* (not only B models), except if it is fixed by some 
> old BIOS upgrade that I must have missed.
> 
> While testing your patch, indeed the temperature was not rising and 
> everything was normal, but the tsc was not marked as unstable so it didn't 
> switch to acpi_pm clocksource, so that was probably the reason.
> 

Arjan, can you please prepare a formal version of the fix?  I guess the
cc:stable will be needed as well.

I assume that the effects which Dimitrios described above were the
intended ones?


  parent reply	other threads:[~2010-01-13  0:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LNX.2.00.1001071941470.1363@localhost.localdomain>
2010-01-08 17:15 ` High cpu temperature with 2.6.32, bisection shows commit 69d258 (fwd) Alex Chiang
2010-01-09 21:43   ` Arjan van de Ven
2010-01-09 23:55     ` Dimitrios Apostolou
2010-01-10  0:08       ` Arjan van de Ven
2010-01-10  0:32         ` Dimitrios Apostolou
2010-01-10  0:42           ` Arjan van de Ven
2010-01-10  1:05             ` Dimitrios Apostolou
2010-01-10  1:38               ` Arjan van de Ven
2010-01-13  0:07               ` Andrew Morton [this message]
2010-01-13  5:32                 ` Arjan van de Ven
2010-02-10 20:51                   ` Dimitrios Apostolou
2010-02-10 21:42                     ` Dimitrios Apostolou
2010-02-11  4:56                     ` Arjan van de Ven
2010-02-11 18:00                       ` Dimitrios Apostolou
2010-02-11 21:58                         ` Wojciech Ploskonka
2010-02-12  5:24                           ` Arjan van de Ven
2010-02-12 21:05                             ` Matthew Garrett
2010-02-18 20:27                             ` Dimitrios Apostolou
2010-02-18 20:34                               ` Rafael J. Wysocki
2010-02-22 16:43                             ` Dimitrios Apostolou
2010-02-23  1:55                               ` Arjan van de Ven
2010-02-12  5:23                         ` Arjan van de Ven
2010-01-10  2:07             ` Ray Lee
2010-01-10  3:09               ` Robert Hancock
2010-01-10  4:15               ` Arjan van de Ven
2010-01-15 20:00           ` -O0 kernel " Pavel Machek
2010-01-15 20:40             ` Dimitrios Apostolou

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=20100112160734.89ee6b11.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=achiang@hp.com \
    --cc=arjan@infradead.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=jimis@gmx.net \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yinghai@kernel.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.