DebuggingACPI

Differences between revisions 1 and 10 (spanning 9 versions)
⇤ ← Revision 1 as of 2006-12-14 13:00:45 →
Size: 374
Editor: ppp128-80
Comment:
← Revision 10 as of 2007-02-22 01:23:36 → ⇥
Size: 649
Editor: c-24-21-235-175
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: ACPI support is tough to get right, so we expect to frequently see problems there. When debugging ACPI problems, ask for the following information:
Line 3: Line 3:
 * Ask them if their BIOS is up to date.
Line 8: Line 9:

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

ACPI support is tough to get right, so we expect to frequently see problems there. 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.

CategoryBugSquad

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