DebuggingACPI

Revision 11 as of 2007-03-06 11:29:01

Clear message

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 Edgy is linux-source-2.6.17 and for Feisty it is linux-source-2.6.20.

Known bugs

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

Open

Bug#

Description

Action

TBD.

TBD.

TBD.

Closed

Bug#

Description

Action

TBD.

TBD.

TBD.

Non-bugs

TBD.

Also see


CategoryBugSquad