DebuggingACPI

Differences between revisions 4 and 14 (spanning 10 versions)
Revision 4 as of 2007-01-30 01:16:16
Size: 1039
Editor: c-24-21-235-175
Comment: Some clarification about kernel versions
Revision 14 as of 2007-09-04 16:42:36
Size: 1833
Editor: 67
Comment: Changed lspci to lspci -vvnn
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 frequently see 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 9: Line 21:
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. 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.
Line 11: Line 23:
Here's a standard response to use: 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.
Line 13: Line 25:
Thanks for reporting this bug. To make any progress with it, some
more information will be needed. Please add (by commenting on the
bug) to the bug report the output of the following commands:
= Known bugs =
Line 17: Line 27:
 * uname -a
 * sudo lspci -vv
 * sudo lspci -vvn
 * sudo dmidecode
Description of known issues, how to recognise them and stock responses/actions.
Line 22: Line 29:
It would also be helpful if you could try to hibernate/suspend and after that
fails, restart your system and attach /var/log/kern.log.0 as well. Thanks again
for your contribution.
'''Open'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

= Non-bugs =

TBD.

= Also see =

 * DebuggingProcedures

 * DebuggingKernelSuspend

----
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.

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

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