https://bugzilla.kernel.org/show_bug.cgi?id=42682


Len Brown <l...@kernel.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |l...@kernel.org
          Component|Power-Fan                   |BIOS
         Resolution|                            |INVALID
         AssignedTo|acpi_power-fan@kernel-bugs. |acpi_b...@kernel-bugs.osdl.
                   |osdl.org                    |org




--- Comment #3 from Len Brown <l...@kernel.org>  2012-01-31 02:54:51 ---
In 2.6.39, commit 9ad19ac456a5f097f7cbbfef820b95297d6a934f
(ACPICA: Split large dsopcode and dsload.c files)
broke this feature.

It was repaired in by commit 
da4d8b287abe783d30e968155614531a0937d090
(ACPICA: Put back the call to acpi_os_validate_address)
in Linux 3.3 merge window

which was back-ported to linux stable, including
0726687ca114dfbba266452fefa6fd05080c9826
in 3.2.2

So I hate to say it, but but this warning is a correct
indication of a bug in your BIOS that Linux ignored
between 2.6.39 and 3.2.1.

If you want to ignore the BIOS bug, you need to manually
use the cmdline acpi_enforce_resources=lax,
or acpi_enforce_resources=no to allow it.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to