abrt / kernel oops issue

[Jiri Moskovcak]

On 11/12/2009 06:50 PM, Dan Williams wrote:
> On Thu, 2009-11-12 at 10:31 -0700, Nathanael D. Noblet wrote:
>> Hello,
>>     I've been running F12/rawhide from a preupgrade from F11 for a couple
>> weeks now. I've just recently noticed the abrt feature. I started
>> submitting the bugs it found in the kerneloops. Which has me wondering
>> couple things.
>>
>>     #1 - I have many many kerneloops, each stacktrace/log snippet seems
>> fairly identical. I assume you would prefer not to get 20 identical abrt
>> submitted bugs? Or should I submit them all?
>>
>>     #2 - When looking at the trace it has the following line(s):
>>
>> Nov 10 09:15:57 iridium kernel: WARNING: at lib/list_debug.c:30
>> __list_add+0x68/0x81() (Tainted: G        W )
>>
>> ...
>>
>> Nov 10 09:15:57 iridium kernel: Pid: 2197, comm: Xorg Tainted: G
>> W  2.6.31.5-127.fc12.x86_64 #1
>>
>>
>> I'm wondering why it is saying it is tainted.. or maybe Tainted: G mean
>> Good?? I don't have any closed source modules loaded as far as I know.
>> Unless Virtualbox is closed source but I didn't think it was. Virtualbox
>> isn't running when this happens, though the module seems to be loaded.
>
> If you have an oops or BUG of any sort, I think that sets the taint flag
> for further oops reports, because after the first one you can't really
> trust that the stacktrace or internal kernel structures aren't
> corrupted.  Most of the time they aren't, but you simply can't trust
> that.  So I'd expect the first one to be untainted, and then subsequent
> oops reports to have the taint flag set.
>
> Of course if you start loading random kernel modules that didn't come
> with the kernel itself, you can also taint the kernel.  If you have
> staging drivers loaded, you'll have the taint_crap flag set because
> staging drivers are crap.
>
> Dan
>
>>
>>     #3 Validity of the bugs it is finding... It calls the following a
>> kerneloops...
>>
>>> Nov 11 16:56:41 iridium gnome-session[2259]: WARNING: Could not parse desktop file /etc/xdg/autostart/network-manager-netbook.desktop: Key file does not have key 'Name'
>>> Nov 11 16:56:41 iridium gnome-session[2259]: WARNING: could not read /etc/xdg/autostart/network-manager-netbook.desktop
>>> Nov 11 16:56:42 iridium kernel: executing set pll
>>> Nov 11 16:56:42 iridium kernel: executing set crtc timing
>>> Nov 11 16:56:42 iridium kernel: [drm] TMDS-15: set mode  25
>>> Nov 11 16:56:42 iridium kernel: executing set pll
>>> Nov 11 16:56:42 iridium kernel: executing set crtc timing
>>> Nov 11 16:56:42 iridium kernel: [drm] TMDS-11: set mode  2f
>>> Nov 11 16:56:42 iridium kernel: fuse init (API version 7.12)
>>> Nov 11 16:56:43 iridium pulseaudio[2406]: pid.c: Daemon already running.
>>> Nov 11 16:56:46 iridium restorecond: Unable to watch (/home/****/public_html/*) No such file or directory
>>
>> do I submit this anyway?
>>
>>
>> Thanks, just rying to do my part without burying you guys in senseless
>> bug reports.
>>
>

ABRT's kerneloops plugin had some problems with false alarms, this 
should be fixed in the next release (this week).

Jirka
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jmoskovc.vcf
Type: text/x-vcard
Size: 126 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20091118/e9739c23/attachment.vcf>