DebuggingACPI

Differences between revisions 1 and 15 (spanning 14 versions)
⇤ ← Revision 1 as of 2006-12-14 13:00:45 →
Size: 374
Editor: ppp128-80
Comment:
← Revision 15 as of 2007-09-12 09:47:45 → ⇥
Size: 1397
Editor: c55DDBF51
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
ACPI support is tough to get right, so we expect to see frequently problems there. When debugging ACPI problems, ask for the following information: ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]||
Line 3: Line 3:
= Introduction =

ACPI support is tough to get right, so we expect to frequently see problems there. See [http://www.acpi.info/ www.acpi.info] and [http://en.wikipedia.org/wiki/Acpi Wikipedia] for background information.

= How to file =

TBD.

= Debugging procedure =

When debugging ACPI problems, ask for the following information:

 * Ask them if their BIOS is up to date.
Line 4: Line 17:
 * Output of 'sudo lspci -vv'
 * Output of 'sudo lspci -vvn'		  * Output of 'sudo lspci -vvnn'
Line 8: Line 20:

Such bugs should be against linux-source-# where number is the specific kernel version. For example, the correct package in Malone for Dapper is linux-source-2.6.15, for Edgy is linux-source-2.6.17, for Feisty it is linux-source-2.6.20 and for Gutsy it is linux-source-2.6.22.

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.

----
CategoryBugSquad

Introduction

ACPI support is tough to get right, so we expect to frequently see problems there. See [http://www.acpi.info/ www.acpi.info] and [http://en.wikipedia.org/wiki/Acpi Wikipedia] for background information.

How to file

TBD.

Debugging procedure

When debugging ACPI problems, ask for the following information:

  • Ask them if their BIOS is up to date.
  • Output of 'uname -a'
  • Output of 'sudo lspci -vvnn'
  • Output of 'sudo dmidecode'
  • Ask the user to try to hibernate/suspend and then restart the system and attach /var/log/kern.log.0

Such bugs should be against linux-source-# where number is the specific kernel version. For example, the correct package in Malone for Dapper is linux-source-2.6.15, for Edgy is linux-source-2.6.17, for Feisty it is linux-source-2.6.20 and for Gutsy it is linux-source-2.6.22.

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.

CategoryBugSquad

DebuggingACPI (last edited 2011-03-03 18:36:15 by c-98-246-63-231)