Responses
|
Size: 2492
Comment: RM'ed vger URL as not all MLs are there.
|
← Revision 144 as of 2019-11-04 15:31:40 ⇥
Size: 11147
Comment: Due to LP#1848445 adj upstream request as folks glance and either miss sending to relevant maintainers, or misinterpret.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| = Please Test Latest Upstream = | ||<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: |
| ||<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, Y, and Z are numbers corresponding to the kernel version. <<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. || | = Introduction = |
| Line 7: | Line 7: |
| = Please upstream = | This page offers kernel bug triagers suggested responses that have been found effective in obtaining requested information. |
| Line 9: | Line 9: |
| 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.). | = Request apport-collect = |
| Line 11: | Line 11: |
| ||<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 e-mail to the mailing list once you have made it so that it may be tracked. It can take a day for the new e-mail to show up in the respective archive. <<BR>><<BR>>Thank you for your understanding. || | Sometimes, folks make reports manually, or against the wrong package initially (e.g. [[https://launchpad.net/ubuntu/+source/linux-meta|linux-meta]], [[https://launchpad.net/ubuntu/+source/linux-hwe|linux-hwe]], [[https://launchpad.net/ubuntu/+source/linux-lts-xenial|linux-lts-xenial]], [[https://launchpad.net/ubuntu/+source/linux-signed|linux-signed]], etc.). Once moved to the [[https://launchpad.net/ubuntu/+source/linux|linux]] package, one may request an apport collection: ||<tablestyle="background-color: #eee"> Thank you for reporting this and helping make Ubuntu better. Could you please boot into a Ubuntu kernel (not third party kernel) and execute the following command only once, as it will automatically gather debugging information, in a terminal: <<BR>> apport-collect BUGNUMBER <<BR>><<BR>> Where BUGNUMBER is replaced with the number of your bug report. || = Request full computer model = For some computers, while computer details may be provided via the Bug Description, the full computer manufacturer and model aren't provided, or the details aren't accurate. Hence, if one is interested in reviewing the computer specifications from the vendor's website, one may request this via: ||<tablestyle="background-color: #eee"> Could you please provide from the the sticker of the computer itself (not from the Bug Description, or the result of a terminal command) the full computer model? || = Request BIOS update = For some issues on some computers, the BIOS being outdated can cause various issues that seem due to Ubuntu itself. For example, hardware intermittently working, hardward not working at all, or what seems software dependent. 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 requirement to have the BIOS updated before upstreaming, one is doing themselves, and upstream a great favor by ensuring it is. As a courtesy to the original reporter, one may provide the direct URL to the latest BIOS update, and note the version number. ||<tablestyle="background-color: #eee"> As per your computer vendor's website, an update for the computer's buggy, insecure, and outdated BIOS is available. Could you please advise on how updating changes the issue following https://help.ubuntu.com/community/BIOSUpdate ? <<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 there is no need to post this on the old BIOS, or create a new report. <<BR>><<BR>> If the problem is still reproducible after updating: <<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 advising on how this improves the situation. <<BR>> 3) Please mark this Status Confirmed. <<BR>><<BR>> However, if this is no longer reproducible, please mark this Status Invalid. <<BR>><<BR>> Thank you for your help. || = Request testing latest mainline kernel = ||<tablestyle="background-color: #eee"> In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following:<<BR>>1) The one to test is in a folder at the very 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 mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible 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 Bug 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 issue is reproducible with the mainline kernel, 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>> In addition, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. <<BR>> <<BR>> Lastly, it is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed. <<BR>> <<BR>> Thank you for your help. || == Request testing drm-tip kernel == If the issue is suspected to be drm related, it is helpful to be provided results while testing it. ||<tablestyle="background-color: #eee"> In order to allow additional upstream developers to examine this issue, at your earliest convenience, could you please test the latest drm-tip kernel? Please keep in mind the following:<<BR>>1) The folder time stamps aren't indicative of when the kernel actually was released upstream.<<BR>>2) 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 this 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. <<BR>><<BR>> However, if you were able to test this kernel, please comment on which kernel version specifically you tested, and the results. If this issue is not reproducible, 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 Bug Description: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-drm-tip <<BR>> <<BR>> If the problem is reproducible, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-drm-tip <<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>> In addition, to keep this issue relevant to upstream, please continue to test newer versions of this kernel as it becomes available. <<BR>> <<BR>> Lastly, it is most helpful that after testing of this kernel is complete, you mark this report Status Confirmed. <<BR>> <<BR>> Thank you for your help. || = Request bisect = ||<tablestyle="background-color: #eee"> The next step is to fully commit bisect from the most recent kernel version that worked, followed immediately by the next kernel version that did not work. This will allow for a direct review of the offending commit for either reverting, or further improvements. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow. <<BR>><<BR>> Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully commit bisecting. <<BR>><<BR>> Also, the kernel release names are irrelevant for the purposes of bisecting. <<BR>><<BR>> It is most helpful that after the bad commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed. <<BR>><<BR>> Thank you for your help. || = Request reverse bisect = ||<tablestyle="background-color: #eee"> The next step is to fully reverse commit bisect from the latest kernel version that did not work followed immediately by the next kernel version that did work. This will allow for a consideration of the fix commit for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow. <<BR>><<BR>> Please note, finding adjacent kernel versions, or providing a commit without testing it and reverting it is not fully reverse commit bisecting. <<BR>><<BR>> Also, the kernel release names are irrelevant for the purposes of bisecting. <<BR>><<BR>> It is most helpful that after the fix commit (not kernel version) has been confirmed via testing, you then mark this report Status Confirmed. <<BR>><<BR>> Thank you for your help. || = Request submit to upstream = It is most helpful to upstream that the original reporter provide all the information necessary 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 at https://wiki.ubuntu.com/Bugs/Upstream/kernel and send TO: the maintainer and CC: the appropriate mailing list? <<BR>><<BR>> This article was written for folks who don't know anything about linux, so it's easy to follow. <<BR>><<BR>> Please provide a direct URL of your email 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 apport-collect
Sometimes, folks make reports manually, or against the wrong package initially (e.g. linux-meta, linux-hwe, linux-lts-xenial, linux-signed, etc.). Once moved to the linux package, one may request an apport collection:
Thank you for reporting this and helping make Ubuntu better. Could you please boot into a Ubuntu kernel (not third party kernel) and execute the following command only once, as it will automatically gather debugging information, in a terminal: |
Request full computer model
For some computers, while computer details may be provided via the Bug Description, the full computer manufacturer and model aren't provided, or the details aren't accurate. Hence, if one is interested in reviewing the computer specifications from the vendor's website, one may request this via:
Could you please provide from the the sticker of the computer itself (not from the Bug Description, or the result of a terminal command) the full computer model? |
Request BIOS update
For some issues on some computers, the BIOS being outdated can cause various issues that seem due to Ubuntu itself. For example, hardware intermittently working, hardward not working at all, or what seems software dependent. 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 requirement to have the BIOS updated before upstreaming, one is doing themselves, and upstream a great favor by ensuring it is. As a courtesy to the original reporter, one may provide the direct URL to the latest BIOS update, and note the version number.
As per your computer vendor's website, an update for the computer's buggy, insecure, and outdated BIOS is available. Could you please advise on how updating changes the issue following https://help.ubuntu.com/community/BIOSUpdate ? |
Request testing latest mainline kernel
In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following: |
Request testing drm-tip kernel
If the issue is suspected to be drm related, it is helpful to be provided results while testing it.
In order to allow additional upstream developers to examine this issue, at your earliest convenience, could you please test the latest drm-tip kernel? Please keep in mind the following: |
Request bisect
The next step is to fully commit bisect from the most recent kernel version that worked, followed immediately by the next kernel version that did not work. This will allow for a direct review of the offending commit for either reverting, or further improvements. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow. |
Request reverse bisect
The next step is to fully reverse commit bisect from the latest kernel version that did not work followed immediately by the next kernel version that did work. This will allow for a consideration of the fix commit for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was written for folks who don't know anything about linux, so it's easy to follow. |
Request submit to upstream
It is most helpful to upstream that the original reporter provide all the information necessary 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 at https://wiki.ubuntu.com/Bugs/Upstream/kernel and send TO: the maintainer and CC: the appropriate mailing list? |
Kernel/BugTriage/Responses (last edited 2019-11-04 15:31:40 by penalvch)