From owner-svn-doc-all@FreeBSD.ORG Tue Apr 15 16:40:29 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7152941; Tue, 15 Apr 2014 16:40:29 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 888E8113A; Tue, 15 Apr 2014 16:40:29 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3FGeTQN022993; Tue, 15 Apr 2014 16:40:29 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3FGeTbC022992; Tue, 15 Apr 2014 16:40:29 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404151640.s3FGeTbC022992@svn.freebsd.org> From: Dru Lavigne Date: Tue, 15 Apr 2014 16:40:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44562 - head/en_US.ISO8859-1/books/handbook/config X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 16:40:29 -0000 Author: dru Date: Tue Apr 15 16:40:29 2014 New Revision: 44562 URL: http://svnweb.freebsd.org/changeset/doc/44562 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/config/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/config/chapter.xml Tue Apr 15 16:12:59 2014 (r44561) +++ head/en_US.ISO8859-1/books/handbook/config/chapter.xml Tue Apr 15 16:40:29 2014 (r44562) @@ -3183,50 +3183,51 @@ hw.acpi.s4bios: 0 This usually fixes the problem of a system powering up spontaneously after a suspend or poweroff. - + BIOS Contains Buggy Bytecode - - ACPI - ASL - - - Some BIOS vendors provide incorrect or - buggy bytecode. This is usually manifested by kernel console - messages like this: + + ACPI + ASL + + + Some BIOS vendors provide incorrect + or buggy bytecode. This is usually manifested by kernel + console messages like this: - ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPC0.FIGD._STA] \\ + ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPC0.FIGD._STA] \\ (Node 0xc3f6d160), AE_NOT_FOUND - Often, these problems may be resolved by updating the - BIOS to the latest revision. Most console - messages are harmless, but if there are other problems, like - the battery status is not working, these messages are a good - place to start looking for problems. + Often, these problems may be resolved by updating the + BIOS to the latest revision. Most + console messages are harmless, but if there are other + problems, like the battery status is not working, these + messages are a good place to start looking for + problems. - + Overriding the Default <acronym>AML</acronym> - The BIOS bytecode, known as + The BIOS bytecode, known as ACPI Machine Language (AML), is compiled from a source language called ACPI Source Language (ASL). The AML is found in the table known as the Differentiated System Description Table (DSDT). - + ACPI ASL The goal of &os; is for everyone to have working ACPI without any user intervention. - Workarounds are still being developed for common - mistakes made by BIOS vendors. The - µsoft; interpreter (acpi.sys and + Workarounds are still being developed for common mistakes made + by BIOS vendors. The µsoft; + interpreter (acpi.sys and acpiec.sys) does not strictly check for adherence to the standard, and thus many BIOS vendors who only test @@ -3234,53 +3235,54 @@ hw.acpi.s4bios: 0 ASL. &os; developers continue to identify and document which non-standard behavior is allowed by µsoft;'s interpreter and replicate it so that &os; can - work without forcing users to fix the ASL. + work without forcing users to fix the + ASL. - To help identify buggy behavior and possibly fix it manually, a copy can be - made of the system's + To help identify buggy behavior and possibly fix it + manually, a copy can be made of the system's ASL. To copy the system's ASL to a specified file name, use acpidump with , to show the contents of the fixed tables, and , to disassemble the AML: - &prompt.root; acpidump -td > my.asl + &prompt.root; acpidump -td > my.asl - Some AML versions assume the user is - running &windows;. To override this, set - hw.acpi.osname="Windows - 2009" in - /boot/loader.conf, using the most recent &windows; - version listed in the ASL. - - Other workarounds may require - my.asl to be customized. If this file is edited, compile the new - ASL using the following command. Warnings can - usually be ignored, but errors are bugs that will usually + Some AML versions assume the user is + running &windows;. To override this, set + hw.acpi.osname="Windows + 2009" in + /boot/loader.conf, using the most recent + &windows; version listed in the ASL. + + Other workarounds may require my.asl + to be customized. If this file is edited, compile the new + ASL using the following command. Warnings + can usually be ignored, but errors are bugs that will usually prevent ACPI from working correctly. - &prompt.root; iasl -f my.asl + &prompt.root; iasl -f my.asl - Including forces creation of - the AML, even if there are errors during - compilation. Some errors, such as missing return - statements, are automatically worked around by the &os; - interpreter. - - The default output filename for iasl is - DSDT.aml. Load this file instead of - the BIOS's buggy copy, which is still - present in flash memory, by editing - /boot/loader.conf as follows: + Including forces creation of the + AML, even if there are errors during + compilation. Some errors, such as missing return statements, + are automatically worked around by the &os; + interpreter. + + The default output filename for iasl is + DSDT.aml. Load this file instead of the + BIOS's buggy copy, which is still present + in flash memory, by editing + /boot/loader.conf as follows: - acpi_dsdt_load="YES" + acpi_dsdt_load="YES" acpi_dsdt_name="/boot/DSDT.aml" - Be sure to copy DSDT.aml to - /boot, then reboot the system. If this fixes the problem, send a - &man.diff.1; of the old and new ASL to - &a.acpi.name; so that - developers can work around the buggy behavior in + Be sure to copy DSDT.aml to + /boot, then reboot the system. If this + fixes the problem, send a &man.diff.1; of the old and new + ASL to &a.acpi.name; so that developers can + work around the buggy behavior in acpica. @@ -3329,36 +3331,34 @@ acpi_dsdt_name="/boot/DSDT.aml"The ACPI driver has a flexible debugging facility. A set of subsystems and the level of verbosity can be specified. The subsystems to debug are - specified as layers and are broken down into - components (ACPI_ALL_COMPONENTS) - and ACPI hardware support - (ACPI_ALL_DRIVERS). The verbosity of debugging output is - specified as the level and ranges from just report errors - (ACPI_LV_ERROR) to everything - (ACPI_LV_VERBOSE). - The level is a bitmask so - multiple options can be set at once, separated by spaces. In - practice, a serial console should be used to log the output - so it is not lost as the console message buffer flushes. A - full list of the individual layers and levels is found in - &man.acpi.4;. + specified as layers and are broken down into components + (ACPI_ALL_COMPONENTS) and + ACPI hardware support + (ACPI_ALL_DRIVERS). The verbosity of + debugging output is specified as the level and ranges from + just report errors (ACPI_LV_ERROR) to + everything (ACPI_LV_VERBOSE). The level is + a bitmask so multiple options can be set at once, separated by + spaces. In practice, a serial console should be used to log + the output so it is not lost as the console message buffer + flushes. A full list of the individual layers and levels is + found in &man.acpi.4;. Debugging output is not enabled by default. To enable it, add options ACPI_DEBUG to the custom kernel configuration file if ACPI is compiled into the kernel. Add ACPI_DEBUG=1 to - /etc/make.conf to enable it globally. - If a module is used instead of a custom kernel, recompile just the - acpi.ko module as follows: + /etc/make.conf to enable it globally. If + a module is used instead of a custom kernel, recompile just + the acpi.ko module as follows: &prompt.root; cd /sys/modules/acpi/acpi && make clean && make ACPI_DEBUG=1 Copy the compiled acpi.ko to /boot/kernel and add the desired level - and layer to /boot/loader.conf. The entries in this - example enable debug messages for all ACPI - components and - hardware drivers and + and layer to /boot/loader.conf. The + entries in this example enable debug messages for all + ACPI components and hardware drivers and output error messages at the least verbose level: debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS" @@ -3367,10 +3367,10 @@ debug.acpi.level="ACPI_LV_ERROR"If the required information is triggered by a specific event, such as a suspend and then resume, do not modify /boot/loader.conf. Instead, use - sysctl to specify the layer and level after booting - and preparing the system for the specific event. The - variables which can be set using sysctl are named - the same as the tunables in + sysctl to specify the layer and level after + booting and preparing the system for the specific event. The + variables which can be set using sysctl are + named the same as the tunables in /boot/loader.conf. @@ -3378,15 +3378,16 @@ debug.acpi.level="ACPI_LV_ERROR"problems - Once the debugging information is gathered, it can be - sent to &a.acpi.name; so that it can be used by the &os; + Once the debugging information is gathered, it can be sent + to &a.acpi.name; so that it can be used by the &os; ACPI maintainers to identify the root cause of the problem and to develop a solution. - Before submitting debugging information to this mailing list, ensure the latest - BIOS version is installed and, if - available, the embedded controller firmware version. + Before submitting debugging information to this mailing + list, ensure the latest BIOS version is + installed and, if available, the embedded controller + firmware version. When submitting a problem report, include the following @@ -3409,7 +3410,8 @@ debug.acpi.level="ACPI_LV_ERROR" The dmesg output from boot -v with ACPI disabled, - if disabling ACPI helps to fix the problem. + if disabling ACPI helps to fix the + problem. @@ -3419,8 +3421,7 @@ debug.acpi.level="ACPI_LV_ERROR" The URL to a pasted version of the - system's - ASL. Do + system's ASL. Do not send the ASL directly to the list as it can be very large. Generate a copy of the ASL by running this @@ -3454,7 +3455,8 @@ debug.acpi.level="ACPI_LV_ERROR" - The &os; ACPI Mailing List Archives (The &os; ACPI Mailing List Archives + (http://lists.freebsd.org/pipermail/freebsd-acpi/)