kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #15204
[Bug 563815] Re: Critical temperature reached (100 C), shutting down. throttling too little, too late.
Wolfgang Kufner, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .
If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:
apport-collect -p linux <replace-with-bug-number>
Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER
where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11.1
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing
If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER
As well, please remove the tag:
needs-upstream-testing
Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/563815
Title:
Critical temperature reached (100 C), shutting down. throttling too
little, too late.
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
[Workaround 1 (quick)]
As a workaround the maximum cpu frequency can be limited:
as root: echo 1333000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq; echo 1333000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
to check the current maximum frequency:
grep . /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq
[Workaround 2 (preferred)]
Clean the notebook. There is, in time, no way around this if the notebook is supposed to run with more than 1GHz on 100% load. There is massive dust caking between the fan and the cooling fins.
The main service hatch needs to be opened with a screwdriver. Then two screws for the fan need to be removed. The fan can then be moved away. The dust cake can then easily be removed.
Caution, e.g. with regard to static electricity and loss of warranty, needs to be applied. The risk is entirely your own.
Result of the cleaning operation: the temperature settles at a mere 70°C on 100% load (at the full 2.17 GHz) on a flat table at about 25°C room temperature.
Conclusion: It would still be nice if temperature control were more agressive. This would also conceivably be advantageous when the notebook is not on a hard, flat surface and cooling is therefore hampered. And temperature control measures at over 90°C would never get in the way of normal operation anyway, where temperature does not get that high.
[Report]
Under heavy use the Acer Extensa 5630Z always overheats and shuts down. I noticed this in lucid, but karmic shows the same principal problem.
The main culprit seems to be that the clock frequency is reduced too little and too late.
It should reduce clock frequency more/sooner to avoid the forced shutdowns.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-20-generic 2.6.32-20.30
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: wolfgang 1230 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf4800000 irq 21'
Mixer name : 'Intel G45 DEVCTG'
Components : 'HDA:10ec0268,1025013c,00100101 HDA:14f12c06,10250093,00100000 HDA:80862802,80860101,00100000'
Controls : 21
Simple ctrls : 12
Date: Thu Apr 15 15:08:59 2010
HibernationDevice: RESUME=UUID=d4760b83-2892-4b31-bf01-cb6c7d267f1f
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100226)
MachineType: Acer Extensa 5630
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-20-generic root=/dev/sda7 i915.powersave=0 mmc_removable=0 thermal.psv=80 quiet splash
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
0: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: rt2860sta
Title: [STAGING]
dmi.bios.date: 12/05/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.25
dmi.board.name: Homa
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.25:bd12/05/2008:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5630
dmi.product.version: 0100
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/563815/+subscriptions