Your message dated Fri, 06 May 2016 06:12:21 +0000
with message-id <[email protected]>
and subject line Bug#823114: Removed package(s) from unstable
has caused the Debian Bug report #623545,
regarding [cpuburn] README outdated on overheating causes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
623545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623545
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cpuburn
Version: 1.4a-1
Severity: minor
Tags: upstream
The README contains a small paragraph on the causes of overheating:
If sub-spec, your system may lock up after 2-10 minutes. It shouldn't.
burn* are just an unpriviliged user processes. But it probably means
your CPU is undercooled, most likely no thermal grease or other interface
material between CPU & heatsink. Or some other deficiency.
First, I don't know what "sub-spec" means.
As discussed above, overclocking is a major cause of overheating. But
overclockers should know that.
I agree the lack of thermal grease or something like that must be
another major cause, however that must rarely happen except for those
who assemble their PCs themselves, and I guess these people should know
what they're doing.
But the vast majority of computers are bought pre-assembled and
shouldn't have this issue. I bought my first branded (non-clone, in this
case Gateway) PC one year ago, and I noticed overheating problems
earlier this month. The Intel Core i3 330 CPU would reach 86 °C and
throttling would start. I could reproduce that easily with burnBX. I
opened the laptop's case and saw no dust. I didn't see any way to access
the CPU even after removing some 20 screws. So I called the retailer,
Future Shop (which usually has outrageous practices, if that's different
from most computer shops), told them about the problem, and they told me
the problem had to be dust, the solution being to bombard the case with
air. The first guy I spoke to said this should be done every 6 months.
The second said each 2-3 months. I couldn't believe I had never heard
about that before, that the Gateway manual didn't even mention this
problem, and that this would have to be done so often. But having no
choice, I tried it and was happy to confirm the CPU now runs much
cooler, about 20 ° less with 4 simultaneous burnBX-s, which is now
normal. This laptop is almost always in my basement, which is not
particularly unclean. The only somewhat unusual thing is it runs day and
night. Still, with that experience and what the store people told me, I
would challenge the README's claim and say that nowadays, with
pre-assembled laptops being so common, if we can no more just put the
vacuum cleaner in the PC, dust must be a more likely cause of
overheating than lack of interface material. It should be at least
mentioned.
--- End Message ---
--- Begin Message ---
Version: 1.4a-6+rm
Dear submitter,
as the package cpuburn has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/823114
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
