Bug#568126: lm-sensors: Resource conflicts policy in kernel has changed
On Wed, Jan 05, 2011 at 12:44:12PM +0100, Didier 'OdyX' Raboud wrote:
> tag 568126 -moreinfo +patch
> Le Sunday 2 January 2011 15:57:30 Julien Cristau, vous avez écrit :
> > tag 568126 moreinfo
> > severity 568126 minor
> > kthxbye
> > On Thu, Aug 5, 2010 at 11:59:59 -0400, Moritz Muehlenhoff wrote:
> > > We won't diverge from the kernel default settings, so I'm reassigning to
> > > release-notes. Please provide a proposed text to ease the work of the
> > > people preparing the release notes.
> > I don't really understand what we're supposed to be documenting here, so
> > if you want it in the release notes it'd be really helpful to provide
> > proposed text and references as Moritz asked.
> > Cheers,
> > Julien
> Although I'm not convinced that this bug would warrant a release-notes entry (as
> it doesn't necessarily affect many people), let's propose a text (linux-only of
> 5.1.5. Change in kernel policy regarding resource conflicts
> The default setting for the acpi_enforce_resources parameter in the new Linux
> kernel version has changed to be "strict" by default. This can lead some legacy
> sensor drivers to be denied access the sensors hardware. This can be
> workarounded by setting this parameter to "lax", e.g. by appending
> "acpi_enforce_resources=lax" to the kernel boot line.
> Hrm; I'm no native english speaker nor kernel specialist; I hope my text helps.
Looks good to me.