DebuggingACPI

Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2006-12-14 13:05:28 →
Size: 418
Editor: ppp128-80
Comment:
← Revision 3 as of 2006-12-14 13:12:58 → ⇥
Size: 918
Editor: ppp128-80
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:

Here's a standard response to use:

Thanks for reporting this bug. To make any progress with it, some
more information will be needed. Please attach (by commenting on the
bug) to the bug report the output of the following commands:

 * uname -a
 * sudo lspci -vv
 * sudo lspci -vvn
 * sudo dmidecode

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.

ACPI support is tough to get right, so we expect to see frequently problems there. When debugging ACPI problems, ask for the following information:

  • 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 the kernel .

Here's a standard response to use:

Thanks for reporting this bug. To make any progress with it, some more information will be needed. Please attach (by commenting on the bug) to the bug report the output of the following commands:

  • uname -a
  • sudo lspci -vv
  • sudo lspci -vvn
  • sudo dmidecode

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.

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