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 -vv'
• Output of 'sudo lspci -vvn'
• 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.

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Closed

Non-bugs

TBD.

Also see

• DebuggingProcedures

• DebuggingKernelSuspend

CategoryBugSquad