Bug 65057
Summary: | Use of lm_sensors fries IBM laptops | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | jon |
Component: | lm_sensors | Assignee: | Phil Knirsch <pknirsch> |
Status: | CLOSED RAWHIDE | QA Contact: | Ben Levenson <benl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | bero, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-27 15:36:46 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: |
Description
jon
2002-05-16 20:22:05 UTC
Preferred fix: Make the lm_sensors lib abort if it detects a broken Thinkpad (probably identifiable through dmidecode?). Bero, how does ksysguardd work? Does it simply run sensors-detect or does it use some libary calls? If so, a patch should be fairly easy in order to avoid frying more Thinkpads (although that won't make IBM fix their broken BIOS's, but i agree, better than having a fried laptop). Read ya, Phil It uses the library. I think the optimal fix [other than making IBM fix their **** BIOSes, of course] is adding assert(THIS_IS_NOT_A_THINKPAD); to sensors_init(), which would fix ksysguardd and everything else. (Crashing the app is probably preferrable over destroying the machine ;) ). Latest rawhide package of lm_sensors now requires kernel-utils which in turn contains dmidecode with which sensors_detect checks if it is run on a Thinkpad and bails out if it is. Read ya, Phil |