DebuggingACPI
Differences between revisions 3 and 7 (spanning 4 versions)
|
Size: 918
Comment:
|
Size: 566
Comment: [Update] Change response of page debuggingACPI Bugs/Responses
|
| 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 9: | Line 9: |
| 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. |
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. ---- 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:
- 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.
DebuggingACPI (last edited 2011-03-03 18:36:15 by c-98-246-63-231)