public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jason Vas Dias <jason.vas.dias@gmail.com>,
	Matthew Garrett <mjg@redhat.com>, Len Brown <len.brown@intel.com>
Cc: Andreas Herrmann <herrmann.der.user@googlemail.com>,
	Comrade DOS <suloevdmitry@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Performance drop
Date: Wed, 11 Jul 2012 15:06:43 -0700	[thread overview]
Message-ID: <20120711220643.GD10930@kroah.com> (raw)
In-Reply-To: <CALyZvKxcdNWMHEGwgdO=sGTTs9sZYerYXcQEyqFwixKzzz3giA@mail.gmail.com>

On Sat, Jul 07, 2012 at 03:40:58PM +0100, Jason Vas Dias wrote:
> I can confirm that the AMD Turion X2 2.2Ghz  HP Compaq 6715b
> "business" x86_64 k8 dual-core laptops circa 2007
> DO get stuck in 800Khz mode  and cannot switch out of it after booting
> the "stable" "v3.4.4" tagged kernel.
> 
> I followed the containing post and reverted commit
> ff74ae50f01ee67764564815c023c362c87ce18b :
> 
> Commit d51cdad33bb5bb370c05129f7c7f3a16a55eff40
> Author: root <root@jvdspc.localdomain>
> Date:   Fri Jul 6 18:57:03 2012 +0000
> 
>     Revert "ACPI: Evaluate thermal trip points before reading temperature"
> 
>     This reverts commit 9bcb8118965ab4631a65ee0726e6518f75cda6c5.
> 
> commit ff74ae50f01ee67764564815c023c362c87ce18b
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date:   Fri Jun 22 11:37:50 2012 -0700
> 
> And wow !  what a difference - back to a circa 2007 machine versus  a
> circa 1987 machine.
> 
> Not too many of us  left around trying to run the latest version of
> linux on nearly 5-year-old hardware I guess, but still -
> please can you restore correct Linux cpufreq & thermal operation on
> old-style AMD k8 CPUs ?
> They do seem to depend on the temperature being set BEFORE 1st entry .
> 
> Thanks & Regards,
> Jason Vas Dias (a Software Engineer) <jason.vas.dias@gmail.com>

Any reason you didn't include the original developers of the
9bcb8118965ab4631a65ee0 patch?

Matthew, Len, any ideas?

greg k-h

  parent reply	other threads:[~2012-07-11 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 19:12 PROBLEM: Performance drop Comrade DOS
2012-05-24 12:31 ` Andreas Herrmann
     [not found]   ` <CA+fU7qfPznJpRABC4Z=xmRZW6p5Mw3dFLBySk9HuPnaCYMMnEg@mail.gmail.com>
2012-05-26  6:11     ` Comrade DOS
     [not found]     ` <20120529140940.GA10421@alberich.amd.com>
2012-05-29 20:20       ` Comrade DOS
2012-05-30 12:43         ` Andreas Herrmann
     [not found]           ` <CA+fU7qehx6Jjb0ZWNrh+bh6SYCKLVWZDd7iLnsC=hDVqqFd74Q@mail.gmail.com>
2012-07-06  2:47             ` Fwd: " Comrade DOS
2012-07-07 14:40           ` Jason Vas Dias
2012-07-07 14:45             ` Jason Vas Dias
2012-07-11 22:06             ` Greg Kroah-Hartman [this message]
2012-07-14 11:11               ` Jason Vas Dias
2012-09-27 17:34                 ` Greg Kroah-Hartman
2012-09-27 17:48                   ` Borislav Petkov
2012-10-09 22:19                     ` katabami
2012-10-18  1:21                     ` katabami

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=20120711220643.GD10930@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=herrmann.der.user@googlemail.com \
    --cc=jason.vas.dias@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=suloevdmitry@gmail.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