[RC5] D.net causing overheating
Colin L. Hildinger
colin at ionet.net
Wed Nov 14 20:42:41 EST 2001
You make a true statement. The other side of the statement is that some
computers cannot run at full load all the time because of cooling issues,
whether it be heat sink issues, high ambient conditions, etc. I used to
have a problem with my upstairs computer locking up in the summer during the
day. My thermostat offsets the temperature during the day and it would get
rather warm upstairs in the bedroom in August. I would get home from work
to a cool house and a locked computer. I set the thermostat offset a little
lower and the problem went away. <shrug> No biggie.
----- Original Message -----
From: "Bruce Wilson" <bwilson at distributed.net>
To: <rc5 at lists.distributed.net>
Sent: Wednesday, November 14, 2001 7:26 PM
Subject: RE: [RC5] D.net causing overheating
> Hi, Ryan.
> In general, we've never (to my knowledge) seen a documented case where
> dnetc itself was the cause of an overheat/crash which would not also
> have been produced by any other task which consumes all available CPU.
> I have heard that some organizations and even PC vendors use dnetc to
> burn in their new computers. If the CPU can hold up under 100%
> utilization for N days, they decide it's going to last long enough for
> Bruce Wilson <bwilson at distributed.net>
> PGP KeyID: 5430B995, http://www.toomuchblue.com/
> rm -rf /bin/laden && chmod 0777 /dev/freedom
> | -----Original Message-----
> | From: owner-rc5 at lists.distributed.net
> | [mailto:owner-rc5 at lists.distributed.net] On Behalf Of Ryan Malayter
> | Sent: Wednesday, November 14, 2001 14:47
> | To: 'rc5 at lists.distributed.net'
> | Subject: [RC5] D.net causing overheating
> | I've come across a real-world example of the d.net client
> | overheating &
> | freezing a machine that otherwise performed normally. This has been
> | discussed as a theoretical problem with the d.net client on
> | the past in
> | this forum.
> | An older Pentium Pro 200 user workstation I had cracking away
> | on my network
> | started freezing intermittently every hour or so - likely a hardware
> | problem, since we use a standard, known-good Win2k disk image on our
> | workstation machines. Instead of cracking the case and diagnosing the
> | hardware, I decided to remove d.net to see what would happen.
> | I had the user
> | continue using the machine for more than a week - no freezes.
> | I've just put the d.net client back on to see if my little
> | experiment is
> | repeatable on this machine (which probably has a loose heat
> | sink or slow
> | fan).
> | :::Ryan Malayter, MCSE
> | :::Bank Administration Institute
> | :::Chicago, Illinois, USA
> | --
> | To unsubscribe, send 'unsubscribe rc5' to
> | majordomo at lists.distributed.net
> | rc5-digest subscribers replace rc5 with rc5-digest
> To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
> rc5-digest subscribers replace rc5 with rc5-digest
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5