Kernel Oops right after boot

Tue Apr 6 19:57:53 UTC 2010

Hello All,

While trying to fix cd-rom automount issue, I noticed my kernel makes
several Oops'es right after boot. I do not notice any strange behavior
whatsoever. It's just these lines in the /var/log/messages that make
me think something is wrong:

2010-04-06T23:33:59.461793+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:33:59.461891+04:00 frontend1 abrtd: Directory 'kerneloops-1270582439-1' creation detected
2010-04-06T23:34:05.996433+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:34:06.030973+04:00 frontend1 abrtd: Crash is in database already (dup of /var/cache/abrt/kerneloops-1270580900-1)
2010-04-06T23:34:06.031042+04:00 frontend1 abrtd: Deleting crash kerneloops-1270582439-1 (dup of kerneloops-1270580900-1), sending dbus signal
2010-04-06T23:35:59.112531+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:35:59.112582+04:00 frontend1 abrtd: Directory 'kerneloops-1270582559-1' creation detected
2010-04-06T23:35:59.206403+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:35:59.210845+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582559-1, processing
2010-04-06T23:35:59.503073+04:00 frontend1 abrtd: Registered Action plugin 'RunApp'
2010-04-06T23:35:59.503133+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582559-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-04-06T23:36:18.187097+04:00 frontend1 ntpd[1165]: synchronized to 90.156.233.43, stratum 3
2010-04-06T23:36:18.187128+04:00 frontend1 ntpd[1165]: time reset +0.697205 s
2010-04-06T23:36:18.187142+04:00 frontend1 ntpd[1165]: kernel time sync status change 2001
2010-04-06T23:37:59.810046+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:37:59.810164+04:00 frontend1 abrtd: Directory 'kerneloops-1270582679-1' creation detected
2010-04-06T23:37:59.896992+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:37:59.901369+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582679-1, processing
2010-04-06T23:37:59.901413+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582679-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-04-06T23:40:00.018233+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:40:00.018286+04:00 frontend1 abrtd: Directory 'kerneloops-1270582800-1' creation detected
2010-04-06T23:40:00.106862+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:40:00.385884+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582800-1, processing
2010-04-06T23:40:00.385984+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582800-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
2010-04-06T23:41:57.269786+04:00 frontend1 ntpd[1165]: synchronized to 212.192.253.168, stratum 2
2010-04-06T23:42:00.112898+04:00 frontend1 abrt: Kerneloops: Reported 1 kernel oopses to Abrt
2010-04-06T23:42:00.112990+04:00 frontend1 abrtd: Directory 'kerneloops-1270582920-1' creation detected
2010-04-06T23:42:00.204395+04:00 frontend1 abrtd: Getting local universal unique identification
2010-04-06T23:42:00.208968+04:00 frontend1 abrtd: New crash /var/cache/abrt/kerneloops-1270582920-1, processing
2010-04-06T23:42:00.208986+04:00 frontend1 abrtd: RunApp('/var/cache/abrt/kerneloops-1270582920-1','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')

I think it all started when I replaced the motherboard. I mentioned
some time ago in this mailing list that my new motherboard (MSI
P43T-C51) didn't work in Linux with my old video adapter (NVidia 8600GT).
As I couldn't find a solution, I just put an older 7600GS to be able
to use the machine. So I used the system in this configuration as a
MythTV frontend and had no troubles at all (except for the recently
disappeared automount, but I tend to think it's caused by a human
factor perhaps I changed something related to automount, just can't
figure out what it is). 

Originally I was using proprietary NVidia driver. Today I switched
back to Nouveau, but Oopses are still there - no difference at all...

I kindly ask for your help in getting to know what actually
causes these oopses. I'd like to have that fixed, if that is at all
possible.

Dmesg output is attached (hope my message won't be too large).

-- 
Best regards,
 Andrew                    
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg.txt
Url: http://lists.fedoraproject.org/pipermail/users/attachments/20100406/ec3f9926/attachment-0001.txt 