All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10658] thermal shutdown - Dell Precision M20, Latitude D610
Date: Mon, 19 May 2008 08:34:04 -0700 (PDT)	[thread overview]
Message-ID: <20080519153404.322D7108061@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-10658-3570@http.bugzilla.kernel.org/>

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





------- Comment #38 from mjg59-kernel@srcf.ucam.org  2008-05-19 08:34 -------
Because there's no reason to believe that it's something that can be well
determined at the per-model level. I can't see any situation in which polling
could trigger bugs, other than the one described in #8842 (which this won't
hit). I appreciate the concerns about performance, though I haven't been able
to trigger any on machines here. If it's an issue, then we could simply skip
this on any hardware where reading the trip points takes a significant quantity
of time. I suspect that most of the thermal zone performance issues have
vanished now we default to burst mode in the ec driver, though.


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

  parent reply	other threads:[~2008-05-19 15:34 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 17:39 [Bug 10658] New: CPU overheats at high frequencies, ondemand governor fails to throttle sufficiently bugme-daemon
2008-05-09 17:39 ` [Bug 10658] " 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 [this message]
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=20080519153404.322D7108061@picon.linux-foundation.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 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.