Responses
|
Size: 8462
Comment: rc1 -> rc6
|
Size: 6366
Comment: 1) + ToC. 2) + intro as ToC presentation w/o was off. 3) + general sect. for upstream. 4) As per LP#1727662 + drm-intel upstream entry.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| <<TableOfContents>> | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 5: | Line 5: |
| == Please Test Latest Development == | = Introduction = |
| 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-rc6 <<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. || | This page offers kernel bug triagers suggested responses that have been found effective in obtaining requested information. |
| Line 9: | Line 9: |
| == Please Test Latest Upstream == | = Request testing of latest upstream kernel = |
| Line 11: | Line 11: |
| ||<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-rc6 <<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. || | ||<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>> Also, you don't need to apport-collect further unless specifically requested to do so. <<BR>> <<BR>> It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed. <<BR>> <<BR>> Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. <<BR>> <<BR>> Thank you for your help. || |
| Line 13: | Line 13: |
| == Old With No Activity == | = Request full computer model = |
| Line 15: | Line 15: |
| ||<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-rc6 <<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. || | For some computers, while the computer manufacturer is provided via the Bug Description, the full computer model isn't provided. Hence, if one is interested in reviewing the computer specifications from the vendor's website, one may request this via the following: ||<tablestyle="background-color: #eee"> Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description, or the result of a terminal command)? || |
| Line 17: | Line 18: |
| == Suspend == | = Request BIOS update = |
| Line 19: | Line 20: |
| ||<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-rc6 <<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. || | For some computers, the BIOS being outdated manifests itself as various issues, both hardware not/intermittently working/working in a degraded state, or what seems software related, but ends up being hardware. Also, many upstream developers request this being updated, despite one having tested the latest mainline kernel, to help them rule out root causes. So, while it's not a hard requirement to have the BIOS updated before upstream, one is doing themselves, and upstream a great favor by ensuring it is. ||<tablestyle="background-color: #eee"> As per your computer vendor's website, an update for your computer's buggy, insecure, and outdated BIOS is available. When you update to this following https://help.ubuntu.com/community/BIOSUpdate how does this improve the situation? <<BR>><<BR>> For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs. <<BR>><<BR>> Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. <<BR>><<BR>> Also, you don't have to create a new report. <<BR>><<BR>> It is most helpful that after the BIOS is updated, if the problem is still reproducible: <<BR>> 1) Please provide the output of the following terminal command (not perform an apport-collect): <<BR>> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date <<BR>> 2) Please make a comment specifically advising on how this improves the situation. <<BR>> 3) Please mark this report Status Confirmed. <<BR>><<BR>> If it's not reproducible, please mark this as Invalid. <<BR>><<BR>> Thank you for your help. || As a courtesy to the original reporter, one may provide the direct URL to the BIOS update, along with the version they would want to update to. |
| Line 21: | Line 24: |
| == Hibernate == | = Request submit to upstream = |
| Line 23: | Line 26: |
| ||<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-rc6 <<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. || | 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.). Also, it is helpful to original reporters to advise them which maintainer(s) to send this to, and which mailing list to CC as it is not always obvious. == DRM Intel == ||<tablestyle="background-color: #eee"> The issue you are reporting is an upstream one. Could you please report this problem to Intel following their instructions via https://01.org/linuxgraphics/documentation/how-report-bugs? <<BR>><<BR>> Please note, pre-built builds of the drm-tip branch are available for Ubuntu from [[https://wiki.ubuntu.com/Kernel/MainlineBuilds]]. <<BR>><<BR>> Please provide a direct URL to your report so that it may be tracked. <<BR>><<BR>>Thank you for your help. || == All others == ||<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 help. || |
Introduction
This page offers kernel bug triagers suggested responses that have been found effective in obtaining requested information.
Request testing of latest upstream kernel
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: |
Request full computer model
For some computers, while the computer manufacturer is provided via the Bug Description, the full computer model isn't provided. Hence, if one is interested in reviewing the computer specifications from the vendor's website, one may request this via the following:
Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description, or the result of a terminal command)? |
Request BIOS update
For some computers, the BIOS being outdated manifests itself as various issues, both hardware not/intermittently working/working in a degraded state, or what seems software related, but ends up being hardware. Also, many upstream developers request this being updated, despite one having tested the latest mainline kernel, to help them rule out root causes. So, while it's not a hard requirement to have the BIOS updated before upstream, one is doing themselves, and upstream a great favor by ensuring it is.
As per your computer vendor's website, an update for your computer's buggy, insecure, and outdated BIOS is available. When you update to this following https://help.ubuntu.com/community/BIOSUpdate how does this improve the situation? |
As a courtesy to the original reporter, one may provide the direct URL to the BIOS update, along with the version they would want to update to.
Request submit to 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.). Also, it is helpful to original reporters to advise them which maintainer(s) to send this to, and which mailing list to CC as it is not always obvious.
DRM Intel
The issue you are reporting is an upstream one. Could you please report this problem to Intel following their instructions via https://01.org/linuxgraphics/documentation/how-report-bugs? |
All others
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? |
Kernel/BugTriage/Responses (last edited 2019-11-04 15:31:40 by penalvch)