서버가 뻗어버렸어요!

커널을 업데이트 했습니다.한6개월전에2.4.19로
근데 12월30일날 뻗는바람에 처음 redhat7.2설치 할때 깔려 있는
2.4.9로 돌려 놓고 쓰고 있었습니다.
서비스 되고 있는중이라 커널 재 컴파일 할 엄두는 못네서
일단 예전 커널로 돌리고 있었습니다.
근데 이놈이 갑자기 오늘 뻗어 버렸습니다.
로그는 아래와 같은데  왜 뻗었는지 이유를 모르겠네요!
그래서 염치 불구 하고 로그를 올립니다.
왜 뻗었는지 이유라도 알아야 치료 할 수 있을 꺼 같아서요!

################/var/log/message#################
Mar 17 14:11:47 panezasp2 kernel: invalid operand: 0000
Mar 17 14:11:47 panezasp2 kernel: Kernel 2.4.9-e.3
Mar 17 14:11:47 panezasp2 kernel: CPU:    0
Mar 17 14:11:47 panezasp2 kernel: EIP:    0010:
[__refile_buffer+0/112]    Not tainted
Mar 17 14:11:47 panezasp2 kernel: EIP:    0010:[<c013da30>]    Not
tainted
Mar 17 14:11:47 panezasp2 kernel: EFLAGS: 00010296
Mar 17 14:11:47 panezasp2 kernel: EIP is at __refile_buffer [kernel] 0x0
Mar 17 14:11:47 panezasp2 kernel: eax: d0a00670   ebx: d4f8a9c0   ecx:
d4f8a9c0   edx: d4f8a9c0
Mar 17 14:11:47 panezasp2 kernel: esi: d0a00670   edi: f66782c0   ebp:
f5d0e000   esp: f07bfdc8
Mar 17 14:11:47 panezasp2 kernel: ds: 0018   es: 0018   ss: 0018
Mar 17 14:11:47 panezasp2 kernel: Process httpd (pid: 13801,
stackpage=f07bf000)
Mar 17 14:11:47 panezasp2 kernel: Stack: c013daaa d4f8a9c0 f8848a01
d4f8a9c0 d0a00670 f66782c0 00000008 00000000
Mar 17 14:11:47 panezasp2 kernel:        00000000 d4f8a9c0 f66782c0
f5d0e094 f5d0e000 e21c7680 d0a00670 f8848ee6
Mar 17 14:11:47 panezasp2 kernel:        e21c7680 d0a00670 00000000
00000000 e21c7680 f07bfe90 c4b07200 f885bf11
Mar 17 14:11:47 panezasp2 kernel: Call Trace: [refile_buffer+10/16]
refile_buffer [kernel] 0xa
Mar 17 14:11:47 panezasp2 kernel: Call Trace: [<c013daaa>] refile_buffer
[kernel] 0xa
Mar 17 14:11:47 panezasp2 kernel:
[eepro100:__insmod_eepro100_O/lib/modules/2.4.9-e.3/kernel/drivers/ne+-
636415/96] do_get_write_access [jbd] 0x191
Mar 17 14:11:47 panezasp2 kernel: [<f8848a01>] do_get_write_access [jbd]
0x191
Mar 17 14:11:47 panezasp2 kernel:
[eepro100:__insmod_eepro100_O/lib/modules/2.4.9-e.3/kernel/drivers/ne+-
635162/96] journal_get_write_access_R5a0a29e6 [jbd] 0x36
Mar 17 14:11:47 panezasp2 kernel: [<f8848ee6>]
journal_get_write_access_R5a0a29e6 [jbd] 0x36
Mar 17 14:11:47 panezasp2 kernel:
[eepro100:__insmod_eepro100_O/lib/modules/2.4.9-e.3/kernel/drivers/ne+-
557295/96] ext3_reserve_inode_write [ext3] 0x31
Mar 17 14:11:47 panezasp2 kernel: [<f885bf11>] ext3_reserve_inode_write
[ext3] 0x31
Mar 17 14:11:47 panezasp2 kernel: [cleanup_rbuf+174/224] cleanup_rbuf
[kernel] 0xae
Mar 17 14:11:47 panezasp2 kernel: [<c01e1a2e>] cleanup_rbuf [kernel] 0xae
Mar 17 14:11:47 panezasp2 kernel:
[eepro100:__insmod_eepro100_O/lib/modules/2.4.9-e.3/kernel/drivers/ne+-
601744/96] .LC12 [jbd] 0x0
Mar 17 14:11:47 panezasp2 kernel: [<f8851170>] .LC12 [jbd] 0x0
Mar 17 14:11:47 panezasp2 kernel:
[eepro100:__insmod_eepro100_O/lib/modules/2.4.9-e.3/kernel/drivers/ne+-
613017/96] __jbd_kmalloc [jbd] 0x27
Mar 17 14:11:47 panezasp2 kernel: [<f884e567>] __jbd_kmalloc [jbd] 0x27
Mar 17 14:11:47 panezasp2 kernel:
[eepro100:__insmod_eepro100_O/lib/modules/2.4.9-e.3/kernel/drivers/ne+-
557144/96] ext3_mark_inode_dirty [ext3] 0x18
Mar 17 14:11:47 panezasp2 kernel: [<f885bfa8>] ext3_mark_inode_dirty
[ext3] 0x18
Mar 17 14:11:47 panezasp2 kernel:
[eepro100:__insmod_eepro100_O/lib/modules/2.4.9-e.3/kernel/drivers/ne+-
556969/96] ext3_dirty_inode [ext3] 0x87
Mar 17 14:11:47 panezasp2 kernel: [<f885c057>] ext3_dirty_inode [ext3]
0x87
Mar 17 14:11:47 panezasp2 kernel: [file_read_actor+112/224]
file_read_actor [kernel] 0x70
Mar 17 14:11:47 panezasp2 kernel: [<c012ab40>] file_read_actor [kernel]
0x70
Mar 17 14:11:47 panezasp2 kernel: [__mark_inode_dirty+42/128]
__mark_inode_dirty [kernel] 0x2a
Mar 17 14:11:47 panezasp2 kernel: [<c014e3fa>] __mark_inode_dirty
[kernel] 0x2a
Mar 17 14:11:47 panezasp2 kernel: [update_atime+74/80] update_atime
[kernel] 0x4a
Mar 17 14:11:47 panezasp2 kernel: [<c014fbea>] update_atime [kernel] 0x4a
Mar 17 14:11:47 panezasp2 kernel: [do_generic_file_read+1425/1440]
do_generic_file_read [kernel] 0x591
Mar 17 14:11:47 panezasp2 kernel: [<c012aac1>] do_generic_file_read
[kernel] 0x591
Mar 17 14:11:47 panezasp2 kernel: [generic_file_new_read+103/128]
generic_file_new_read [kernel] 0x67
Mar 17 14:11:47 panezasp2 kernel: [<c012ac37>] generic_file_new_read
[kernel] 0x67
Mar 17 14:11:47 panezasp2 kernel: [file_read_actor+0/224]
file_read_actor [kernel] 0x0
Mar 17 14:11:47 panezasp2 kernel: [<c012aad0>] file_read_actor [kernel]
0x0
Mar 17 14:11:47 panezasp2 kernel: [generic_file_read+27/32]
generic_file_read [kernel] 0x1b
Mar 17 14:11:47 panezasp2 kernel: [<c012abcb>] generic_file_read
[kernel] 0x1b
Mar 17 14:11:47 panezasp2 kernel: [sys_read+150/256] sys_read [kernel]
0x96
Mar 17 14:11:47 panezasp2 kernel: [<c013b9c6>] sys_read [kernel] 0x96
Mar 17 14:11:47 panezasp2 kernel: [sys_llseek+115/224] sys_llseek
[kernel] 0x73
Mar 17 14:11:47 panezasp2 kernel: [<c013b8c3>] sys_llseek [kernel] 0x73
Mar 17 14:11:47 panezasp2 kernel: [sys_llseek+204/224] sys_llseek
[kernel] 0xcc
Mar 17 14:11:47 panezasp2 kernel: [<c013b91c>] sys_llseek [kernel] 0xcc
Mar 17 14:11:47 panezasp2 kernel: [system_call+51/56] system_call
[kernel] 0x33
Mar 17 14:11:47 panezasp2 kernel: [<c0106f03>] system_call [kernel] 0x33
Mar 17 14:11:47 panezasp2 kernel:
Mar 17 14:11:48 panezasp2 kernel:
Mar 17 14:11:48 panezasp2 kernel: Code: 56 ba 01 00 00 00 53 31 db 83 ec
10 8b 74 24 1c 8b 46 18 a9
Mar 17 14:11:48 panezasp2 kernel:  <0>Kernel panic: not continuing
#####################################################################

그리고 top명령어를 치면
4:07pm  up 170 days, 42 min,  2 users,  load average: 0.05, 0.07, 0.01
63 processes: 62 sleeping, 1 running, 0 zombie, 0 stopped
CPU0 states:  1.0% user,  0.2% system,  0.0% nice, 98.2% idle
CPU1 states:  0.1% user,  0.4% system,  0.0% nice, 99.0% idle
Mem:   903952K av,  894272K used,    9680K free,       0K shrd,   93216K
buff
Swap:  522104K av,  171664K used,  350440K free                  607300K
cached

메모리가 거의 풀로 차 버리는데 이것도 서버가 뻗어버리는 거 하고 문제가 있
나요!