Bug 440225 - lm_sensors / coretemp General parse error
Summary: lm_sensors / coretemp General parse error
Keywords:
Status: CLOSED DUPLICATE of bug 436767
Alias: None
Product: Fedora
Classification: Fedora
Component: lm_sensors
Version: 8
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-02 12:42 UTC by Brian Long
Modified: 2008-04-02 14:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-02 14:09:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
strace output from running /usr/bin/sensors (8.79 KB, text/plain)
2008-04-02 12:55 UTC, Brian Long
no flags Details

Description Brian Long 2008-04-02 12:42:15 UTC
Description of problem:
service lm_sensors start gives an error message:
Starting lm_sensors: loading module coretemp General parse error

Version-Release number of selected component (if applicable):
lm_sensors-2.10.5-1.fc8

How reproducible:
This started when kernel-2.6.24.3-34.fc8 was released and continues with
kernel-2.6.24.3-50.fc8.

Steps to Reproduce:
1. Add MODULE_0=coretemp to /etc/sysconfig/lm_sensors on Thinkpad T61p
2. run service lm_sensors start
 
Actual results:
General parse error
lsmod | grep coretemp shows the module is loaded

Expected results:
lm_sensors should start

Comment 1 Brian Long 2008-04-02 12:55:59 UTC
Created attachment 300057 [details]
strace output from running /usr/bin/sensors

Comment 2 Brian Long 2008-04-02 12:59:46 UTC
I updated to lm_sensors-2.10.6-53.fc8 from AtRPMS and sensors no longer gives a
General Parse error.  It appears something changed in the thinkpad hwmon sysfs
entry which causes grief for lm_sensors 2.10.5.  Please consider releasing
2.10.6 for Fedora 8.

Comment 3 Hans de Goede 2008-04-02 14:09:07 UTC
This was already reported as bug 436767 and a fix has been available in
updates-testing. Thanks for the reminder though, since the fix in
updates-testing has not received any negative feedback I'll be pushing it to the
stable updates repository now.


*** This bug has been marked as a duplicate of 436767 ***


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