[Ubuntu Wiki] Update of "DebuggingACPI" by brian-murray

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The following page has been changed by brian-murray:
http://wiki.ubuntu.com/DebuggingACPI?action=diff&rev1=30&rev2=31

------------------------------------------------------------------------------
  
  === Trouble Booting ===
  
+ For detailed instructions regarding how to modify boot parameters see DebuggingKernelBoot.
-  {{{sudo cp /boot/grub/menu.lst /boot/grub/menu.lst.bck}}}
- 
-  {{{sudo gedit /boot/grub/menu.lst}}}
  
   1. Try booting with the "acpi=off" kernel parameter
-   * This will disable ACPI support.  If the error is the same with acpi enabled and disabled, this may not be an ACPI issue.
+   * This will disable ACPI support.  If the error is the same with ACPI enabled and disabled, this may not be an ACPI issue.
   1. If "acpi=off" allows the system to boot, try to isolate the ACPI issue with the following boot parameters
    * Try booting with "acpi=ht"
     * This disables all of ACPI except just enough to enable Hyper Threading.  If acpi=off works and acpi=ht fails, then the issue is in the ACPI table parsing code itself, or perhaps the SMP code. 
@@ -35, +33 @@

    * Try booting with "noapic"
     * Disables the IO-APIC for IRQ routing or PCI scanning. 
    * Try booting with "nolapic"
-    * Disables the local APIC
+    * Disables the local APIC.
  
  === Fan Issues ===
  
- These usually relate to the fan spinning too much or too fast.  Another indication may be that the temperature remains high even when the fans are spinning.
+ These usually relate to the fan spinning too often or too fast.  Another indication may be that the temperature remains high even when the fans are spinning.
  
   1. Determine if the system has ACPI-based fan control
    * if /proc/acpi/fan is empty and /proc/acpi/thermal_zone/*/trip_points has no active trip points (those starting with "AC") then there is no ACPI-based fan control on your system
@@ -51, +49 @@

  
   * Output of {{{uname -a}}}
   * Output of {{{sudo lspci -vvnn}}}
-  * Output of {{{sudo dmidecode}}}
+  * Output of {{{sudo dmidecode > dmidecode.txt }}}
   * Try to hibernate/suspend and then restart the system and attach {{{/var/log/kern.log.0}}}
   * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc.
    * {{{cp -r /proc/acpi /tmp}}}
    * {{{tar -cvjf ~/acpi.tar.bz /tmp/acpi}}}
  
- Such bugs should be reported against the appropriate linux-source-2.6.xx package.  For example, the correct package in Malone for Dapper is linux-source-2.6.15, for Feisty it is linux-source-2.6.20 and for Gutsy it is linux-source-2.6.22, for Hardy it is just linux.
+ Such bugs should be reported against the linux package.
  
  Sometimes, everything works except resume (that is, all ACPI functions work, the user can hibernate and restart their computer, etc.). In this case, the DebuggingKernelSuspend procedure can be useful.  UnderstandingSuspend can also provide some useful information.