public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Jason Vas Dias <jason.vas.dias@gmail.com>
Cc: linux-kernel@vger.kernel.org, davej@redhat.com,
	Arjan van de Ven <arjan@infradead.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux PM mailing list <linux-pm@vger.kernel.org>,
	Venkatesh Pallipadi <venki@google.com>,
	Len Brown <lenb@kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: after resume from suspend to disk, x86_64 CPU frequency throttling stops working - a known issue ?
Date: Mon, 12 Mar 2012 15:01:49 +0530	[thread overview]
Message-ID: <4F5DC285.9060405@linux.vnet.ibm.com> (raw)
In-Reply-To: <CALyZvKxQ1-5RY_7a4NiqDLuUf4cBaLTASAybUd67Z0AuJedsJw@mail.gmail.com>

On 03/11/2012 01:54 AM, Jason Vas Dias wrote:

> Hi - since many kernel versions ago (I believe 2.6.38+), now running
> 3.1.1 (built from 'stable' GIT tree),
> CPU frequency throttling once the maximum fans have been enabled does
> not work after I resume
> my HP 6715b x86_64 2.2GHz TL64 dual-core laptop from disk . The trip
> point temperatures are :
> $ cat /sys/class/thermal/thermal_zone0/trip_point_*temp | tr '\n' ' '
> 105000 95000 75000 65000 50000 15900
> 
> When the 95-degree thermal_zone0 trip point is exceeded, the CPU is
> meant to be throttled back from 2.2Ghz to 800Khz, until the
> temperature
> falls below the trip point when the normal frequency is restored (with
> some hystereisis delay factor) .
> 
> On boot-up from a 'pm-hibernate' suspend-to-disk on my laptop ,
> however,  the 95-degree trip point is triggered,  but no CPU frequency
> throttling occurs, and no  below-95-degree
> trip-point is triggerred, so the CPU eventually reaches the 105 degree
> trip-point and does an emergency power-off if it is heavily loaded.
> Also, the system
> in this state generates only one 95 degree trip-point event ;  after
> the temperature falls below 95-degrees for some time (over 10mins) ,
> and then I load
> the machine again, so the temperature again exceeds 95-degrees, no
> ACPI thermal event is raised .
> 
> This occurs with ANY available "governor" - I use "ondemand" by
> default, with a 'scaling_max_freq' set to 2.0Ghz (because when I run
> the CPU at 2.2Ghz , and load the machine
> (with for instance  a large package 'make -j2' build) I get hardware
> 'system hang' issues - I've tried every available means to get the
> kernel to trace / log something or boot a crash
> kernel when this occurs, with no luck, so have concluded this is a
> hardware issue - it did not occur when the laptop was new (it is now
> nearly 4 years old) - since the machine  goes
> into a state that is totally unresponsive to anything (mouse,
> keyboard, networking, video,  serial, parport, USB devices all hang),
> only a PCI bus analyzer will help solve this).
> But I've reproduced the no-throttling-
> above-95-degrees-after-suspend-from-disk problem with EVERY governor:
> performance, userspace, etc.  I have the powernow-k8 CPU
>  frequency scaling module built-in to the kernel.
> 
> I've resorted to hacking together an acpid driven thermal.sh shell
> script that, on receipt of a 95 degree event, spawns a daemon process
> that periodically monitors
> the thermal_zone0 temperature and if the temp is above 95 and the freq
> is above 800Khz, sets the frequency down a notch, and back to where it
> was
> when the temperature falls below 95 degrees.
> 
> Is this a known kernel issue ? Should I raise a bug about this ? I can
> post detailed logs showing the events occurring and CPU frequency
> throttling when booted up from cold,
> and no frequency scaling and only one 95-degree event when booted from
> suspend to disk - I wanted to check if this was a known issue first (a
> bugzilla search for
> 'no ACPI thermal event after resume from disk' returned zarro boogs).
> 
> Comments and advice would be much appreciated,
> 


Just a wild guess, but does the patch posted below help?
https://lkml.org/lkml/2012/2/28/288

(It applies on current Linux mainline.)
 
Regards,
Srivatsa S. Bhat
IBM Linux Technology Center


      reply	other threads:[~2012-03-12  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 20:24 after resume from suspend to disk, x86_64 CPU frequency throttling stops working - a known issue ? Jason Vas Dias
2012-03-12  9:31 ` Srivatsa S. Bhat [this message]

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=4F5DC285.9060405@linux.vnet.ibm.com \
    --to=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=jason.vas.dias@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=venki@google.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