hello,
given the varity of messages i would say you have a hwardware issue - memory or CPU...
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: ------------[ cut here ]------------
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: kernel BUG at mm/mmap.c:2055!
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: invalid opcode: 0000 [#1]
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: CPU: 0
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: EIP is at exit_mmap+0xc6/0xd5
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: eax: 00000000 ebx: c6b22e20 ecx: cffefc60 edx: c0e481d4
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: esi: 00000000 edi: c7064c80 ebp: c1356aa0 esp: c6b22e10
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: ds: 007b es: 007b ss: 0068
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: Process gdm-binary (pid: 1695, threadinfo=c6b22000 task=c1356aa0)
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: Stack: 00000000 c6b22e1c 00000000 00000044 c076731c c7064c80 c7064ce4 c7064280
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: c0419fb1 24e20042 e788ba49 c0417994 c7064c80 c7064c80 c0465613 cf8ffc14
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: cd09c200 00000000 cfde94e0 c045c74f 00000000 c6b22000 cd09c200 c0000000
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: Call Trace:
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: <c0419fb1> mmput+0x26/0xce <c0417994> arch_pick_mmap_layout+0x70/0xd0
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: <c0465613> flush_old_exec+0x570/0x7a3 <c045c74f> vfs_read+0x110/0x14e
Message from syslogd@server at Sat Jul 8 17:12:02 2006 ...
server kernel: <c0464dbf> kernel_read+0x37/0x41 <c0484d42> load_elf_binary+0x475/0x1601
Message from syslogd@server at Sat Jul 8 17:12:03 2006 ...
server kernel: <c04441ee> __alloc_pages+0x6d/0x29c <c0467b17> deny_write_access+0x37/0x3c
Message from syslogd@server at Sat Jul 8 17:12:03 2006 ...
server kernel: <c04d84df> copy_from_user+0x54/0x80 <c04848cd> load_elf_binary+0x0/0x1601
Message from syslogd@server at Sat Jul 8 17:12:03 2006 ...
server kernel: <c0464b7c> search_binary_handler+0x83/0x1f0 <c046643a> do_execve+0x14b/0x1df
Message from syslogd@server at Sat Jul 8 17:12:03 2006 ...
server kernel: <c0401875> sys_execve+0x30/0x6e <c0402cb3> syscall_call+0x7/0xb
Message from syslogd@server at Sat Jul 8 17:12:03 2006 ...
server kernel: Code: 94 00 00 00 75 06 0f 20 d8 0f 22 d8 89 f8 e8 d7 3f fb ff eb 09 89 f0 e8 ff fe ff ff 89 c6 85 f6 75 f3 83 bf 98 00 00 00 00 74 08 <0f> 0b 07 08 b9 2f 62 c0 83 c4 14 5b 5e 5f c3 55 57 89 d7 56 89
Message from syslogd@server at Sat Jul 8 17:12:03 2006 ...
server kernel: EIP: [<c044d143>] exit_mmap+0xc6/0xd5 SS:ESP 0068:c6b22e10
What does those messages mean?
hello,
given the varity of messages i would say you have a hwardware issue - memory or CPU...
telnet mtrek.game-host.org 1701
I've just tested memory with Memtest86+. It seems OK. But I recently had problem with CPU. It was overheated because of fan stop. It was 90 degrees Celsius = 194 degrees Fahrenheit. How can I test CPU?
Quake is a great test, seriously. Run the demo loop for a while ... like 18-24 hours and see if it survives that. If so you should be okay.
Again crash! I've been running cpubuild script over nignt (http://www-128.ibm.com/developerworks/library/l-hw1/).
I have to replace CPU and run test again.
Last edited by GNEEOT; 07-11-2006 at 10:27 AM.
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: Oops: 0000 [#1]
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: CPU: 0
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: EIP is at free_hot_cold_page+0xb/0x19b
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: eax: 00000212 ebx: 00000212 ecx: c076731c edx: 00000000
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: esi: c06be714 edi: 00000000 ebp: 09d7f000 esp: cd830dc4
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: ds: 007b es: 007b ss: 0068
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: Process wcg_faah_autodo (pid: 2532, threadinfo=cd830000 task=c78f
5550)
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: Stack: 09d7f000 00000212 c0446203 c10a7900 c0446203 c06be6e8 0000
0286 c06be714
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: c10a7900 09d7f000 c18d05fc 053c8067 c044a75b 00000000 ca35
f284 cd830e5c
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: 000a6d3b 00000000 00000001 0a000000 cc20609c c6625d80 c076
731c ffffff58
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: Call Trace:
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c0446203> __page_cache_release+0xca/0xd8 <c0446203> __page_cac
he_release+0xca/0xd8
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c044a75b> unmap_vmas+0x297/0x490 <c044d0dc> exit_mmap+0x5f/0xd
5
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c0419fb1> mmput+0x26/0xce <c041d46d> exit_mm+0x10f/0x11f
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c041e9a5> do_exit+0x1c2/0x768 <c041efb8> sys_exit_group+0x0/0x
d
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c042609a> get_signal_to_deliver+0x3a8/0x3d0 <c0602553> do_page
_fault+0x0/0x5ad
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c04023df> do_notify_resume+0x74/0x5f6 <c044b60c> __handle_mm_f
ault+0x7c5/0x7ed
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c04074f4> convert_fxsr_from_user+0x2b/0xeb <c0602a8c> do_page_
fault+0x539/0x5ad
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: <c0602553> do_page_fault+0x0/0x5ad <c0402d42> work_notifysig+0x
13/0x19
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: Code: 24 18 83 7c 24 18 ff 0f 85 5a fd ff ff 8b 44 24 1c 83 c4 30
5b 5e 5f 5d 83 c0 48 e9 54 df 1b 00 55 57 89 d7 56 53 89 c3 83 ec 18 <8b> 00 c1
e8 1e 8b 04 85 84 db 71 c0 89 44 24 0c f6 43 10 01 74
Message from syslogd@server at Tue Jul 11 12:55:42 2006 ...
server kernel: EIP: [<c04439fa>] free_hot_cold_page+0xb/0x19b SS:ESP 0068:cd830d
c4
What does "server kernel: Oops: 0000 [#1]" mean?
are you running Red Hat,Mandriva,OpenSuSE by anychance??
I had the same problem with my dads PC and no matter what I did I kept getting the same messages. but I in ubuntu it worked great and no annoying messages.
Bookmarks