Ubuntu
kerneloops package

  1. Bug #346303
  2. Comment #3

Comment 3 for bug 346303

Revision history for this message
Steve Beattie (sbeattie) wrote : Re: Kernel oops dialog is inconsistent with kerneloops semantics

A couple of things:

First, a kerneloops update was issued last night (see bug 471137) that effectively neuters kerneloops by default for karmic, so you should stop seeing these once you apply the update. (It can be re-enabled by editing /etc/default/kerneloops)

What kerneloops is doing is monitoring the kernel log looking for output that looks like a kernel oops (hence the name) or was generated by a BUG_ON() or WARN_ON() call. I haven't looked at what typical WARN_ON()s are to verify that they are generally safe to ignore. In the case of the thinkpad_acpi issue in bug 430361, it's a false positive in that the reported message starts with "Warning" which is what kerneloops triggers on to look for an invocation of WARN_ON(). The thinkpad_acpi kernel code that emits it should either be fixed to do a proper WARN_ON() if it's warrented or the string should be changed to "Alert" or something similar.

Thanks!