1002:7145 [Lenovo ThinkPad R60] Laptop too hot with radeon drivers

Bug #1164557 reported by Rainer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

My laptop goes to very high temperature. First I think it was a fan problem. I adjusted thinkfan to use the disengaged option. Now my fan is at maximum speed if the temperature goes over 67°C. But still it is not possible to run the laptop for a longer time an 100% CPU. It then overheats and stops working. For example just after clamscan starts working the fan is at maximum speed (5600 revolutions) and the temperature goes up over 85°C, the CPU usage is the about 70%.

My standard governer is "ondemand". By using "powersave" the temperature will be about 5-10°C decrease.

My investigation show me that in my opinion the VID is to high. To verify this I do the following:
- rdmsr -p0 [1] 0x0199 for every speed steps
- the governer "ondemand" switches the MSR 0x199 between
   - 0x0613, which means 1GHz and 1.275V?
   - 0x081c, which means 1,33GHz and 1.3875V?
   - 0x0b28, which means 1,83GHz and 1.5375V?
> by 100% CPU the laptop overheats and stops

- set the governer to userspace 1.833GHz
- reduce the VID using: wrmsr -p0 [1] 0x0199 0x0b20
> the temperature goes not over 65°C by starting load that goes to 100% CPU!.

I see that the VID is always set to 0x0b28 when the governor change the speed to the highest speed. I don't know if the governor or an other kernel module set the VID The Sped (FID) is selected by the governor.

WORKAROUND: Use the powersave CPU governor.

---
ApportVersion: 2.12.6-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3165 F.... pulseaudio
CasperVersion: 1.336ubuntu1
CurrentDmesg:
 [ 71.182993] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 71.185122] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 71.982542] iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
 [ 72.055058] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
 [ 72.055518] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
DistroRelease: Ubuntu 14.04
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131108)
MachineType: LENOVO 9461DXG
MarkForUpload: True
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcVersionSignature: Ubuntu 3.12.0-2.5-generic 3.12.0
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-2-generic N/A
 linux-backports-modules-3.12.0-2-generic N/A
 linux-firmware 1.117
Tags: trusty
Uname: Linux 3.12.0-2-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/28/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7CETD3WW (2.23 )
dmi.board.name: 9461DXG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7CETD3WW(2.23):bd08/28/2009:svnLENOVO:pn9461DXG:pvrThinkPadR60:rvnLENOVO:rn9461DXG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 9461DXG
dmi.product.version: ThinkPad R60
dmi.sys.vendor: LENOVO

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1164557

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Laptop to hot - VID to high

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc5-raring/

tags: added: kernel-da-key
Revision history for this message
Rainer (r-e-l) wrote : ProcEnviron.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Rainer (r-e-l) wrote : Re: Laptop to hot - VID to high

Hi,
I tryed the apport command twice and it never ends. I allways must kill them (1. after an hour, 2. after a nigth. Parallel I updateted to mainline. As a last trial I tryed the apport again afer booting with mainline kernel. Now apport has worked.

The problem still exists with the mainline kernel. But I see one Problem with the mainline kernel: ACPIBatteries does say "No Batteries". Will ignore it.

Regards Rainer

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Rainer (r-e-l) wrote :

Hi Joseph,

I start reading what I should do to an upstream bug report. I was stopped because I don't be able to determind the correct Maintainer.

I don't know which part of the kernel is doind the error.

What can I do furthermore??

Thanks and regards Rainer

Revision history for this message
penalvch (penalvch) wrote :

Rainer, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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 (not the daily folder, but the one all the way at the bottom) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.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.12-rc7

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.

tags: added: kernel-therm needs-kernel-logs needs-upstream-testing regression-potential
removed: overheating vid
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Rainer (r-e-l) wrote : AlsaInfo.txt

apport information

tags: added: trusty
description: updated
Revision history for this message
Rainer (r-e-l) wrote : BootDmesg.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : CRDA.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : IwConfig.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : Lspci.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : Lsusb.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcEnviron.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcModules.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : PulseList.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : RfKill.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : UdevDb.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : UdevLog.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : WifiSyslog.txt

apport information

description: updated
Revision history for this message
Rainer (r-e-l) wrote : AlsaInfo.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : BootDmesg.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : CRDA.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : IwConfig.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : Lspci.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : Lsusb.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcEnviron.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : ProcModules.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : PulseList.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : RfKill.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : UdevDb.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : UdevLog.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : WifiSyslog.txt

apport information

Revision history for this message
Rainer (r-e-l) wrote : Re: Laptop to hot - VID to high

Hi,
I try to do what asked for. With the Apport-collect they exits some problem. I may be double or incomplet. Sorry.

I test 3.12.0-2-generic it overheats the laptop.
3.12.0-31200-generic overheats the laptop too.

If any further testing or info is required please call.

Thanks and regards Rainer

tags: removed: needs-upstream-testing
tags: added: 3.12.0-2-generic kernel-bug-exits-upstream-
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
description: updated
description: updated
tags: removed: kernel-bug-exits-upstream- needs-kernel-logs
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-v3.12
removed: kernel-bug-exists-upstream
summary: - Laptop to hot - VID to high
+ [Lenovo ThinkPad R60] Laptop to hot - VID to high
Revision history for this message
penalvch (penalvch) wrote : Re: [Lenovo ThinkPad R60] Laptop to hot - VID to high

Rainer, did this problem not occur in a release prior to Precise?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Rainer (r-e-l) wrote :

Hi,

this is not easy to answer.

As I start with Ubuntu 10.x on my laptop I got hot problems at load. I start then to add some packages (I not rember more which one) an dthe problem disapears!

I have done an update to the second 10.x and I don't have any problem.

After updating to Precise first I see no problem, but short after I occurs. This is because in normal usage, like internet writng viewing, I got no problems. When I start cpu load activity like a lot of graphics or video work the laptop overheads an hangup.

I tried to figure out if I have done some mistake, like wrong governor packages i.e. Also google gave no solution. One interestin point is: I use the package thinkfan. I have it customized just after starting the overheating problems at the beginning. After updating to Precise I found that thinkfan was configured to use the fan in the level 0-7. Which means max 3900 fan speed. So I found using google that there is a fan level disengaded (which brings an fan speed 5800. I activate this under precis for the first time. But this don't help to prevent overheading. At 68°C cpu temp run my fan with 5800 revolution, what he have never done before Precise.

This seems to be a serious and useable Linux problem: I often get computer hangups if I use different Linux live system on many computers to do a offline backup. When I then run parallel partimage tasks for different disks those computers hang. I guess overheating. Running the partimage for the disks in serial get no problem.

To circumvent my problem I have writen a pearl script which monitors the cpu temp every 10s and switch to governor powersave at 82°C and back to conserative at 73°C.

Hope this explains in dead what happens regards Rainer

penalvch (penalvch)
tags: added: lucid
removed: 3.12.0-2-generic regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Rainer, as WORKAROUNDs, in addition to maxing out your fan speed, I was going to suggest using powersave governor setting. At this point, it would be helpful if a powertop was run and the top power consuming processes were identified. Could you please do this?

Revision history for this message
Rainer (r-e-l) wrote :

Hi Christopher,

the problem is not the the power consuming procceses. It is normal that processing of videos or graphis are power consuming.

I see no reason that the processor overheat if both processors are used at 100%. Before Precise it works and under Windows too. Powersave brings my processors to work at 1GHz every time. With Ondemand it switches between 1, 1.33 and 1.88GHz. If the processors go to hot the Linux should reduce the VID or automaticaly lower the CPU frequence for while.

I circumvent the problem by my private pearl script which switches between powersave and ondemand.

I attach the script for understanding.

I would like to take a look in the source where the VID is set to understand the problem. But I don't find the rigth source module.

As a summary the top power comsuming tasks are normal and need not to be identified.

Hope this clearify and regards Rainer

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: latest-bios-2.23
penalvch (penalvch)
summary: - [Lenovo ThinkPad R60] Laptop to hot - VID to high
+ 1002:7145 [Lenovo ThinkPad R60] Laptop to hot - VID to high
description: updated
Revision history for this message
penalvch (penalvch) wrote : Re: 1002:7145 [Lenovo ThinkPad R60] Laptop to hot - VID to high

Rainer, thank you for your comments. I can advise that unfortunately putting in some VID logic in augmenting the ondemand governor, or the cpufreq module in anyway like this is just simply not going to happen.

Despite this, one vital piece of information to know is are you able to utilize the proprietary drivers for your card following https://help.ubuntu.com/community/BinaryDriverHowto/ATI (strongly prefer downstream, but upstream for testing would be fine as a worst case)?

Changed in linux (Ubuntu):
importance: Medium → Low
status: Confirmed → Incomplete
summary: - 1002:7145 [Lenovo ThinkPad R60] Laptop to hot - VID to high
+ 1002:7145 [Lenovo ThinkPad R60] Laptop too hot with radeon drivers
description: updated
Revision history for this message
Rainer (r-e-l) wrote : Re: [Bug 1164557] Re: 1002:7145 [Lenovo ThinkPad R60] Laptop to hot - VID to high
Download full text (6.0 KiB)

Hello Christopher,

thanks to Your answer.

I wrote this by email, because I don't now if You immediate receive
chandes in the LaunchPad and a lot of my answers already in the
Launchpad entry.

I believe there is going some thing wrong. My laptop goes hot. I googled
a lot an try a lot. The current Radeon card driver is the open version
not the AMD. I changed what ever can reduce power. But the Radeon is
not the problem, it only goes on top. the real problem is the CPU
(Intel) is to hot.

I can say it is the VID on the Intel CPU which is to high! Before I
switch from Windows to LINUX I had have been no problems with Windows
and LINUX. After going to newer LINUX releases the problem appears. My
investigating shows that the CPU voltage is to high, and if I set the
CPU voltage manually lower it will work without any problem. But the
governor switch always back to the high voltage at the next governor
cycle. I believe this is done by the kernel. I tryed to find where in
the source with no success.

In addition I tryed to use LINUX-PHC which would solve the problem if it
work. It did, but a lot of other problems occur by using the ubuntu-tp
kernel. so I can say LINUX-PHC would help, but it must be integrated as
standard in Ubuntu to solve all the other problems (Integration problems).

For my normal processing my bypass with the previous descripted script
(if temperature to high go to governor Powersave till the temperature is
lowered) works well. But if I must use a live Linux for backup, I must
be carefull and do not high CPU usage.

Regards Rainer

On 03.01.2014 07:09, Christopher M. Penalver wrote:
> Rainer, thank you for your comments. I can advise that unfortunately
> putting in some VID logic in augmenting the ondemand governor, or the
> cpufreq module in anyway like this is just simply not going to happen.
>
> Despite this, one vital piece of information to know is are you able to
> utilize the proprietary drivers for your card following
> https://help.ubuntu.com/community/BinaryDriverHowto/ATI (strongly prefer
> downstream, but upstream for testing would be fine as a worst case)?
>
> ** Changed in: linux (Ubuntu)
> Importance: Medium => Low
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Summary changed:
>
> - 1002:7145 [Lenovo ThinkPad R60] Laptop to hot - VID to high
> + 1002:7145 [Lenovo ThinkPad R60] Laptop too hot with radeon drivers
>
> ** Description changed:
>
> My laptop goes to very high temperature. First I think it was a fan
> problem. I adjusted thinkfan to use the disengaged option. Now my fan is
> at maximum speed if the temperature goes over 67°C. But still it is not
> possible to run the laptop for a longer time an 100% CPU. It then
> overheats and stops working. For example just after clamscan starts
> working the fan is at maximum speed (5600 revolutions) and the
> temperature goes up over 85°C, the CPU usage is the about 70%.
>
> My standard governer is "ondemand". By using "powersave" the temperature
> will be about 5-10°C decrease.
>
> My investigation show me that in my opinion the VID is to high. To verify this I do the following:
> - rdmsr -p0 [1]...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.