Redid /Include so all of the upstream procedure is captured.
Added source URL for page in # comment as FYI.
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|# The page contents are sourced from https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_upstream_kernel_bugs|
- If your downstream bug report on Launchpad has been marked Triaged, and a Ubuntu community member asked you to read this, thank you for doing so! By reading and following this completely, you are maximizing the speed with which your bug will be fixed. Please take care to read every step carefully.
First step: Prepare the Kernel.org format information
Note the below Kernel.org format was taken directly from upstream.
Please ensure you follow the below format word for word. Just because you tested the latest mainline kernel, may have bisected a kernel regression, or others say they are experiencing the same problem, doesn't mean you should omit anything. Providing this information is vital for a developer to fix your problem, and to maximize the chance of your bug being addressed.
Please take care that when you provide the below information, check that you are booted into the newest available upstream mainline kernel only. Folks have had their bug marked Triaged, sent their e-mail, but had a newer kernel release come out without them realizing this. Hence, if upstream didn't ignore your report altogether, they will ask you to test this in the newest release that just came out and you didn't check for. Failure to do this may have negative unintended consequences. The Ubuntu kernel is the Ubuntu Community's responsibility, the upstream mainline kernel is the Kernel.org Community's responsibility, of which Ubuntu is a part of.
For input problems only
For reports that would normally be sent to the linux-input mailing list, as requested by the maintainer, please do not send any of the information from section [7.] through [7.7] below.
Second step: Prepare your email to be sent
Now that you have prepared the Kernel.org format information, the next step is formating your email correctly. Specifically:
When sending an email, do so in plain text, not html. Otherwise, it will be flagged as SPAM, and silently discarded without notification to you. For more on this and other reasons your post would be flagged as SPAM, please see here.
- Do not send attachments. Instead, post all information in the body of your e-mail.
Third step: With the Kernel.org format send to appropriate maintainers
Reporting Graphics card driver bugs
- The following graphics card driver bugs are submitted to the respective bug tracker below:
Ensure you have tested drm-intel-nightly. The Ubuntu Kernel team has made this available from here.
While booted into drm-intel-nightly capture dmesg after booting with the drm.debug=14 kernel boot parameter.
After the above is collected, report it to the email@example.com mailing list.
All other drivers send an E-Mail TO: the maintainers and CC: the maintainer mailing list
Please ensure you send your email TO: all maintainers of the driver in the TO: field, and put the mailing list in the CC: field. A list of both may be found here. The 'M:' is the Maintainer, and the 'L:' is the mailing list. If no list is specified, send an e-mail TO: the maintainers of the relevant driver.
- If this is a regression, also put the submitter of the regression commit in the TO: field.
If the author of the driver (which may or may not be the current maintainer) appears still active in development, or the driver isn't listed, one would want to put the author in the TO: field. They may be found via a terminal:
modinfo DRIVERWhere DRIVER is the name of the kernel driver.
Please ensure you post in your Launchpad report a URL of your e-mail from the mailing list found from the mailing list archives. It can take a few hours to days for the e-mail to show up to the respective archive.
* Please note that for non-WiFi USB bugs, the USB maintainer(s) do not want anyone to create a Bugzilla report. For more on this, please see this upstream report comment. If you do open an upstream report anyways, it will be immediately closed, and may cause negative unintended consequences.
Fourth step: No response from maintainers
If no response to your email has been received within a week, and the issue is still reproducible with the latest mainline kernel available, then if the issue is related to:
Intel graphics driver bugs - Please report to https://01.org/linuxgraphics/documentation/how-report-bugs.
- All others - You would want to send a follow up e-mail to the mailing list with the updated kernel testing results, and relevant verbose debugging information.
Negative unintended consequences
- If you contact upstream, please follow the Kernel.org format created by Kernel.org developers. Failure to follow these directions exactly as shown may have the following negative unintended consequences:
- May likely result in your bug requiring upstream developers to ask unnecessary follow up questions that should have been provided upfront.
- May likely result in your bug being promptly ignored by the kernel maintainer, sub-maintainer, or community developer(s) responsible to fix your kernel bug.
May create friction between you, the Ubuntu Community, and the kernel.org developers, which is not very Ubuntu.