Enabling Kerneloops in Saucy or T Series

[Brian Murray]

On Wed, Sep 04, 2013 at 10:03:04AM -0400, Joseph Salisbury wrote:
> Hello,
> 
> In prior releases, the kerneloops daemon was enabled early in the
> development cycle to help catch serious kernel bugs.  Before release,
> kerneloops is then disabled again.
>   
> Kerneloops has not been enabled the past couple of releases due to a
> bug[0].  However, that bug does not appear to affect Saucy.  
> 
> Since kerneloops seems to be working in Saucy, do we want to consider
> enabling kerneloops for the rest of the Saucy cycle or wait until the
> next cycle?

These kerneloops reports can already sent be to errors.ubuntu.com[1],
they just may not be easily findable or grouped together.  However, that
is something that Evan and I can work on while we are receiving the
reports.  Additionally, as I mentioned previously just as apport crash
reports do are not sent to Launchpad near the end of the development of
the release but are still sent to errors.ubuntu.com - the same thing can
be done with kerneloops reports.

So I think the question is are the Oops reports, or could they be,
useful to fixing kernel bugs?  If so then we should just enable it.

[1] This is an oops I experienced and sent just by enabling kerneloops
https://errors.ubuntu.com/oops/197aa15a-103a-11e3-826d-e4115b0f8a4

--
Brian Murray