cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10658] New: CPU overheats at high frequencies, ondemand governor fails to throttle sufficiently.
Date: Fri,  9 May 2008 10:39:06 -0700 (PDT)	[thread overview]
Message-ID: <bug-10658-3570@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=10658

           Summary: CPU overheats at high frequencies, ondemand governor
                    fails to throttle sufficiently.
           Product: Power Management
           Version: 2.5
     KernelVersion: 2.6.25.2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@www.linux.org.uk
        ReportedBy: martin-kernel-bugzilla@earth.li
                CC: mjg59-kernel@srcf.ucam.org


Latest working kernel version: Not sure if this ever worked.
Earliest failing kernel version: 2.6.23.12 definitely, probably much earlier.
Hardware Environment: Dell Precision M20, aka Latitude D610.

Problem Description:

This laptop has a very poor cooling system. If the CPU is run fast for too long
it will trip the thermal threshold at 101 deg C. I have been working around
this for some time by using the powersave governor which keeps the CPU at the
minimum 800MHz and prevents overheat. It would be nice to be able to use
ondemand reliably.

The ondemand governor is okay for normal loads. Under heavy load though, as the
temperature increases it will only reduce the CPU frequency from the maximum of
2GHz to the next lower setting of 1.6GHz, and then often allow it quickly back
to 2GHz. This is not enough to keep the temperature down so the system will
trip and shutdown.

Steps to reproduce:

Obtain one of these badly designed laptops. Set cpufreq governor to ondemand,
performance, or anything else that lets the CPU stay at 1.6GHz+. while(1);


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2008-05-09 17:39 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 17:39 bugme-daemon [this message]
2008-05-09 17:39 ` [Bug 10658] CPU overheats at high frequencies, ondemand governor fails to throttle sufficiently bugme-daemon
2008-05-09 17:40 ` bugme-daemon
2008-05-09 17:45 ` bugme-daemon
2008-05-09 21:05 ` bugme-daemon
2008-05-11 16:25 ` bugme-daemon
2008-05-11 17:09 ` bugme-daemon
2008-05-11 17:33 ` bugme-daemon
2008-05-11 18:04 ` bugme-daemon
2008-05-11 18:09 ` [Bug 10658] CPU overheats at high frequencies, ACPI " bugme-daemon
2008-05-12  1:36 ` bugme-daemon
2008-05-12  1:40 ` bugme-daemon
2008-05-12  2:27 ` bugme-daemon
2008-05-12  2:53 ` bugme-daemon
2008-05-12  4:36 ` bugme-daemon
2008-05-12  7:27 ` bugme-daemon
2008-05-12  7:37 ` bugme-daemon
2008-05-12  7:45 ` bugme-daemon
2008-05-12  7:52 ` bugme-daemon
2008-05-13  0:59 ` bugme-daemon
2008-05-13  8:25 ` bugme-daemon
2008-05-13  8:31 ` bugme-daemon
2008-05-13  9:19 ` bugme-daemon
2008-05-13  9:37 ` bugme-daemon
2008-05-13 11:19 ` bugme-daemon
2008-05-13 12:24 ` bugme-daemon
2008-05-14  0:39 ` [Bug 10658] thermal shutdown - Dell Precision M20, Latitude D610 bugme-daemon
2008-05-14  0:47 ` bugme-daemon
2008-05-14  0:49 ` bugme-daemon
2008-05-14  0:50 ` bugme-daemon
2008-05-14  0:53 ` bugme-daemon
2008-05-14  7:36 ` bugme-daemon
2008-05-14 11:40 ` bugme-daemon
2008-05-15 11:36 ` bugme-daemon
2008-05-15 11:48 ` bugme-daemon
2008-05-15 11:50 ` bugme-daemon
2008-05-15 17:42 ` bugme-daemon
2008-05-15 18:35 ` bugme-daemon
2008-05-16 18:19 ` bugme-daemon
2008-05-16 18:36 ` bugme-daemon
2008-05-19 11:33 ` bugme-daemon
2008-05-19 15:24 ` bugme-daemon
2008-05-19 15:34 ` bugme-daemon
2008-05-19 21:34 ` bugme-daemon
2008-05-19 21:39 ` bugme-daemon
2008-05-20  7:55 ` bugme-daemon
2008-05-20  9:04 ` bugme-daemon
2008-05-21  8:47 ` bugme-daemon
2008-05-21 12:26 ` bugme-daemon
2008-05-21 12:58 ` bugme-daemon
2008-05-28  7:33 ` bugme-daemon
2008-06-03 17:29 ` bugme-daemon
2008-06-03 17:55 ` bugme-daemon
2008-06-03 18:40 ` bugme-daemon
2008-06-03 19:00 ` bugme-daemon
2008-06-03 19:12 ` bugme-daemon
2008-06-03 19:12 ` bugme-daemon
2008-06-03 19:21 ` bugme-daemon
2008-06-04  1:09 ` bugme-daemon
2008-06-11 16:56 ` bugme-daemon
2008-06-12 20:14 ` bugme-daemon
2008-06-12 20:16 ` bugme-daemon
2008-06-12 20:42 ` bugme-daemon
2008-06-24 11:50 ` bugme-daemon
2008-06-24 14:21 ` bugme-daemon
2008-06-25 13:58 ` bugme-daemon

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=bug-10658-3570@http.bugzilla.kernel.org/ \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@www.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).