Ubuntu
kerneloops package

Generates two crash reports for the same oops

Bug #429000 reported by Matt Zimmerman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kerneloops (Ubuntu)
Fix Released
High
James Westby
Ubuntu karmic-alpha-6

Bug Description

Binary package hint: kerneloops

I'm not sure if this has the same root cause as bug 345483, so i'm reporting it separately.

I just had an oops occur, and after discovering that kerneloops wasn't running (bug 428997), I started it. The result was that it generated three crash reports in /var/crash: one was for an older oops which occurred several days earlier, and two were for the one I had just noticed today.

I will attach the two .crash files, which contain identical oops text but slightly different timestamps.

Perhaps one was found in dmesg, and the other in syslog?

ProblemType: Bug
Architecture: i386
Date: Sun Sep 13 11:22:19 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: kerneloops (not installed)
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SourcePackage: kerneloops
Tags: ubuntu-unr
Uname: Linux 2.6.31-10-generic i686

Related branches

lp:ubuntu/karmic/kerneloops
Revision history for this message
Matt Zimmerman (mdz) wrote :
Revision history for this message
Matt Zimmerman (mdz) wrote :
Revision history for this message
James Westby (james-w) wrote :

Your analysis seems to be spot on. Without looking deeper I'm
not sure why they differ at the bottom, but that's kind of irrelevant.

I think the best thing to do is just not look at dmesg at all, so that
we can't get duplicates when they differ like this.

Marking for upload today, so that we can have this turned on by
default without a flood of duplicates.

Thanks,

James

Changed in kerneloops (Ubuntu):
importance: Undecided → High
assignee: nobody → James Westby (james-w)
status: New → Triaged
milestone: none → karmic-alpha-6
Revision history for this message
James Westby (james-w) wrote :

I mean *only* scan dmesg.

However, that means that we can't pick up problems that were logged
but that were not caught by kerneloops.

I think the threat of duplicates means we should do that for now, but
thinking about ways to get more robust duplicate detection across
sources would be good.

Thanks,

James

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kerneloops - 0.12+git20090217-1ubuntu3

---------------
kerneloops (0.12+git20090217-1ubuntu3) karmic; urgency=low

  * Install kerneloops.conf in the kerneloops-daemon package. Thanks
    Matt Zimmerman. (LP: #428891)
  * Don't scan the log file, just rely on dmesg for now to avoid a flood
    of duplicate reports. Thanks Matt Zimmerman. (LP: #429000)

 -- James Westby <email address hidden> Mon, 14 Sep 2009 16:16:49 +0100

Changed in kerneloops (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.