Greetings,

I've ran into a problem here and though i'd see if anyone knew what may be causing this. It's the second time it's happened this week and I'm at my wits end trying to figure this out.

I'm running redhat 7 with apache 1.2 compiled as a mod.

This is the error that was created in /varlog/messages

-----------------------------------------begin---------------------------------------------

Mar 19 14:00:16 webserver kernel: Code: 0f 0b 87 04 b8 4b 25 c0 68 00 03 00 00 6a 00 57 e8 f1 d5 ff
Mar 19 14:00:22 webserver kernel: kernel BUG at mmap.c:1159!
Mar 19 14:00:22 webserver kernel: invalid operand: 0000
Mar 19 14:00:22 webserver kernel: CPU: 0
Mar 19 14:00:22 webserver kernel: EIP: 0010:[exit_mmap+250/288] Not tainted
Mar 19 14:00:22 webserver kernel: EIP: 0010:[<c012531a>] Not tainted
Mar 19 14:00:22 webserver kernel: EFLAGS: 00010206
Mar 19 14:00:22 webserver kernel: eax: 2d86d000 ebx: 00000000 ecx: 0000005a edx: 000001fa
Mar 19 14:00:22 webserver kernel: esi: c19add70 edi: e51eb080 ebp: f4b9d0c0 esp: ed837ea0
Mar 19 14:00:22 webserver kernel: ds: 0018 es: 0018 ss: 0018
Mar 19 14:00:22 webserver kernel: Process httpd (pid: 17825, stackpage=ed837000)
Mar 19 14:00:22 webserver kernel: Stack: 00000000 bfffb648 bfffb5e8 ed836564 ed836000 e51eb080 ed8360e4 ed836000

Mar 19 14:00:22 webserver kernel: 0000000b c0114b19 e51eb080 e51eb080 c0118d11 e51eb080 c011e1d6 c19af2f0
Mar 19 14:00:22 webserver kernel: f7e0f0c0 ed837f3c 00000282 000045a1 0000000b ed836000 0000000b ed836000
Mar 19 14:00:22 webserver kernel: Call Trace: [mmput+57/96] [do_exit+145/528] [collect_signal+150/224] [do_signal+503/624] [path_release+15/48]
Mar 19 14:00:22 webserver kernel: Call Trace: [<c0114b19>] [<c0118d11>] [<c011e1d6>] [<c0108757>] [<c013aebf>]
Mar 19 14:00:22 webserver kernel: [restore_sigcontext+277/320] [sys_sigreturn+180/224] [signal_return+20/24]
Mar 19 14:00:22 webserver kernel: [<c0107c85>] [<c0107d64>] [<c01088f4>]
Mar 19 14:00:22 webserver kernel:

-----------------------------------------end---------------------------------------------

this causes the box to freeze and i have to do a hard reset. the only thing i can pick out that seems unique (and for that matter human readable) is that httpd could have caused the error.

a bit more sys info:




----------------------------------------begin-------------------------------------

processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(tm) XP 1700+
stepping : 2
cpu MHz : 1466.443
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 2922.90


Linux version 2.4.19 (root@localhost.localdomain) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #2

Apache/1.3.27 Server

total: used: free: . . . . shared: buffers: cached:
Mem: 925966336 206823424 719142912 0 39673856 114081792
Swap: 271310848 0 271310848
MemTotal: 904264 kB
MemFree: 702288 kB
MemShared: 0 kB
Buffers: 38744 kB
Cached: 111408 kB
SwapCached: 0 kB
Active: 103900 kB
Inactive: 68356 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 904264 kB
LowFree: 702288 kB
SwapTotal: 264952 kB
SwapFree: 264952 kB

-----------------------------------------end-------------------------------



if anyones has any ideas, i'm open for suggestion..cause i'm sure out of them.

Well, that error message paste from your messages file simply shows the status of various x86 CPU registers at the time the error occured. (Yeah, I see your using AMD, but AMD copied the Intel instructions set). I'm afraid my knowledge of assembly language and the workings of the kernel are too limited for me to be able to decipher the exact problem.

mmap.c deals with mapping virtual memory, so thats probably a good place to start looking into. I'm sorry I cant be much more help, but this is a little out of my league. Good luck.

is there a memory tester of sorts that I can use to test virtual memory? I'm sure that this is over my head as well, but i guess now is a better time than ever to learn.

I've discussed with several other people and some have mentioned apache settings others have said either swapping or v-mem. What's odd about the whole thing is the server has run fine for over 200 days, and now all of a sudden it's decided to poop out every other day.

Again, any and all suggestions are welcome.

http://memtest86.com/


link copied from post in the same forum, about constant rebooting.