kerneloops

[Brian Murray]

On Fri, Feb 14, 2014 at 05:22:46PM +0000, Barry Drake wrote:
> On 14/02/14 16:32, Phill Whiteside wrote:
> >I've had 14.04 running (lubuntu) since the alpha 1's went out. The
> >only issue I've seen with kernel was the i386 one refusing to boot
> >on a KVM. This has been resolved with the latest kernel release.
> >Apart from that, it has been all been rock solid :)
> 
> Have installed kerneloops ....   The only ongoing issue I have is
> the reported bug in lightdm in which the login screen doesn't find
> the keyboard spasmodically.  Currently I'm using gdm for the time
> being, but it does slow things down a bit.  Other than that, I've
> had very few bugs since I installed pre-alpha right at the beginning
> of the cycle.

Maybe I should clarify what kerneloops does, it looks for OOPS messages
from the running kernel in /var/log/syslog and then prepares a
kerneloops report which is then handed to apport and additional data is
gathered to augment the already gathered data.  From there the "crash"
report can be sent to the Ubuntu Error Tracker and Launchpad.

Here is part of what an OOPS as found in /var/log/syslog looks like:

Feb 13 13:34:15 localhost kernel: [36701.217227] BUG: unable to handle
kernel NULL pointer dereference at           (null)
Feb 13 13:34:15 localhost kernel: [36701.217379] IP:
[<ffffffffa0011012>] my_oops_init+0x12/0x1000 [oops]
Feb 13 13:34:15 localhost kernel: [36701.217491] PGD 0 
Feb 13 13:34:15 localhost kernel: [36701.217525] Oops: 0002 [#1] SMP 
...
Feb 13 13:34:15 localhost kernel: [36701.277919] ---[ end trace
f166bd03a370511f ]---

Without kerneloops enabled you'd like be unaware of these issues, unless
you read your syslog regularly. ;-)

--
Brian Murray
Ubuntu Bug Master