Responses

Differences between revisions 1 and 124 (spanning 123 versions)
⇤ ← Revision 1 as of 2010-07-14 16:04:22 →
Size: 43
Editor: pool-173-50-146-9
Comment:
← Revision 124 as of 2016-01-24 00:02:54 → ⇥
Size: 2847
Editor: penalvch
Comment: Due to many recent OR confusion events, re-wrote to ensure they don't confuse folder time stamps with kernel release date chronology.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe Kernel/BugTriage/Responses here. <<Include(Kernel/MenuBar)>>

= Please Test Latest Upstream =

||<tablestyle="background-color: #eee"> In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:<<BR>>1) The one to test is at the very top line at the top of the page (not the daily folder).<<BR>>2) The release names are irrelevant.<<BR>>3) The folder time stamps aren't indicative of when the kernel actually was released upstream.<<BR>>4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .<<BR>><<BR>> If testing on your main install would be inconvenient, one may: <<BR>> 1) Install Ubuntu to a different partition and then test this there. <<BR>> 2) Backup, or clone the primary install. <<BR>><<BR>> 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: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-X.Y-rcZ <<BR>> <<BR>> Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. <<BR>> <<BR>> If the mainline kernel does not fix the issue, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-X.Y-rcZ <<BR>> <<BR>> Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. <<BR>> <<BR>> Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. <<BR>><<BR>> 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.).

||<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 post to the mailing list when it becomes available so that it may be tracked. <<BR>><<BR>>Thank you for your understanding. ||

Please Test Latest Upstream

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

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, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

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 post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.

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