Responses
Differences between revisions 101 and 104 (spanning 3 versions)
|
Size: 8462
Comment: 3.16 -> 3.17-rc1
|
Size: 1528
Comment: 1) RM'ed responses not used, debugging articles cover what is needed, asks reporters do too much (which end up not doing it) & makes pg easier to maintain. 2) rc3 -> rc4 3) Add earlier release request
|
| 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 (the release names are irrelevant for testing in your release) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. |
| Line 7: | Line 7: |
| ||<tablestyle="background-color: #eee"> Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a 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>> If reproducible, could you also please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-VERSION-NUMBER <<BR>> <<BR>> where VERSION-NUMBER is the version number exactly shown as: <<BR>> kernel-fixed-upstream-3.17-rc1 <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. <<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 == ||<tablestyle="background-color: #eee"> Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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: <<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.17-rc1 <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. <<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. || == 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 images are available from http://cdimage.ubuntu.com/daily-live/current/ .<<BR>><<BR>> If it remains an issue, could you please run the following command in the development release from a 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>> If reproducible, could you also please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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: <<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.17-rc1 <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. <<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. || == Suspend == ||<tablestyle="background-color: #eee"> Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command from a 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>> If reproducible, could you also please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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: <<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.17-rc1 <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. <<BR>> <<BR>> If the mainline kernel does not fix this bug, firstly, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> Secondly, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? <<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. || == Hibernate == ||<tablestyle="background-color: #eee"> Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/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, 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>> If reproducible, could you also please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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: <<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.17-rc1 <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. <<BR>> <<BR>> If the mainline kernel does not fix this bug, firstly, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> Secondly, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelHibernate ? <<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. || |
If they 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: <<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.18-rc3 <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. <<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
||<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 in your release) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.
If they 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:
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.18-rc3
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.
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)