invalid opcode, semaphore expired, and several other errors before system crashes

punt · 11-01-2009, 10:36 PM

Hey guys, does anyone know what this means and what I can do to fix it?

FC11, 2.6.30.9-90.fc11.i586

Code:

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel:invalid opcode: 0000 [#1] SMP 

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel:last sysfs file: /sys/devices/virtual/vc/vcsa2/dev

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel:Process kswapd0 (pid: 22, ti=dfa28000 task=dfa20ca0 task.ti=dfa28000)

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel:Stack:

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: 00000002 00000001 c117a740 c12f52a0 c103ba20 c103ba60 c103baa0 c110a600

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: c110a640 c110a6e0 c136f800 c10ebc40 c10ebc60 c10ebc80 c114e2e0 c114e260

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel:Call Trace:

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c048bf17>] ? shrink_list+0x24d/0x4e1

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c048893d>] ? get_dirty_limits+0x1f/0x2e1

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c0423803>] ? set_next_entity+0xa0/0x10c

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c0402286>] ? __switch_to+0x78/0xfb

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c042c374>] ? finish_task_switch+0x8d/0xa7

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c048c3c1>] ? shrink_zone+0x216/0x289

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c048c8dc>] ? kswapd+0x369/0x51b

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c048b14e>] ? isolate_pages_global+0x0/0x19b

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c044065d>] ? autoremove_wake_function+0x0/0x34

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c0422947>] ? complete+0x39/0x43

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c048c573>] ? kswapd+0x0/0x51b

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c048c573>] ? kswapd+0x0/0x51b

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c0440365>] ? kthread+0x4b/0x6f

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c044031a>] ? kthread+0x0/0x6f

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel: [<c0403f87>] ? kernel_thread_helper+0x7/0x10

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel:Code: f6 43 ea 01 75 24 8b 85 78 ff ff ff f6 40 08 40 0f 84 63 03 00 00 89 f0 e8 88 14 01 00 85 c0 0f 84 2d 03 00 00 bf 01 00 00 00 89 <f0> e8 db f0 ff ff 89 85 7c ff ff ff 8b 46 08 85 c0 78 2b 83 bd 

Message from syslogd@server at Nov  1 21:41:58 ...
 kernel:EIP: [<c048b90e>] shrink_page_list+0x1b0/0x56c SS:ESP 0068:dfa29d80

The semaphore timeout period has expired.

timmeke · 11-06-2009, 09:18 AM

Sounds like a problem with swapping of processes between disk and memory.
"invalid opcode" could be interpreted as the kernel trying to perform an invalid instruction on the CPU.
"semaphore timeout" could refer to a problem in communication between processes (semaphores are used for that)

Not sure what causes this behaviour though.
Is it a new install?
Is your distro fit for your platform (ie do you have an i586 platform)?
Have you checked hardware / fedora forums?