Responses

Differences between revisions 13 and 108 (spanning 95 versions)
Revision 13 as of 2012-07-31 01:36:29
Size: 7985
Editor: penalvch
Comment: Streamlined sentence to make it "Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ?"
Revision 108 as of 2015-01-25 17:27:14
Size: 1612
Editor: penalvch
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.
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 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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 comment on which kernel version specifically you tested and 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. <<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, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'. <<BR>><<BR>> Please let us know your results. Thanks in advance. ||

== Please Test Latest Upstream ==

||<tablestyle="background-color: #eee"> Could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 comment on which kernel version specifically you tested and 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. <<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, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'. <<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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 comment on which kernel version specifically you tested and 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. <<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, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'. <<BR>><<BR>> Please let us know your results. Thanks in advance. ||

== Suspend ==

||<tablestyle="background-color: #eee"> 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>> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 comment on which kernel version specifically you tested and 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. <<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, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'. <<BR>><<BR>> Please let us know your results. Thanks in advance. ||

== Hibernate ==

||<tablestyle="background-color: #eee"> 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>> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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 comment on which kernel version specifically you tested and 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. <<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"> 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. ||

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.

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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.XY-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

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.

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