Responses
|
Size: 1612
Comment: 1) Chg'd vers. # presented to reduce admin. overhead chg'ing it when a new mainline kernel vers. comes out. 2) Adjusted explanation of Tags location to flow chronologically.
|
Size: 1482
Comment: RM'ed redundant VERSION-NUMBER explanation to streamline.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| ||<tablestyle="background-color: #eee"> Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. <<BR>><<BR>> If the test 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 bug 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-VERSION-NUMBER <<BR>> <<BR>> where VERSION-NUMBER is the version number of the kernel you tested exactly shown as: <<BR>> kernel-fixed-upstream-3.XY-rcZ <<BR>><<BR>> Where XY and Z are numbers corresponding to the kernel version. <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. || | ||<tablestyle="background-color: #eee"> Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. <<BR>><<BR>> If the test 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 bug 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-3.XY-rcZ <<BR>> <<BR>> Where XY and Z are numbers corresponding to the kernel version. <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. <<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 (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. |
Kernel/BugTriage/Responses (last edited 2019-11-04 15:31:40 by penalvch)