From: Kyle Moffett <mrmacman_g4@mac.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Schwartz <davids@webmaster.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: PC speaker
Date: Thu, 14 Jun 2007 20:36:49 -0400 [thread overview]
Message-ID: <5B4A5F89-935F-48DA-941D-54F7B0FC2FAA@mac.com> (raw)
In-Reply-To: <20070613195329.GC8273@ucw.cz>
On Jun 13, 2007, at 15:53:30, Pavel Machek wrote:
>> Other great examples are hardware that allows you to control
>> voltages, fan speeds, and operating frequencies. Sometimes you can
>> overvoltage it directly and blow it immediately. Other times, you
>> can increase the voltage and operating frequency and decrease the
>> fan speed to the point where it stops spinning. This is possible
>> on many modern graphics cards and CPUs.
>
> Not true for cpus; try it before spreading FUD. Thermal protection
> will kill the machine when cpu goes over 95C or so.
Well, sorta. Things tend to die early heat deaths if you repeatedly
spike the temperature (different rates of thermal expansion and all
that jazz). If you alternated repeatedly between max-CPU/no-fan and
no-CPU/max-fan, staying just within the thermal kill limits and
spending 3/4 of the time at near max temp, you'd probably have a 30%
chance to kill an average CPU within a couple weeks.
I know when designing the G5 CPU, IBM had to be _really_ careful
about the variably high operating temperature. Their first few
designs ended up having BGA breakdown well before the desired
lifetime due to thermal creep (long-duration at high temp) and
fatigue shear failure (alternation between high and low temp).
There's a paper somewhere on the web about the whole deal.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2007-06-15 0:37 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 12:45 R.F. Burns
2007-06-12 13:31 ` Jan Engelhardt
2007-06-12 13:54 ` R.F. Burns
2007-06-12 13:57 ` Jan Engelhardt
2007-06-12 15:09 ` Jan Engelhardt
2007-06-12 15:19 ` Alan Cox
2007-06-12 17:26 ` Jan Engelhardt
2007-06-12 20:08 ` David Schwartz
2007-06-12 20:34 ` Jan Engelhardt
2007-06-13 9:22 ` Helge Hafting
2007-06-13 10:27 ` Maciej W. Rozycki
2007-06-13 10:41 ` Paulo Marques
2007-06-13 19:53 ` Pavel Machek
2007-06-15 0:36 ` Kyle Moffett [this message]
2007-06-12 14:44 ` Lee Revell
2007-06-12 17:39 ` jimmy bahuleyan
2007-06-12 20:25 ` R.F. Burns
2007-06-12 20:36 ` Jan Engelhardt
2007-06-12 21:15 ` Clemens Koller
2007-06-12 22:08 ` David Schwartz
2007-06-13 12:26 ` Chris Smith
2007-06-15 17:07 ` Phillip Susi
2007-06-15 19:34 ` Jan Engelhardt
2007-06-15 23:30 ` Phillip Susi
2007-06-16 3:20 ` Kyle Moffett
2008-07-08 17:08 R.F. Burns
2008-07-08 17:38 ` Jan Engelhardt
2009-06-12 21:28 R.F. Burns
2009-06-12 21:40 ` Valdis.Kletnieks
2009-06-13 0:10 ` John Sheu
2010-06-12 21:32 R.F. Burns
2010-06-12 21:50 ` Daniel Hazelton
2010-06-13 0:07 ` Alan Cox
2016-08-05 16:51 R.F. Burns
2017-06-12 19:13 R.F. Burns
2017-06-12 21:25 ` Randy Dunlap
2017-06-12 22:52 ` Dmitry Torokhov
2018-06-12 20:31 R.F. Burns
2019-06-13 16:16 R.F. Burns
2019-06-13 19:57 ` Theodore Ts'o
2019-06-13 20:07 ` Randy Dunlap
2020-06-18 17:49 R.F. Burns
2020-06-19 3:04 ` Randy Dunlap
2020-06-23 8:03 ` Oleksandr Natalenko
2021-06-15 3:32 R.F. Burns
2021-06-24 14:21 ` Oleksandr Natalenko
2021-06-25 10:12 ` Oleksandr Natalenko
2022-06-12 22:29 R.F. Burns
2023-06-13 3:10 R.F. Burns
2024-06-12 20:16 R.F. Burns
2025-07-01 3:58 R.F. Burns
2026-06-13 3:04 R.F. Burns
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=5B4A5F89-935F-48DA-941D-54F7B0FC2FAA@mac.com \
--to=mrmacman_g4@mac.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®