Bug 498757

Summary:	mention lm_sensors changes
Product:	[Fedora] Fedora Documentation	Reporter:	Tom Horsley <horsley1953>
Component:	release-notes	Assignee:	John J. McDonough <wb8rcr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Karsten Wade <kwade>
Severity:	medium	Docs Contact:
Priority:	low
Version:	devel	CC:	eric, relnotes, wb8rcr
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-06-09 19:27:26 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 Tom Horsley 2009-05-02 23:10:03 UTC

Description of problem:

I was quite confused by the kernel changes that had the side effect
of disabling almost all the lm_sensors info. Bug 496355 shows my
confusion and the kernel changes which caused it as well as the
kernel boot parameter that can be used to get old behavior.
Seems like this would be good info to go in the release notes
somewhere (if it is already there, I couldn't find it).

The acpi_enforce_resources=lax boot parameter got back my sensor
data, and copying the /etc/sensors3.conf file from fedora 10 got
back my interpretation of that data.

Comment 1 John J. McDonough 2009-06-09 19:27:26 UTC

Added to zero-day release notes.  Basically, the release notes entry points to 496355, better to admonish people of the risks.