Results 1 to 7 of 7
  1. #1
    Join Date
    Dec 2000
    Posts
    954

    Question Server Crash What error is this?

    hi all,
    suddenly the server crash (load was only 0.26)
    Looking the log files i se this below but do not understand.
    Can somone tell me what erro is this and how to fix?
    --------
    Oct 13 01:22:22 server kernel: Unable to handle kernel paging request at virtual address 402fc7fc
    Oct 13 01:22:22 server kernel: printing eip:
    Oct 13 01:22:22 server kernel: c0218020
    Oct 13 01:22:22 server kernel: *pde = 00000000
    Oct 13 01:22:22 server kernel: Oops: 0000 [#1]
    Oct 13 01:22:22 server kernel: Modules linked in: ipt_owner ipt_REJECT md5 ipv6 3c59x iptable_filter ip_tables loop ext3 jbd
    Oct 13 01:22:22 server kernel: CPU: 0
    Oct 13 01:22:22 server kernel: EIP: 0060:[<c0218020>] Not tainted VLI
    Oct 13 01:22:22 server kernel: EFLAGS: 00010202 (2.6.9)
    Oct 13 01:22:22 server kernel: EIP is at neigh_resolve_output+0xd8/0x17b
    Oct 13 01:22:22 server kernel: eax: 402fc7e0 ebx: 0000000e ecx: 00000000 edx: 00000000
    Oct 13 01:22:22 server kernel: esi: d4839980 edi: f7477780 ebp: f7dac800 esp: f7a57b20
    Oct 13 01:22:22 server kernel: ds: 007b es: 007b ss: 0068
    Oct 13 01:22:22 server kernel: Process named (pid: 2054, threadinfo=f7a56000 task=f756caa0)
    Oct 13 01:22:22 server kernel: Stack: d4839980 f7dac800 00000800 f74777a4 00000000 000000bf d4839980 d4839980
    Oct 13 01:22:22 server kernel: c8e9dd80 00000000 c022f65c d4839980 f881b8e0 00000000 c021c504 00000003
    Oct 13 01:22:22 server kernel: f7a57bc8 00000000 00000001 00000003 00000002 c0231ddc c0231df0 d4839980
    Oct 13 01:22:22 server kernel: Call Trace:
    Oct 13 01:22:22 server kernel: [<c022f65c>] ip_finish_output+0xda/0x1e3
    Oct 13 01:22:22 server kernel: [<c021c504>] nf_iterate+0x71/0xa5
    Oct 13 01:22:22 server kernel: [<c0231ddc>] dst_output+0x0/0x29
    Oct 13 01:22:22 server kernel: [<c0231df0>] dst_output+0x14/0x29
    Oct 13 01:22:22 server kernel: [<c021c850>] nf_hook_slow+0xc4/0xf8
    Oct 13 01:22:22 server kernel: [<c0231ddc>] dst_output+0x0/0x29
    Oct 13 01:22:22 server kernel: [<c023193b>] ip_push_pending_frames+0x406/0x462
    Oct 13 01:22:22 server kernel: [<c0231ddc>] dst_output+0x0/0x29
    Oct 13 01:22:22 server kernel: [<c024e058>] udp_push_pending_frames+0x142/0x26c
    Oct 13 01:22:22 server kernel: [<c024e548>] udp_sendmsg+0x387/0x704
    Oct 13 01:22:22 server kernel: [<c0255d36>] inet_sendmsg+0x4d/0x59
    Oct 13 01:22:22 server kernel: [<c02099f8>] sock_sendmsg+0xe5/0x100
    Oct 13 01:22:22 server kernel: [<c0209b66>] sock_recvmsg+0xfe/0x119
    Oct 13 01:22:22 server kernel: [<c025f3f2>] fib_lookup+0xaa/0xf3
    Oct 13 01:22:22 server kernel: [<c0195c0a>] copy_from_user+0x42/0x70
    Oct 13 01:22:22 server kernel: [<c0114f4b>] autoremove_wake_function+0x0/0x57
    Oct 13 01:22:22 server kernel: [<c020b2f4>] sys_sendmsg+0x1be/0x217
    Oct 13 01:22:22 server kernel: [<c012855e>] unqueue_me+0x43/0x7e
    Oct 13 01:22:22 server kernel: [<c01286df>] futex_wait+0x146/0x19c
    Oct 13 01:22:22 server kernel: [<c013e123>] find_extend_vma+0x29/0x7e
    Oct 13 01:22:22 server kernel: [<c0195c0a>] copy_from_user+0x42/0x70
    Oct 13 01:22:22 server kernel: [<c020b7ab>] sys_socketcall+0x238/0x256
    Oct 13 01:22:22 server kernel: [<c0105a6f>] syscall_call+0x7/0xb
    ----------

    Thanks a lot

  2. #2
    Join Date
    Apr 2004
    Location
    California
    Posts
    132
    Does the server still bootup?

    Also is there any history of other errors on the system?

  3. #3
    Join Date
    May 2005
    Location
    Bay Area
    Posts
    1,211
    There may be a fault in your kernel. Maybe a recompilation might help? Id do some research on the issue.

  4. #4
    Join Date
    Dec 2000
    Posts
    954
    lyzer-- no the server doesnt' bootup. This is the first time this happens..neve see this befor on a server i had.

  5. #5
    Join Date
    Jan 2004
    Location
    York, UK
    Posts
    371
    Looks like a possible hardware error there. Esp with the server not coming back up at all after the crash.

    Could be bad RAM or a fired drive. Could also be most things in between though, it's difficult to guess without more detail.

  6. #6
    Join Date
    Dec 2004
    Location
    Canada
    Posts
    1,097
    I'm not sure what's causing the problem; a stack trace isn't all that useful to anyone other than a kernel develeoper, but it's definitely a major problem. It appears to be crashing inside Netfilter (iptables kernel-mode code), so you might want to try booting into singleuser mode (which I think should work...) and disabling those modules, at least to see if that's the problem. As was mentioned, it's highly likely that you've just got some bad RAM, in which case it would crash randomly all over the place (code-wise, it may not be that common, but it'll occur in different programs, and different portions of the kernel).

    I'd recommend first running memtest86 or some other memory tester against the system. If that passes, try unloading the netfilter modules (not loding them at all, I mean), and then perhaps try upgrading your kernel version. If that doesn't solve it, it's probably some other hardware fault.

  7. #7
    Join Date
    Dec 2000
    Posts
    954
    ok thanks.

    just curiose i also get some strange error from PRM when this happens as below:
    ----------
    Oct 13 11:03:00 server prm(23357): locked subsystem, already running ? (/usr/local/prm/lock.utime is 121 seconds old), aborting
    Oct 13 11:06:00 server prm(23968): cleared stale lock file file.
    ---------
    i not sure if this is related

    Thanks a lot

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •