Bug 588115 - Xeon 3330 not supported under coretemp (coretemp: Unknown CPU model 17)
Summary: Xeon 3330 not supported under coretemp (coretemp: Unknown CPU model 17)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lm_sensors
Version: 5.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jaromír Cápík
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On: 559228 595390
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-02 18:23 UTC by David Kovalsky
Modified: 2023-09-14 01:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-03 12:48:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Kovalsky 2010-05-02 18:23:59 UTC
Description of problem:
Xeon 3330, but it's not supported under lm_sensors. 

syslog shows: 
kernel: w83627ehf: Found W83627DHG chip at 0x290  
kernel: coretemp: Unknown CPU model 17   


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

How reproducible:
Always

Comment 1 David Kovalsky 2010-05-24 14:03:21 UTC
So I've tried the kmod-coretemp from elrepo with updated lmsensors from the same repo:

http://elrepo.org/linux/elrepo/el5/x86_64/RPMS/kmod-coretemp-xen-1.1-6.el5.elrepo.x86_64.rpm

http://elrepo.org/linux/elrepo/el5/x86_64/RPMS/lm_sensors-2.10.8-2.el5.elrepo.x86_64.rpm


Works like charm. lm-sensors output:
coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +38°C  (high =  +100°C)                   

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +25°C  (high =  +100°C)                   

coretemp-isa-0002
Adapter: ISA adapter
Core 2:      +34°C  (high =  +100°C)                   

coretemp-isa-0003
Adapter: ISA adapter
Core 3:      +41°C  (high =  +100°C)  


I'll keep this bug open for the update to 2.10.8 (latest supported in the 2.10 branch) and also open a bug for the kernel part to happen.

Comment 3 RHEL Program Management 2010-08-09 19:31:17 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2011-05-31 14:59:12 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 5 RHEL Program Management 2014-03-07 13:37:46 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 7 RHEL Program Management 2014-06-03 12:48:30 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).

Comment 8 Red Hat Bugzilla 2023-09-14 01:21:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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