[Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists)

[Josh Boyer]

On Wed, Jul 8, 2015 at 2:49 PM, Steven Rostedt <rostedt at goodmis.org> wrote:
> On Wed, 8 Jul 2015 07:43:25 -0400
> Josh Boyer <jwboyer at fedoraproject.org> wrote:
>
>> In order to track this well, you need data from users.  And therein
>> lies one of the problems.  The majority of users don't use kernel.org
>> kernels.  They use distro kernels.  The distros have data and tools to
>> help track bugs and regressions, but upstream is somewhat loathe to
>> look at anything that starts with b and ends with zilla.  Why?
>> Because the data coming from users is often utterly junk.  You get a
>> kernel splat and a "I don't know why this happened."  And frankly, I
>> don't expect them to know why it happened either.  Particularly when
>> you have subsystems that are using WARN_ON as a fixme comment and
>> sprinkling them all over the damn place.
>>
>
> Just a note. I hate the use of WARN_ON()s in this case. I bitch quite
> loudly when I stumble across them (and I do often), because my ktest
> scripts I use to test my own patches will fail if a WARN_ON() is
> triggered.
>
> At least if my test boxes have the hardware that does this, it wont
> last long, as I'm pretty good at bitching ;-)

Are you test boxes headless?  Because i915 is littered with WARN and
WARN_ON, to the point where we carry a patch in Fedora to quiet most
of the state machine related ones.  If you look at retrace and filter
out all the proprietary oopses, i915 is always most of the top 10
kernel issues Fedora sees.

https://retrace.fedoraproject.org/faf/problems/?component_names=&associate=__None&daterange=2015-06-24%3A2015-07-08&exclude_taintflags=7&exclude_taintflags=9&exclude_taintflags=5&bug_filter=None&function_names=&binary_names=&source_file_names=&since_version=&since_release=&to_version=&to_release=#

josh