Enabling Kerneloops in Saucy or T Series

James M Leddy james.leddy at canonical.com
Wed Sep 4 17:49:29 UTC 2013

On 09/04/2013 12:54 PM, Joseph Salisbury wrote:
> On 09/04/2013 12:12 PM, Chris J Arges wrote:
>> http://www.kerneloops.org/ seems to be up and running and receiving reports.
>> --chris
>> On 09/04/2013 09:03 AM, 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?
>>> Thanks,
>>> Joe
>>> [0] https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1026251
> There's been a thread going on LKML[0] about http://oops.kernel.org/ . 
> The original kerneloops.org site was down for a while after the
> kernel.org break in.  The project has since been moved over from Arjen
> to Anton Arapov of Redhat.  We might also consider submitting the oops
> data upstream.  However, I'm not sure if we would need to change the way
> we used to submit the data.  We could contact Anton thought and work it out.

Arjan's version used to have a flag that was sort of a "forward report
upstream" flag. This may come in handy if we were to run our own
instance. Maybe we can integrate it into the work that's already going
on with whoopsie-daisy or something else.

More information about the kernel-team mailing list