Re: URGENT! Service process max out, server hang, "Work To Do"onconsole
Massimo Rosen wrote:
> Hi,
>
> KH wrote:
>> It did abend this time, which it didn't yesterday. Below is the first
>> chunk of the abend log.
>>
>> Server RHODAN halted Friday, September 15, 2006 11:03:47.953 am
>> Abend 1 on P00: Server-5.60.05: Bounds Check Processor Exception
>
> Hmm. A bounds check is usually a hardware problem, most likely the CPU
> itself. This also is commonly attributed to CPU overheating.
>
> CU,
> --
Well, it abended again at 9pm tonight. Is there any way to confirm it's
the processor? This is a Dell PowerEdge 4600. I'm not sure Dell will
replace the processor based on an abend.
Server RHODAN halted Friday, September 15, 2006 9:02:25.248 pm
Abend 1 on P00: Server-5.60.05: Page Fault Processor Exception (Error
code 00000000)
Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 00000046 EBX = CA572320 ECX = 004F1910 EDX = 00000040
ESI = CA572320 EDI = C877F500 EBP = C877F500 ESP = C98E4EB8
EIP = 00264F90 FLAGS = 00010046
00264F90 8B5AF8 MOV EBX,[EDX-08]=?
EIP in SERVER.NLM at code start +0005AF10h
Access Location: 0x00000038
The violation occurred while processing the following instruction:
00264F90 8B5AF8 MOV EBX,[EDX-08]
00264F93 83EA08 SUB EDX,00000008
00264F96 85DB TEST EBX,EBX
00264F98 0F841B010000 JZ 002650B9
00264F9E 66F7C3FF0F TEST BX,0FFF
00264FA3 0F8510010000 JNZ 002650B9
00264FA9 F6420401 TEST byte ptr [EDX+04],01
00264FAD 0F841A010000 JZ 002650CD
00264FB3 833DDCEC430000 CMP
[SERVER.NLM|MemoryDebugCount]=00000000,00000000
00264FBA 7514 JNZ 00264FD0
Running process: Server 00:22 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: C98E4F80
OS Stack limit: C98DD040
CPU 0 (Thread C877F500) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 70700E0 Exiting OR terminated
Stack: --00000001 ?
--201F7B60 ?
--201F7B60 ?
--201F7B60 ?
--C98E4ED8 ?
CD5405BD (NSS.NLM|msgFreeObject+3D)
--201F7B60 ?
--201F7B60 ?
--C98E4EF0 ?
CD540B04 (NSS.NLM|MSG_DestroyKey+64)
--201F7B60 ?
--B7E749A0 ?
--00000000 ?
--00000246 ?
C9AC3C1D (LIBC.NLM|RecycleStruct+3D)
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--4346696C ?
--B7E749A0 ?
--C98E4F28 ?
C9A33943 (LIBC.NLM|DisposeOFS+13)
--B7E749A0 ?
--C98E4F3C ?
C9A288EE (LIBC.NLM|kgClose+6E)
--B7E749A0 ?
--CFBD00A0 ?
--0000000C ?
--C98E4F54 ?
C9A28850 (LIBC.NLM|close+C0)
--B7E749A0 ?
--2AB0ADC0 ?
--CFBCE680 ?
--17072298 ?
--CFBCE680 ?
--CFBCE680 ?
--C877F500 ?
--C877F500 ?
--CA572320 ?
--CA572320 ?
00226269 (SERVER.NLM|FreeTCO+49)
--00000040 ?
--C877F500 ?
--CA572320 ?
--CA572320 ?
00224F4E (SERVER.NLM|TcoResumeThreadsInAddressSpace+29A)
--CA572320 ?
--00000046 ?
--00000003 ?
--C877F500 ?
--00000000 ?
--C877F500 ?
--00000000 ?
--C877F500 ?
0022430D (SERVER.NLM|TcoThreadExit+15)
--C877F500 ?
00225F4D (SERVER.NLM|TcoNewSystemThreadEntryPoint+61)
--C877F500 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--C98DD000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
Stack dump exceeded the valid memory limit
Additional Information:
The CPU encountered a problem executing code in SERVER.NLM. The
problem may be in that module or in data passed to that module by a
process owned by SERVER.NLM.
|