[oopscheck] KERNEL Oops on host1.!!!

[WeMasterz5]

Hello...had this in my email today:

IMPORTANT: Do not ignore this email.
Your kernel had an Oops!

This is the result of bad hardware or a kernel bug.
Your system may continue to function as normal, however
there is a good chance bad things are happening right now.
Bad things include: files disappearing, daemons crashing,
complete server crashs, disk corruption and many others.

You might want to check your RAM with memtest86 as this is
usually the cause of the problem.
http://www.memtest86.com/

The Oops is below:
Unable to handle kernel paging request at virtual address 350001f0
printing eip:
c0134f43
*pde = 00000000
Oops: 0000
autofs eepro100 iptable_filter ip_tables mousedev keybdev hid input usb-ohci u
CPU: 1
EIP: 0010:[<c0134f43>] Not tainted
EFLAGS: 00010206

EIP is at find_vma [kernel] 0x33 (2.4.18-14smp)
eax: 350001e8 ebx: bffff000 ecx: 00000000 edx: 35000200
esi: f5a88440 edi: efcc0000 ebp: 00000000 esp: f133fe9c
ds: 0018 es: 0018 ss: 0018
Process ps (pid: 24552, stackpage=f133f000)
Stack: f5a88440 bffff000 c0135129 f5a88440 bffff000 f5a88440 bffffd71 efcc0000
c01322a4 f5a88440 bffffd71 f42ceb2c f42ceac0 f6d9b5e0 00000010 00000000
f5a88440 00000000 efcc0000 efcc0000 c012a3d4 f133e000 f5a88440 bffffd71
Call Trace: [<c0135129>] find_extend_vma [kernel] 0x29 (0xf133fea4))
[<c01322a4>] get_user_pages [kernel] 0x54 (0xf133febc))
[<c012a3d4>] access_process_vm [kernel] 0xd4 (0xf133feec))
[<c016f629>] proc_pid_cmdline [kernel] 0x69 (0xf133ff3c))
[<c016fa57>] proc_info_read [kernel] 0x77 (0xf133ff6c))
[<c014a297>] sys_read [kernel] 0x97 (0xf133ff94))
[<c0149622>] sys_open [kernel] 0xa2 (0xf133ffa8))
[<c0109437>] system_call [kernel] 0x33 (0xf133ffc0))


Code: 39 58 08 76 1a 39 58 04 89 c1 76 07 8b 52 0c 85 d2 75 ea 85



---------------------------------------
anyone seen this before?


Thanks

[rhood]

I would recommend rebooting your server, using the "reboot" command as root.

Should the problem still reoccur after this, try upgrading your kernel. If you are using RedHat, you can use up2date to do this (search this forum to see how). If after that you are STILL getting the error, it is most likely a hardware problem, possibly bad memory.

[dgs]

Just for the record, I got the same email also. Will try the reboot and see what happens.

[equens]

I got the same email also!!

What´s happening!

[beekeeper]

rhood,

Originally posted by rhood
I would recommend rebooting your server, using the "reboot" command as root.

I have a similar problem.

Is a (graceful) reboot from the WHM interface the same or would this need to be done using SSH?

Thanx

[rhood]

It should be the same, but don't quote me on that. We basically had the same issue, and a simple reboot fixed it -- that was over a month ago, and not a single kernel panic since.

We have since upgraded the kernel on that machine as well, and again the issue has not reoccured.