DebuggingACPI
|
Size: 593
Comment: [ADD] Update BIOS, many problems is BUGS BIOS.
|
Size: 1791
Comment: Added reference to https://wiki.ubuntu.com/DebuggingKernelSuspend
|
| 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: |
| * Pliss update you BIOS. | = 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 10: | Line 22: |
| 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 Edgy is linux-source-2.6.17 and for Feisty it is linux-source-2.6.20. 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''' ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || || TBD. || TBD. || TBD. || '''Closed''' ||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || || TBD. || TBD. || TBD. || = Non-bugs = TBD. = Also see = * DebuggingProcedures * DebuggingKernelSuspend |
ContentsBRTableOfContents |
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.
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
DebuggingACPI (last edited 2011-03-03 18:36:15 by c-98-246-63-231)