Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 580699

Summary:	hwmon: (coretemp) Get TjMax value from MSR for i series CPUs
Product:	Red Hat Enterprise Linux 5	Reporter:	Dean Nelson <dnelson>
Component:	kernel	Assignee:	Dean Nelson <dnelson>
Status:	CLOSED ERRATA	QA Contact:	Hangbin Liu <haliu>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.5	CC:	haliu, me
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	580700 (view as bug list)		Environment:
Last Closed:	2011-01-13 21:25:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	559228
Bug Blocks:

Description Dean Nelson 2010-04-08 19:33:34 UTC

Description of problem:
Doing a 'modprobe coretemp' on dell-per210-01.lab.bos.redhat.com, a system with CPU family=6 and model=30, and installed with RHEL5.6 that includes the patch submitted for bug 559228, results in console errors that indicate a failure to get the proper TjMax value. I've also seen this failure on dell-per710-01.lab.bos.redhat.com, which is a system with CPU family=6 and model=26.


Version-Release number of selected component (if applicable):
kernel-2.6.18-194.el5


How reproducible:
Always.


Steps to Reproduce:
1. modprobe coretemp


Actual results:
(on dell-per210-01.lab.bos.redhat.com which has 8 CPUs (family=6 and model=30).

[root@dell-per210-01 ~]# modprobe coretemp
coretemp coretemp.0: Unable to access MSR 0xEE, for Tjmax, left at default
coretemp coretemp.1: Unable to access MSR 0xEE, for Tjmax, left at default
coretemp coretemp.2: Unable to access MSR 0xEE, for Tjmax, left at default
coretemp coretemp.3: Unable to access MSR 0xEE, for Tjmax, left at default
coretemp coretemp.4: Unable to access MSR 0xEE, for Tjmax, left at default
coretemp coretemp.5: Unable to access MSR 0xEE, for Tjmax, left at default
coretemp coretemp.6: Unable to access MSR 0xEE, for Tjmax, left at default
coretemp coretemp.7: Unable to access MSR 0xEE, for Tjmax, left at default
[root@dell-per210-01 ~]#


Expected results:
Getting the proper TjMax value from MSR should not fail. The upstream patch as it is currently produces the following results on dell-per210-01.labs.bos.redhat.com.

[root@dell-per210-01 ~]# modprobe coretemp
coretemp : The TjMax is 99
[root@dell-per210-01 ~]#


Additional info:
A two-patch patchset has been submitted upstream to lm-sensors by huaxu.wan that addresses this problem. (See http://lists.lm-sensors.org/pipermail/lm-sensors/2010-March/027967.html) This patchset has not been accepted yet.

Comment 1 RHEL Program Management 2010-07-30 00:28:59 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 2 Dean Nelson 2010-07-30 01:13:11 UTC

The patchset posted by huaxu.wan @linux.intel.com to lm-sensors has been accepted into linux-2.6:

  http://git.kernel.org/linus/5db47b009d17d69a2f8d84357e7b24c3e3c2edec
  http://git.kernel.org/linus/a321cedb12904114e2ba5041a3673ca24deb09c9

Comment 7 Jarod Wilson 2010-08-11 00:12:15 UTC

in kernel-2.6.18-211.el5
You can download this test kernel from http://people.redhat.com/jwilson/el5

Detailed testing feedback is always welcomed.

Comment 11 errata-xmlrpc 2011-01-13 21:25:21 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0017.html