Bug#568126: lm-sensors: Resource conflicts policy in kernel has changed

["Didier 'OdyX' Raboud" <didier@raboud.com>]

Le lundi 2 août 2010 00:27:10, vous avez écrit :
> On Fri, Feb 05, 2010 at 11:58:36AM -0500, Dave Witbrodt wrote:
> > Package: lm-sensors
> > Severity: normal
> > 
> > 
> > This looks like a consequence of a recent change in kernel policy
> > regarding resource conflicts.  According to the 'kernel-parameters.txt'
> > file in the kernel documentation, the default value of the parameter
> > "acpi_enforce_resources" has changed:
> > 
> > $ grep -A 15 acpi_enforce_resources Documentation/kernel-parameters.txt
> > 
> > 	acpi_enforce_resources=	[ACPI]
> > 	
> > 			{ strict | lax | no }
> > 			Check for resource conflicts between native drivers
> > 			and ACPI OperationRegions (SystemIO and SystemMemory
> > 			only). IO ports and memory declared in ACPI might be
> > 			used by the ACPI subsystem in arbitrary AML code and
> > 			can interfere with legacy drivers.
> > 			strict (default): access to resources claimed by ACPI
> > 			is denied; legacy drivers trying to access reserved
> > 			resources will fail to bind to device using them.
> > 			lax: access to resources claimed by ACPI is allowed;
> > 			legacy drivers trying to access reserved resources
> > 			will bind successfully but a warning message is logged.
> > 			no: ACPI OperationRegions are not marked as reserved,
> > 			no further checks are performed.
> > 
> > I recently resolved a very similar issue myself by adding
> > "acpi_enforce_resources=lax" to my kernel boot line in GRUB.
> 
> Didier, does this fix the issue for you?
> 
> Cheers,
>         Moritz

Hi Moritz, 

yes it does. But if this option is to stay, it really should get either i) set 
automagically by <insert smart package name here> ii) documented visibly in 
release notes maybe ?

Thanks for your following-up on that bug.

Cheers, OdyX

-- 
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
didier@raboud.com