← Back to team overview

ubuntu-bugcontrol team mailing list archive

Inquiry on Improving https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Reporting_Bugs_Upstream

 

Ubuntu Bug Control / Ubuntu Kernel Team,

Hello everyone. I wanted to inquire about improving https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Reporting_Bugs_Upstream . What I have noticed in my triaging linux package bugs is that the high majority of original reporters who are steered to this article when asked to upstream their bug, do not follow the directions at all. In turn, their bugs are promptly ignored, and by kindness/busy'ness of the maintainer/submaintainer/community developers, not closed or flagged REJECTED INSUFFICIENT_DATA.

What seems best is something to the following:

<START>

Thank you for following this. Firstly, please do not report your bug upstream unless you have followed the below mentioned format created by kernel.org developers. Failure to follow these directions exactly as shown below, may likely result in your bug being promptly ignored by the kernel maintainer or submaintainer who could fix your problem, or the report being be closed as [[https://bugzilla.kernel.org/page.cgi?id=faq.html|REJECTED INSUFFICIENT_DATA]].

||<tablestyle="background-color: #eee"> <<BR>> [1.] One line summary of the problem: <<BR>> Paste the downstream bug title. <<BR>> <<BR>> [2.] Full description of the problem/report: <<BR>> Paste the Bug Description. <<BR>> <<BR>> [3.] Keywords (i.e., modules, networking, kernel): <<BR>> [4.] Kernel version (from /proc/version): <<BR>> [5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) <<BR>> If you have a kernel oops, one may consult http://www.kernel.org/doc/Documentation/oops-tracing.txt . <<BR>> [6.] A small shell script or example program which triggers the problem (if possible) <<BR>> [7.] Environment <<BR>> lsb_release -rd <<BR>> <<BR>> [7.1.] Software (add the output of the ver_linux script here) <<BR>> For Ubuntu, this is found in the directory: <<BR>> /usr/src/linux-headers-<VERSION>/scripts <<BR>> <<BR>> where <VERSION> is the version of the kernel you are using, found in the directory /usr/src. You may run the script via a terminal: <<BR>> sh ver_linux <<BR>> <<BR>> [7.2.] Processor information (from /proc/cpuinfo): <<BR>> [7.3.] Module information (from /proc/modules): <<BR>> [7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) <<BR>> [7.5.] PCI information ('lspci -vvv' as root) <<BR>> [7.6.] SCSI information (from /proc/scsi/scsi) <<BR>> [7.7.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant): <<BR>> List the output of /proc. <<BR>> <<BR>> [X.] Other notes, patches, fixes, workarounds: <<BR>> Be 100% certain you have included all relevant comment information not included in the Bug Description and a kernel developer should review. They are very busy, and do not need to dive through downstream bug reports to find something that should have been provided when the bug was first filed. If you are unsure about anything asked for, or intend on not following this format, please do not file a report. Instead, continue to ask questions in Launchpad and of the Ubuntu community until all issues are cleared up. ||

Note the above format was taken directly from [[http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html]].

It is often the case that once a bug with the above format is escalated upstream, there is a quick resolution through the help and support of the mainline kernel community. Bug reports in Launchpad can also be set up to monitor bugs reported in other bug tracking systems. Once you have collected the above information, the following steps will help you report your bug upstream and monitor it in Launchpad.

1. Go to http://bugzilla.kernel.org

2. ....

<END>

What do you think?

--
Christopher M. Penalver
E-Mail: christopher.penalver@xxxxxxx
MCSE:Security, MCSA, MCDST, MCP, Security+, Network+, A+, NSSP

This E-Mail was sent via a laptop using Xubuntu, Linux for human beings.
www.xubuntu.org
http://www.launchpad.net/~penalvch
Acer Aspire 5750-9668 Xubuntu 12.04


Follow ups