Responses
Differences between revisions 11 and 121 (spanning 110 versions)
|
Size: 8229
Comment: 1) Asking is better than telling. :) Changed statements from telling to asking and included "please"s. 2) Seperated suspend and hibernate out into 2 different responses.
|
Size: 2454
Comment: Modified wording to be more precise.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| <<TableOfContents>> | = Please Test Latest Upstream = |
| Line 5: | Line 5: |
| == Please Test Latest Development == | ||<tablestyle="background-color: #eee"> 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. <<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. || |
| Line 7: | Line 7: |
| ||<tablestyle="background-color: #eee">Could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p linux <replace-with-bug-number><<BR>><<BR>> Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.<<BR>><<BR>> If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.<<BR>><<BR>> If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.<<BR>><<BR>> If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.<<BR>><<BR>> Please let us know your results. Thanks in advance. || | = Please upstream = |
| Line 9: | Line 9: |
| == Please Test Latest 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.). |
| Line 11: | Line 11: |
| ||<tablestyle="background-color: #eee">Could you please test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.<<BR>><<BR>> If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.<<BR>><<BR>> If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.<<BR>><<BR>> If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.<<BR>><<BR>> Please let us know your results. Thanks in advance. || == Old With No Activity == ||<tablestyle="background-color: #eee">This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .<<BR>><<BR>> If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p linux <replace-with-bug-number><<BR>><<BR>> Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.<<BR>><<BR>> If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.<<BR>><<BR>> If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.<<BR>><<BR>> If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.<<BR>><<BR>> Please let us know your results. Thanks in advance. || == Suspend == ||<tablestyle="background-color: #eee">If not provided, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, could you please run the following command from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p %s %d<<BR>><<BR>> Additionally, could you please try to reproduce this with the upstream mainline kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.<<BR>><<BR>> If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.<<BR>><<BR>> If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.<<BR>><<BR>> If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.<<BR>><<BR>> Please let us know your results. Thanks in advance. || == Hibernate == ||<tablestyle="background-color: #eee">If not provided, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . Please note that one will need to install Ubuntu to test hibernate, as at this time, hibernate does not work in a live environment. If the issue remains, could you please run the following command from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p %s %d<<BR>><<BR>> Additionally, could you please try to reproduce this with the upstream mainline kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.<<BR>><<BR>> If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.<<BR>><<BR>> If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.<<BR>><<BR>> If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.<<BR>><<BR>> Please let us know your results. Thanks in advance. || |
||<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 venue? <<BR>><<BR>> Please provide a direct URL to your newly made report when it becomes available so that it may be tracked. <<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. |
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 venue? |
Kernel/BugTriage/Responses (last edited 2019-11-04 15:31:40 by penalvch)