Hi Guys,

of late i have been getting a strange error on my FC6 machine, i really dont know if its hardware or software related. At times the machine just hangs and I usually cold start it. It has started happening frequently of late an dam a bit concerned.

i usualy get the followng error on my terminals just before the mishap;

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: invalid opcode: 0000 [#1]

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: SMP

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: CPU: 0

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: EIP is at symhash+0x1a/0x33

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: eax: d3b20501 ebx: d3b20580 ecx: c6dcee24 edx: ce8ed3e0

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: esi: c0802f20 edi: ce8ed3e0 ebp: c0802f20 esp: c6dced98

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: ds: 007b es: 007b ss: 0068

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: Process yum (pid: 3064, ti=c6dce000 task=cde16760 task.ti=c6dce000)

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: Stack: c04c45ea c6dcee08 c0802f20 c6dcee08 c04cb403 c6dcee14 c6dcee24 c6dcee20

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: c6dcee18 c6dcee24 00000000 c6dcee08 c0802f20 c5fcb484 c6dcee08 c04c5f9d

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: c5fd3d04 00000000 c04c8ee4 00000010 c6dcee08 00000007 000004c2 00000007

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: Call Trace:

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c6dcee08>] 0xc6dcee08

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: DWARF2 unwinder stuck at 0xc6dcee08

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: Leftover inexact backtrace:

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c04cb403>] mls_context_isvalid+0x82/0x18a

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c04c5f9d>] policydb_context_isvalid+0x6a/0x79

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c04c8ee4>] security_compute_sid+0x1a2/0x2e7

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c04bccba>] avc_has_perm+0x4e/0x58

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c04c9082>] security_transition_sid+0x1b/0x1f

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c04bdf22>] may_create+0x9c/0xea

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c0476d70>] permission+0xa2/0xb5

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c047734e>] vfs_create+0x81/0x13b

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c0479e5c>] open_namei+0x17b/0x61f

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c0469c35>] do_filp_open+0x2a/0x3e

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c047e726>] fcntl_setlk64+0x1e9/0x20c

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c04699cd>] get_unused_fd+0xb9/0xc3

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c0469c8f>] do_sys_open+0x46/0xc8

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c0469d4a>] sys_open+0x1c/0x1e

Message from syslogd@localhost at Wed Jun 6 15:57:44 2007 ...
localhost kernel: [<c0404027>] syscall_call+0x7/0xb


Any ideas??

It'd probably help if you posted the output of one of the relevant log files rather than what's posted to the screen. The output of dmesg is usually helpful in these cases, lspci might be handy as well. When you start noticing it happening, type:

dmesg > dmesgsnapshot.txt

This will give you a snapshot of dmesg right when it's starting to crash. That'd probably be the most helpful to diagnose your problem. Once you have that info, you may also want to consider reposting with a more informative thread name .