[prev in list] [next in list] [prev in thread] [next in thread] 

List:       novell
Subject:    RE: EIP in MBNWSA.NSS still here
From:       "Alar Pandis" <Alar.Pandis () mtk ! ut ! ee>
Date:       2003-03-31 9:21:16
[Download RAW message or body]

Hi again!
I found TID 10071071 in KB. As I noticed this NCPIPX.NLM|FinishUpPacket all
the time appear. Yes, I have this parameter set OFF. I try turn it ON.
More thanks,
Alar.

-----Original Message-----
From: Alar Pandis [mailto:Alar.Pandis@mtk.ut.ee] 
Sent: 31. märts 2003. a. 9:20
To: 'novell@netlab1.usu.edu'
Subject: EIP in MBNWSA.NSS still here


Hi again on this subject!
NW5.1SP5, eDir8.62SP1, SYS and SYS1 (mirrored) traditional volumes, VOL5 and
VOL6 NSS volumes. All IBM SCSI disks. Two processors. Two servers in tree,
another NW6SP2. Two NSS disks is in external box.
At night server abended second time with same error and now utilization
constantly 22% and above. First abend was 26.03, but after that all
processes seems to be OK! Also utilization. (Well, obviously, something
isn't.)
Also, Netware Management Portal Abended Thread Count shows 0.
I add latest patches for NSS.
It started to happen some two months ago or so, after months server did work
ok w/o any problems. Just started to happen - I didn't add anything, didn't
remove anything.
Also, in abend log is all the time almost same (NCPIPX.NLM at least):
...
Wait state: 50500F0  (Waiting for work)
	or
Wait state: 5050090  (Wait for interrupt)
Stack: D56B5CE0  (NCPIPX.NLM|FinishUpPacket+B6)
       --D0BF498E  ?
       -D56BB3F0  (NCPIPX.NLM|IPXReplyProceduresVector+0)
...
Here is info from Profiling & Debug Information:
Thread Name Thread ID Thread State Parent NLM Execution Time 
Server 08				D0912700 Delayed SERVER.NLM 47.6 % 
Java_341 Thread-14		CF4FB520 Blocked on Semaphore JAVA.NLM 40.0
% 
Java_341 Thread-24		CF75A120 Yielded CPU JAVA.NLM 7.5 % 
Processor 1: IDLE Thread	D07EA580 Ready to run / running SERVER.NLM
1.4 % 
MercNDSP 20874			B8079120 Blocked on a kernel CV MERCNDSP.NLM
1.1 % 
ListenThd256-10.0.0.2:2805	CBAF0520 Blocked on Semaphore HTTPSTK.NLM
0.7 % 
NDSIMON				CDCD4140 Wait for interrupt NDSIMON.NLM 0.5
% 
Java_619 Storer Main Thread	C30606E0 Blocked on Semaphore JAVA.NLM 0.3 %

Server 24				C68DA440 Waiting for work SERVER.NLM
0.2 % 
httpexpThread28			CBC6C600 Wait for interrupt HTTPSTK.NLM 0.2
% 
httpexpThread29			CBC78640 Delayed HTTPSTK.NLM 0.1 % 

Unfortunately I have no clue why this abend happen.
Any ideas how can I find out source of this problem?
Any help is greately appreciated.
More thanks,
Alar.

Abend 2 on P00: Server-5.00k: Page Fault Processor Exception (Error code
00000000)

Registers:
    CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0010 SS = 0010
    EAX = 00006365 EBX = 65657246 ECX = C694CD60 EDX = C2BEF5A0
    ESI = D0BF498E EDI = 00000000 EBP = D0BF4944 ESP = C694CD44
    EIP = D7ADF4C5 FLAGS = 00010246 
    D7ADF4C5 8B9B7C010000   MOV     EBX,[EBX+0000017C]=?
    EIP in MBNWSA.NSS at code start +000404C5h
    Access Location: 0x656573C2

The violation occurred while processing the following instruction:
D7ADF4C5 8B9B7C010000   MOV     EBX,[EBX+0000017C]
D7ADF4CB 8B4328         MOV     EAX,[EBX+28]
D7ADF4CE 25FEFFFFFF     AND     EAX,FFFFFFFE
D7ADF4D3 0F8434000000   JZ      D7ADF50D
D7ADF4D9 8B4328         MOV     EAX,[EBX+28]
D7ADF4DC 2501000000     AND     EAX,00000001
D7ADF4E1 0F8507000000   JNZ     D7ADF4EE
D7ADF4E7 B81813AED7     MOV     EAX,D7AE1318
D7ADF4EC FF20           JMP     near ptr [EAX]
D7ADF4EE 33C0           XOR     EAX,EAX



Running process: Server 28 Process
Created by: NetWare Application
Thread Owned by NLM: SERVER.NLM
Stack pointer: C694CF88
OS Stack limit: C6945040
Scheduling priority: 67371008
Wait state: 50500F0  (Waiting for work)
Stack: D56B5CE0  (NCPIPX.NLM|FinishUpPacket+B6)
       --D0BF498E  ?
       -D56BB3F0  (NCPIPX.NLM|IPXReplyProceduresVector+0)
...

_______________________________________________
Novell mailing list
Novell@netlab1.usu.edu
http://netlab1.usu.edu/mailman/listinfo/novell

[prev in list] [next in list] [prev in thread] [next in thread]