The Linux/ACPI community makes active use of bugzilla. http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
Note that this database is for kernel.org kernels only.
If an issue is specific to a distribution, it should be filed in their database. If a sighting appears in both, please cross-reference it using a complete URL.
For either kernel.org or Linux distributor bugzilla, cc: email@example.com on bug reports involving Linux ACPI. You can subscribe to this list to see all ACPI bugzilla updates: https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
Note that this list is intended for bugzilla machine-generated messages only.
If the distribution bug report is private, due to being on pre-production hardware and you want Intel's Linux ACPI team to know about it, then cc: firstname.lastname@example.org
Sometimes you'll see check-in comments, including reference to small bugzilla numbers, such as BZ 123. These refer to a bugzilla database inside Intel, where ACPICA issues are tracked that don't apply directly to the Linux kernel and thus would not fit within the charter of bugzilla.kernel.org.
While discussion-oriented issues are best dealt with on the list, bugzilla has two useful properties:
- you can attach a whole bunch of stuff there without irritating everybody on the list, including items > 100KB.
- bugzilla never forgets, so your issue will not get lost in the shuffle of e-mail overload.
Sometimes it works well to file the supporting debug output for your issue in bugzilla, and then refer to it on the email@example.com list.
Please be sure to answer these questions when you submit the bug, so they don't have to be asked later:
- Exactly what kernel version does this bug appear in?
- Does it still appear in the latest version?
- Is this a new problem (a regression) or has this problem always existed in every version of Linux tested?
- If this is a regression, what is the latest version of the kernel.org kernel where it does not happen? If you have a git tree, can you, using git-bisect, isolate the regression to a particular commit?
- For the latest working, and for the failing kernel, please _attach_ (do not paste) the complete output from dmesg -s64000 or serial console capture with "debug" on cmdline, if possible.
- If it is an interrupt-related problem, please paste a copy of /proc/interrupts showing, if possible, both the success and failure case. Also, include the full output from lspci -vv.
- Please attach the complete, unprocessed output from acpidump. acpidump is available in /usr/sbin, or in the latest PMtools here: http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
Note that acpidump is a BIOS image. It will not change with different kernel parameters. However, it will change when you install a different version of the BIOS.
- If this turns out to be a platform-specific issue, where we may have to blacklist the machine to enable a workaround, please include the output from dmidecode.