acpi (4)Table of Contents
acpi - Advanced Configuration and Power Management support
The acpi driver provides support for the Intel/Microsoft/Compaq/Toshiba
ACPI standard. This support includes platform hardware discovery (superseding
the PnP and PCI BIOS), as well as power management (superseding
APM) and other features. ACPI core support is provided by the ACPI CA
reference implementation from Intel.
Note that the acpi driver is automatically loaded by the loader(8) , and
should only be compiled into the kernel on platforms where
The acpi driver is intended to provide power management without user
intervention. Thus, some of these sysctls are controlled automatically
by the power_profile rc(8) script, which can be configured via
rc.conf(5) . If values are specified manually, they may be overridden.
Debugging information listing the percent of total usage for each
sleep state. The values are reset when hw.acpi.cpu.cx_lowest is
Lowest Cx state to use for idling the CPU. A scheduling algorithm
will select states between C1 and this setting as system
load dictates. To enable ACPI CPU idling control, machdep.cpu_idle_hlt must be set to 1.
List of supported CPU idle states and their transition latency in
microseconds. Each state has a type (e.g., C2). C1 is equivalent
to the ia32 HLT instruction, C2 provides a deeper sleep with
the same semantics, and C3 provides the deepest sleep but additionally
requires bus mastering to be disabled.
than C3 provide even more power savings with the same semantics
as the C3 state. Deeper sleeps provide more power savings but
increased transition latency when an interrupt occurs.
Tunables can be set at the loader(8) prompt before booting the kernel or
stored in /boot/loader.conf.
Enables loading of a custom ACPI DSDT.
Name of the DSDT table to load, if loading is enabled.
Selectively disables portions of ACPI for debugging purposes.
Specify the number of task threads that are started on boot.
Limiting this to 1 may help work around various
handle parallel requests. The default value is 3.
Override any automatic quirks completely.
Set this to 1 to disable all of ACPI. If ACPI has been disabled
on your system due to a blacklist entry for your
set this to 0 to re-enable ACPI for testing.
Delay in milliseconds to wait for the EC to respond.
increasing this number if you get the error “AE_NO_HARDWARE_RESPONSE".
Override the assumed memory starting address for PCI host
Override the interrupt to use.
Enables calling the VESA reset BIOS vector on the resume path.
Some graphic chips have problems such as LCD whiteout after
resume. Try setting this to 0 if this causes problems for you.
Allow override of whether methods execute in parallel or not.
Enable this for serial behavior, which fixes “AE_AL-
errors for AML that really cannot handle parallel method execution.
It is off by default since this breaks recursive methods
and some IBMs use such code.
Turn on verbose debugging information about what
Since ACPI support on different platforms varies greatly, there are many
debugging and tuning options available.
For machines known not to work with acpi enabled, there is a
Currently, the blacklist only controls whether acpi should be disabled
or not. In the future, it will have more granularity to control
features (the infrastructure for that is already there).
To enable acpi (for debugging purposes, etc.) on machines that are on the
blacklist, set the kernel environment variable hint.acpi.0.disabled to 0.
Before trying this, consider updating your BIOS to a more recent version
that may be compatible with ACPI.
To disable the acpi driver completely, set the kernel environment variable
hint.acpi.0.disabled to 1.
Some i386 machines totally fail to operate with some or all of ACPI disabled.
Other i386 machines fail with ACPI enabled. Disabling all or
part of ACPI on non-i386 platforms (i.e., platforms where
mandatory) may result in a non-functional system.
The acpi driver comprises a set of drivers, which may be selectively disabled
in case of problems. To disable a sub-driver, list it in the kernel
environment variable debug.acpi.disabled. Multiple entries can be
listed, separated by a space.
ACPI sub-devices and features that can be disabled:
- Disable all ACPI features and devices.
- (device) Supports AC adapter.
- (feature) Probes and attaches subdevices.
will avoid scanning the ACPI namespace entirely.
- (feature) Attaches standard ACPI subdrivers and devices enumerated in the ACPI namespace. Disabling this has a similar effect to disabling ‘‘bus’’, except that the ACPI namespace will still be scanned.
- (device) Supports ACPI button devices (typically power and sleep buttons).
- (device) Control-method batteries device.
- (device) Supports CPU power-saving and speed-setting functions.
- (device) Supports the ACPI Embedded Controller interface, used to communicate with embedded platform controllers.
- (device) Supports an ISA bus bridge defined in the ACPI namespace, typically as a child of a PCI bus.
- (device) Supports an ACPI laptop lid switch, which typically puts a system to sleep.
- (feature) Do not honor quirks. Quirks automatically disable ACPI functionality based on the XS-
vendor name and revision date.
- (device) Supports Host to PCI bridges.
- (feature) Performs PCI interrupt routing.
- (device) Pseudo-devices containing resources which ACPI claims.
- (device) Supports system cooling and heat management.
- (device) Implements a timecounter using the
It is also possible to avoid portions of the ACPI namespace which may be
causing problems, by listing the full path of the root of the region to
be avoided in the kernel environment variable debug.acpi.avoid. The
object and all of its children will be ignored during the bus/children
scan of the namespace. The ACPI CA code will still know about the
To enable debugging output, acpi must be compiled with options
ACPI_DEBUG. Debugging output is separated between layers and levels,
where a layer is a component of the ACPI subsystem, and a level is a particular
kind of debugging output.
Both layers and levels are specified as a whitespace-separated list of
tokens, with layers listed in debug.acpi.layer and levels in debug.acpi.level.
The first set of layers is for ACPI-CA components, and the second is for
FreeBSD drivers. The ACPI-CA layer descriptions include the prefix for
the files they refer to. The supported layers are:
- Utility ("ut") functions
- Hardware access ("hw")
- Event and GPE ("ev")
- Table access ("tb")
- Namespace evaluation ("ns")
- AML parser ("ps")
- Internal representation of interpreter state ("ds")
- Execute AML methods ("ex")
- Resource parsing ("rs")
- Debugger implementation ("db", “dm")
- Usermode support routines ("os")
- Disassembler implementation (unused)
- All the above ACPI-CA components
- AC adapter driver
- Control-method battery driver
- ACPI, ISA, and PCI bus drivers
- Power and sleep button driver
- Embedded controller driver
- Fan driver
- Platform-specific driver for hotkeys, LED, etc.
- Power resource driver
- CPU driver
- Thermal zone driver
- Timer driver
- All the above FreeBSD ACPI drivers
The supported levels are:
- Fatal error conditions
- Warnings and potential problems
- Initialization progress
- Stores to objects
- General information and progress
- All the previous levels ACPI_LV_INIT_NAMES ACPI_LV_PARSE ACPI_LV_LOAD ACPI_LV_DISPATCH ACPI_LV_EXEC ACPI_LV_NAMES ACPI_LV_OPREGION ACPI_LV_BFIELD ACPI_LV_TABLES ACPI_LV_VALUES ACPI_LV_OBJECTS ACPI_LV_RESOURCES ACPI_LV_USER_REQUESTS ACPI_LV_PACKAGE
- All the previous levels ACPI_LV_ALLOCATIONS ACPI_LV_FUNCTIONS ACPI_LV_OPTIMIZATIONS ACPI_LV_VERBOSITY2 ACPI_LV_ALL ACPI_LV_MUTEX ACPI_LV_THREADS ACPI_LV_IO ACPI_LV_INTERRUPTS
- All the previous levels ACPI_LV_AML_DISASSEMBLE ACPI_LV_VERBOSE_INFO ACPI_LV_FULL_TABLES ACPI_LV_EVENTS
- All levels after “ACPI_LV_VER-
Selection of the appropriate layer and level values is important to avoid
massive amounts of debugging output. For example, the following configuration
is a good way to gather initial information. It enables debug
output for both ACPI-CA and the acpi driver, printing basic information
about errors, warnings, and progress.
Debugging output by the ACPI CA subsystem is prefixed with the module
name in lowercase, followed by a source line number. Output from the
FreeBSD-local code follows the same format, but the module name is uppercased.
ACPI interprets bytecode named AML (ACPI Machine Language) provided by
the BIOS vendor as a memory image at boot time. Sometimes, the AML code
contains a bug that does not appear when parsed by the Microsoft implementation.
FreeBSD provides a way to override it with your own AML code
to work around or debug such problems. Note that all AML in your DSDT
and any SSDT tables is overridden.
In order to load your AML code, you must edit /boot/loader.conf and
include the following lines.
acpi_dsdt_name="/boot/acpi_dsdt.aml” # You may change this name.
ACPI is only found and supported on i386/ia32, ia64, and amd64.
Compaq Computer Corporation, Intel Corporation, Microsoft
Phoenix Technologies Ltd., and Toshiba Corporation, Advanced Configuration and Power Interface Specification, August 25, 2003,
The ACPI CA subsystem is developed and maintained by Intel
The following people made notable contributions to the ACPI subsystem in
FreeBSD: Michael Smith, Takanori Watanabe <takawata@jp.FreeBSD.org>,
Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>, Munehiro Matsuda,
the ACPI-jp mailing list at <acpi-jp@jp.FreeBSD.org>, and many other contributors.
This manual page was written by Michael Smith <msmith@FreeB-
If the acpi driver is loaded as a module when it is already linked as
part of the kernel, odd things may happen.
- ACPI is mandatory.
- Sysctl Variables
- States greater
- Loader Tunables
- BIOSes that cannot
- BIOS, you can
- ACPI is doing.
- Disabling Acpi
- BIOS blacklist.
- ACPI support is
- DT table's OEM
- ACPI fixedfrequency
- Debugging Output
- Overriding Your Bios Bytecode
- See Also
- Nate Lawson,
- BSD February 13, 2005
- ppdcfile (5)
- tvtime-scanner (1)
- pthread_mutex_destroy (3thr)
- glGetPixelMapusv (3x)
- arl (4)
- vtoanalyze (1)
- Test::Dir (3pm)
- XGetFontProperty (3x)
- stringprep_unichar_to_utf8 (3)
- fgetws (3)
- Net::Amazon::Request::TextStream (3pm)
- kguitar (1)
- freefem (1)
- dpns-enterusrmap (1)
- XmCreateDialogShell (3)
- SetPaletteEntries (3w)
- selector (3bobcat)
- std::tr1::__detail::__numeric_constants (3cxx)
- torsocks.conf (5)
- attroff (3ncurses)