Bug 737700 - CPU temperature too high in Fedora 16
Summary: CPU temperature too high in Fedora 16
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-12 22:17 UTC by Erinn Looney-Triggs
Modified: 2011-09-12 23:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-12 23:24:51 UTC


Attachments (Terms of Use)

Description Erinn Looney-Triggs 2011-09-12 22:17:51 UTC
Description of problem:
This probably gives the best summary here:
https://lists.fedoraproject.org/pipermail/test/2011-September/102788.html

But the long and the short of it, after upgrading the F 16 I am constantly seeing thermal events for the VPU being logged.

A sampling:
[ 2116.023711] intel ips 0000:00:1f.6: MCP limit exceeded: Avg temp 9487, limit 9000
[ 2121.011212] intel ips 0000:00:1f.6: MCP limit exceeded: Avg temp 9687, limit 9000
[ 2125.998701] intel ips 0000:00:1f.6: MCP limit exceeded: Avg temp 9799, limit 9000
[ 2185.848650] intel ips 0000:00:1f.6: MCP limit exceeded: Avg temp 9366, limit 9000
[ 2190.836146] intel ips 0000:00:1f.6: MCP limit exceeded: Avg temp 9699, limit 9000
[ 2195.823651] intel ips 0000:00:1f.6: MCP limit exceeded: Avg temp 9799, limit 9000

When running under windows I do not have this issue. When running under Fedora 15 I do not have this issue. I am unsure at this point if it is in fact the kernel, but given that I booted a F 15 rescue disk with an older kernel and chrooted into my F 16 install, and then ran stress -c 5 without issue I believe it probably is related to the kernel. 

The hardware is a Lenovo ThinkPad T510. Smolt profile here:
http://www.smolts.org/client/show/pub_89da1bce-aee0-447a-b859-06a44111f08b

Let me know what I can do to help diagnose this issue.

Version-Release number of selected component (if applicable):

rpm -q kernel
kernel-3.1.0-0.rc3.git0.0.fc16.x86_64
kernel-3.1.0-0.rc4.git0.0.fc16.x86_64
kernel-3.1.0-0.rc5.git0.0.fc16.x86_64

Comment 1 Erinn Looney-Triggs 2011-09-12 23:24:51 UTC
I was able to reproduce this in Windows, I believe it to be a HW issue now. Sorry for the inconvenience.

-Erinn


Note You need to log in before you can comment on or make changes to this bug.