Responses

Differences between revisions 116 and 117
⇤ ← Revision 116 as of 2015-09-14 16:16:44 →
Size: 1706
Editor: penalvch
Comment: 1) Modified structure as many ORs don't test the latest kernel as specifically requested, and have unnecessary Qs regarding kernel to test. 2) bug > issue to be consistent. 3) bug > report.
← Revision 117 as of 2015-09-20 15:17:31 → ⇥
Size: 2536
Editor: penalvch
Comment: Added upstream request response.
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:

= Please upstream =

Please be sure before asking the original reporter to report a bug upstream, the Launchpad report has included enough information for an upstream developer to begin working on it (ex. regressions bisected, latest upstream kernel tested, call trace captured, etc.).

||<tablestyle="background-color: #eee"> The issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list? <<BR>><<BR>> Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive. <<BR>><<BR>>Thank you for your understanding. ||

Please Test Latest Upstream

Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

Please upstream

Please be sure before asking the original reporter to report a bug upstream, the Launchpad report has included enough information for an upstream developer to begin working on it (ex. regressions bisected, latest upstream kernel tested, call trace captured, etc.).

The issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.

Kernel/BugTriage/Responses (last edited 2019-11-04 15:31:40 by penalvch)