Abend
Our server has gone from being virtually bomb proof to abending occasionally.
It always seems to be triggered by one of the XP client machines. Not sure where to start?
This is the abend log:
Server FS411 halted Wednesday, 6 May 2009 8:15:31 am
Abend 1: Server-4.11a: CPU Hog Detected by Timer
Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
EAX = D7F30EEE EBX = 00000000 ECX = 00000006 EDX = B9432174
ESI = F9157E10 EDI = 00000002 EBP = B9432154 ESP = B9432148
EIP = 00000000 FLAGS = 00007082
Running process: Server 11 Process
Created by: SERVER.NLM
Stack pointer: B9432390
Stack limit: B942F640
Scheduling priority: 0
Wait state: 00
Stack: F802AAEE (SERVER.NLM|InternalDiskGetNoReadNoWaitNoAlloc+EF7 F)
--D7F30EEE ?
F80F3372 ?
--B9432178 ?
--00000002 ?
--00000006 ?
--00000002 ?
F80F0F44 ?
--00000002 ?
--00000006 ?
--B9432174 ?
--BDFB08B0 ?
--B9432330 ?
--FFFFFFFF ?
--BECC94FE ?
--00000002 ?
F804FD73 ?
--00000002 ?
--00000006 ?
--00000002 ?
--D5026A84 ?
--00000001 ?
--FFFF2100 ?
--BE516CC0 ?
--BE516C40 ?
-00026A85 (LOADER.EXE|(Data Start)+86F5)
-00026A84 (LOADER.EXE|(Data Start)+86F4)
--48000010 ?
--000046CF (DS.NLM|DSF90B6B60+139C)
--00000000 ?
--B8273CA0 ?
--0000FFFF (DS.NLM|DSF90B6B60+CCCC)
Additional Information:
The NetWare OS detected a problem with the system while executing
a process owned by SERVER.NLM. It may be the source of the problem or
there may have been a memory corruption.
|