View Full Version : Exact Cause for FC6 Frequent Crash
dmode
26th April 2007, 10:04 AM
Hi,
First of all I am an avid user of fc3 to fc6, I even have a mail server running fc4 perfectly...
I have a prob concerning one of my fc6 box (fully updated)... it always crashes... i get tons of kernel errors from time to time and maybe the cause is my gfx card which is an nvidia tnt2 (i can't use compiz due to some harware limitations, this is ok)... i have installed the latest gfx (livna) drivers too...
I have moved from Gnome, to KDE to XFce 4, but same prob... I really have no clue...
Where should I start? This is the first time that this is happening to me... it crashes without any reason at all...
dmode
26th April 2007, 10:16 AM
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: Oops: 0000 [#1]
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: SMP
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: CPU: 0
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: EIP: 0060:[<c04291cf>] Not tainted VLI
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: EFLAGS: 00210246 (2.6.20-1.2944.fc6 #1)
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: EIP is at __do_proc_dointvec+0x28b/0x2ad
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: eax: 00000001 ebx: 0a62f330 ecx: 00000001 edx: 00000003
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: esi: 0a6309f8 edi: 0045c8d4 ebp: 0a62f330 esp: c4c7cea0
Message from syslogd@db at Thu Apr 26 13:09:49 2007 ...
db kernel: ds: 007b es: 007b ss: 0068
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: Process yum (pid: 3577, ti=c4c7c000 task=d64e2e30 task.ti=c4c7c000)
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: Stack: c04380a9 00000000 00000001 d6cac94c 00000000 d6cac94c 00000000 00000001
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: c4c7cee4 c041c88d 00000000 00000000 00000001 00200282 d6cac80c 00200282
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: 00200282 00200202 0000000a c0618137 ffffffda c0433738 00200202 00200202
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: Call Trace:
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c04380a9>] do_futex+0x217/0xb7d
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c041c88d>] __wake_up+0x32/0x43
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0618137>] _spin_lock_irqsave+0x9/0xd
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0433738>] remove_wait_queue+0x16/0x22
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c04c0a80>] file_has_perm+0x8c/0x94
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0403130>] __switch_to+0x182/0x18e
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0618125>] _spin_unlock_irq+0x5/0x7
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0616aab>] __sched_text_start+0x99b/0xa23
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0534dfd>] read_chan+0x0/0x543
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c041cc31>] task_running_tick+0x1ae/0x237
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0438b2d>] sys_futex+0x11e/0x131
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: [<c0403fe0>] syscall_call+0x7/0xb
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: =======================
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: Code: e8 2f f9 0b 00 85 c0 75 37 0f b6 c2 f6 80 60 f4 6f c0 20 74 06 46 4d 85 ed 75 e3 83 7c 24 1c 00 b8 ea ff ff ff 75 1e 8b 54 24 60 <8b> 02 29 e8 89 02 8b 4c 24 64 31 d2 01 01 11 51 04 31 c0 eb 05
Message from syslogd@db at Thu Apr 26 13:09:50 2007 ...
db kernel: EIP: [<c04291cf>] __do_proc_dointvec+0x28b/0x2ad SS:ESP 0068:c4c7cea0
dmode
27th April 2007, 08:27 AM
anyone... HELP
jbannon
27th April 2007, 08:39 AM
Have you run a memtest?
Have you run an fsck?
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.