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

2010-08-05 Thread Didier 'OdyX' Raboud
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
did...@raboud.com



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201008051730.09081.did...@raboud.com



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

2010-08-05 Thread Moritz Muehlenhoff
reassign 568126 release-notes
thanks

On Thu, Aug 05, 2010 at 05:30:08PM +0200, Didier 'OdyX' Raboud wrote:
 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.

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.

Cheers,
Moritz



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100805155959.ga14...@galadriel.inutil.org



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

2010-08-01 Thread Moritz Muehlenhoff
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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100801222710.ga31...@galadriel.inutil.org



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

2010-02-05 Thread Dave Witbrodt
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.


HTH,
Dave W.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32.2-0git+k10temp+f71889fg+r600fix.091222.desktop.kms (SMP 
w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages lm-sensors depends on:
ii  libc62.10.2-5Embedded GNU C Library: Shared lib
ii  libsensors4  1:3.1.1-4+svn091221 library to read temperature/voltag
ii  lsb-base 3.2-23  Linux Standard Base 3.2 init scrip
ii  perl 5.10.1-9Larry Wall's Practical Extraction 
ii  sed  4.2.1-6 The GNU sed stream editor

lm-sensors recommends no packages.

Versions of packages lm-sensors suggests:
pn  i2c-tools none (no description available)
pn  read-edid none (no description available)
pn  sensord   none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org