Kernel Panic / kernel paging request?

T

TMMM

Verified User
Joined
Oct 29, 2006
Messages
48
I was curious as to if any of this message rings a bell with anybody? Maybee RAM?

At 1:25am last night I received this message and our server locked up:

Jan 16 01:25:02 host kernel: Unable to handle kernel paging request at virtual address 00361fa8
Jan 16 01:25:02 host kernel: printing eip:
Jan 16 01:25:02 host kernel: c0177f86
Jan 16 01:25:02 host kernel: *pde = 3cc79067
Jan 16 01:25:02 host kernel: Oops: 0000 [#1]
Jan 16 01:25:02 host kernel: Modules linked in: md5 ipv6 parport_pc lp parport ipt_TOS ip_conntrack_ftp ip_conntrack_irc ipt_REJECT ipt_limit ipt_multiport ipt_state autofs4 sunrpc ipt_LOG iptable_filter iptable_mangle iptable_nat ip_conntrack ip_tables dm_mirror dm_mod button battery ac ohci_hcd ehci_hcd r8169 8139too mii floppy ext3 jbd
Jan 16 01:25:02 host kernel: CPU: 0
Jan 16 01:25:02 host kernel: EIP: 0060:[<c0177f86>] Not tainted VLI
Jan 16 01:25:02 host kernel: EFLAGS: 00010202 (2.6.9-22.EL)
Jan 16 01:25:02 host kernel: EIP is at __link_path_walk+0xa77/0xd98
Jan 16 01:25:02 host kernel: eax: 00361f80 ebx: 00000000 ecx: f3138e60 edx: f3138e5c
Jan 16 01:25:02 host kernel: esi: f7b4ea0c edi: 01b07b37 ebp: f3138f0c esp: f3138e3c
Jan 16 01:25:03 host crond(pam_unix)[27321]: session closed for user root
Jan 16 01:25:03 host kernel: ds: 007b es: 007b ss: 0068
Jan 16 01:25:03 host kernel: Process dataskq (pid: 27325, threadinfo=f3138000 task=f403d220)
Jan 16 01:25:03 host kernel: Stack: f3138f58 00000000 f3138e90 c018109b 00000001 00000000 f4e0f00a c18c8c80
Jan 16 01:25:03 host kernel: f22e0ef8 01b07b37 00000004 f4e0f006 f3138f0c f3138f0c f4e0f000 f4e0f000
Jan 16 01:25:03 host kernel: 00000000 c01782e8 f7c609b8 c18c8e00 00000000 00000000 00000000 00000001
Jan 16 01:25:03 host kernel: Call Trace:
Jan 16 01:25:03 host kernel: [<c018109b>] dput+0x33/0x423
Jan 16 01:25:03 host kernel: [<c01782e8>] link_path_walk+0x41/0xb9
Jan 16 01:25:03 host kernel: [<c01785e0>] path_lookup+0x104/0x135
Jan 16 01:25:03 host kernel: [<c0178725>] __user_walk+0x21/0x51
Jan 16 01:25:03 host kernel: [<c01729bc>] vfs_stat+0x14/0x3a
Jan 16 01:25:03 host kernel: [<c0172fc5>] sys_stat64+0xf/0x23
Jan 16 01:25:03 host kernel: [<c030f91f>] syscall_call+0x7/0xb
Jan 16 01:25:03 host kernel: Code: e8 46 f4 ff ff 8b 44 24 20 8b 70 20 31 c0 85 f6 0f 95 c0 85 44 24 10 0f 84 6f 02 00 00 8b 86 cc 00 00 00 85 c0 0f 84 61 02 00 00 <83> 78 28 00 0f 84 57 02 00 00 8b 44 24 1c 85 c0 74 03 ff 40 28
Jan 16 01:25:03 host kernel: <0>Fatal exception: panic in 5 seconds
Jan 16 01:25:06 host crond(pam_unix)[27320]: session closed for user root

-----------------------------------------
Yesterday morning I received a similare message aswell as the server locking up:
-----------------------------------------

Jan 15 06:40:47 host kernel: Unable to handle kernel paging request at virtual address 00fe0dc8
Jan 15 06:40:47 host kernel: printing eip:
Jan 15 06:40:47 host kernel: c03074f2
Jan 15 06:40:47 host kernel: *pde = 3b25c067
Jan 15 06:40:47 host kernel: Oops: 0002 [#1]
Jan 15 06:40:47 host kernel: Modules linked in: md5 ipv6 parport_pc lp parport ipt_TOS ip_conntrack_ftp ip_conntrack_irc ipt_REJECT ipt_limit ipt_multiport ipt_state autofs4 sunrpc ipt_LOG iptable_filter iptable_mangle iptable_nat ip_conntrack ip_tables dm_mirror dm_mod button battery ac ohci_hcd ehci_hcd r8169 8139too mii floppy ext3 jbd
Jan 15 06:40:47 host kernel: CPU: 0
Jan 15 06:40:47 host kernel: EIP: 0060:[<c03074f2>] Not tainted VLI
Jan 15 06:40:47 host kernel: EFLAGS: 00010286 (2.6.9-22.EL)
Jan 15 06:40:47 host kernel: EIP is at __unix_remove_socket+0x14/0x4e
Jan 15 06:40:47 host kernel: eax: f7abb948 ebx: f5fe0280 ecx: f5fe0288 edx: 00fe0dc8
Jan 15 06:40:47 host kernel: esi: f5fe0280 edi: f76fccbc ebp: 00000000 esp: f6974f68
Jan 15 06:40:47 host kernel: ds: 007b es: 007b ss: 0068
Jan 15 06:40:47 host kernel: Process estate.cgi (pid: 10298, threadinfo=f6974000 task=f6870600)
Jan 15 06:40:47 host kernel: Stack: 00000000 c030775f f5fe0280 f5fe0280 00000000 f76fcc80 f76fccbc f7a7a780
Jan 15 06:40:47 host kernel: c02aae3a f76fccbc c18c8600 c02ab950 f65b4680 c0168e5a f65b4680 00000000
Jan 15 06:40:47 host kernel: f792ac80 f6974000 c0167763 00000003 09d6cec8 00000000 c030f91f 00000003
Jan 15 06:40:47 host kernel: Call Trace:
Jan 15 06:40:47 host kernel: [<c030775f>] unix_release_sock+0xf/0x19f
Jan 15 06:40:47 host kernel: [<c02aae3a>] sock_release+0x11/0x63
Jan 15 06:40:47 host kernel: [<c02ab950>] sock_close+0x26/0x2a
Jan 15 06:40:47 host kernel: [<c0168e5a>] __fput+0x55/0xee
Jan 15 06:40:47 host kernel: [<c0167763>] filp_close+0x59/0x5f
Jan 15 06:40:47 host kernel: [<c030f91f>] syscall_call+0x7/0xb
Jan 15 06:40:47 host kernel: Code: 89 c2 c1 ea 08 31 c2 81 e2 ff 00 00 00 89 16 89 fa 5b 89 d0 5e 5f c3 53 89 c3 83 78 0c 00 74 43 8d 48 08 8b 40 08 8b 51 04 85 c0 <89> 02 74 03 89 50 04 c7 41 04 00 00 00 00 8b 43 18 48 75 21 68
Jan 15 06:40:47 host kernel: <0>Fatal exception: panic in 5 seconds

--------------------
Please help!
Thank you for reading.
 
Last edited:
If you're using a stock kernel intalled when the OS was installed, or an automated update thereof, then most likely the problem is a hardware issue, very likely bad memory.

Jeff
 
Thank you both for the prompt replys.

Around the time that I posted this question I replaced the RAM and it has been running fine since. I will know for sure as time passes.
 
You must log in or register to reply here.
Back
Top