cav23 Absent Member.
Absent Member.
1036 views

Mulitple abends

I have a NetWare 6.5 SP8 server that randomly crashes without any reason. I have opened an incident with Novell Support however they have not been very responsive. I'm looking to this group for suggestions/recommendations in case someone on this list has seen these errors. Below you will find the last 3 abends. Please review and let me know your thoughts.

Thanks

Chris

-----------------------------------------------------------------------------------------------
Abend 1
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08

Server NOVELSRV01 halted Monday, March 14, 2011 1:30:33.105 am
Abend 1 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000002)

Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 00000000 EBX = 00000000 ECX = 00000000 EDX = 00000000
ESI = 00000000 EDI = 08F02C64 EBP = 004C5EDC ESP = 8A293F2C
EIP = 0036BC36 FLAGS = 00010202
0036BC36 895E0C MOV [ESI+0C]=?, EBX
EIP in SERVER.NLM at code start +00163096h
Access Location: 0x0000000C

The violation occurred while processing the following instruction:
0036BC36 895E0C MOV [ESI+0C], EBX
0036BC39 897310 MOV [EBX+10], ESI
0036BC3C E8F28BCAFF CALL LOADER.NLM|Disable
0036BC41 BEB45C4400 MOV ESI, 00445CB4
0036BC46 897720 MOV [EDI+20], ESI
0036BC49 8B5E24 MOV EBX, [ESI+24]
0036BC4C 895F24 MOV [EDI+24], EBX
0036BC4F 897E24 MOV [ESI+24], EDI
0036BC52 897B20 MOV [EBX+20], EDI
0036BC55 8B473C MOV EAX, [EDI+3C]



Running process: Server 18 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8A293F3C
OS Stack limit: 8A28C000
CPU 0 (Thread 8A2955C0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work

------------------------------------------------------------------------------------------------
Abend 2
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08

Server NOVELSRV01 halted Monday, March 28, 2011 12:44:25.093 am
Abend 1 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000002)

Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 00000000 EBX = 04919C64 ECX = 00000000 EDX = 00000000
ESI = 00000000 EDI = 7D99752C EBP = 004C949C ESP = 89705F4C
EIP = 0036F1F6 FLAGS = 00010202
0036F1F6 895E0C MOV [ESI+0C]=?, EBX
EIP in SERVER.NLM at code start +00163096h
Access Location: 0x0000000C

The violation occurred while processing the following instruction:
0036F1F6 895E0C MOV [ESI+0C], EBX
0036F1F9 897310 MOV [EBX+10], ESI
0036F1FC E83256CAFF CALL LOADER.NLM|Disable
0036F201 BE74924400 MOV ESI, 00449274
0036F206 897720 MOV [EDI+20], ESI
0036F209 8B5E24 MOV EBX, [ESI+24]
0036F20C 895F24 MOV [EDI+24], EBX
0036F20F 897E24 MOV [ESI+24], EDI
0036F212 897B20 MOV [EBX+20], EDI
0036F215 8B473C MOV EAX, [EDI+3C]



Running process: Server 2 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 89705F5C
OS Stack limit: 896FE020
CPU 0 (Thread 8A0163A0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: 00371A9D (SERVER.NLM|CacheUpdateProcedure+D6)

------------------------------------------------------------------------------------------------
Abend 3
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08

Server NOVELSRV01 halted Monday, March 28, 2011 11:11:14.716 am
Abend 1 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000002)

Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 00000000 EBX = 00000000 ECX = 00000000 EDX = 00000000
ESI = 00000000 EDI = 7DD5EC64 EBP = 004C18BC ESP = 8A01EF2C
EIP = 00367616 FLAGS = 00010202
00367616 895E0C MOV [ESI+0C]=?, EBX
EIP in SERVER.NLM at code start +00163096h
Access Location: 0x0000000C

The violation occurred while processing the following instruction:
00367616 895E0C MOV [ESI+0C], EBX
00367619 897310 MOV [EBX+10], ESI
0036761C E812D2CAFF CALL LOADER.NLM|Disable
00367621 BE94164400 MOV ESI, 00441694
00367626 897720 MOV [EDI+20], ESI
00367629 8B5E24 MOV EBX, [ESI+24]
0036762C 895F24 MOV [EDI+24], EBX
0036762F 897E24 MOV [ESI+24], EDI
00367632 897B20 MOV [EBX+20], EDI
00367635 8B473C MOV EAX, [EDI+3C]



Running process: Server 3 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8A01EF3C
OS Stack limit: 8A017000
CPU 0 (Thread 8A0244A0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Labels (2)
0 Likes
4 Replies
ataubman Absent Member.
Absent Member.

Re: Mulitple abends

The 3 abends are all the same, and seem to be in server.nlm, so you'll just have to keep the pressure on NTS until they get the coredump analysed. You could post the whole entry from any one of those for more comment here.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
cav23 Absent Member.
Absent Member.

Re: Mulitple abends

Thanks for the reply. Here is a copy of the last abend.

Chris
-------------------------------------------------------------------------------------------------------------------------------------------------------

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08

Server MBSDATA halted Monday, March 28, 2011 11:11:14.716 am
Abend 1 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000002)

Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 00000000 EBX = 00000000 ECX = 00000000 EDX = 00000000
ESI = 00000000 EDI = 7DD5EC64 EBP = 004C18BC ESP = 8A01EF2C
EIP = 00367616 FLAGS = 00010202
00367616 895E0C MOV [ESI+0C]=?, EBX
EIP in SERVER.NLM at code start +00163096h
Access Location: 0x0000000C

The violation occurred while processing the following instruction:
00367616 895E0C MOV [ESI+0C], EBX
00367619 897310 MOV [EBX+10], ESI
0036761C E812D2CAFF CALL LOADER.NLM|Disable
00367621 BE94164400 MOV ESI, 00441694
00367626 897720 MOV [EDI+20], ESI
00367629 8B5E24 MOV EBX, [ESI+24]
0036762C 895F24 MOV [EDI+24], EBX
0036762F 897E24 MOV [ESI+24], EDI
00367632 897B20 MOV [EBX+20], EDI
00367635 8B473C MOV EAX, [EDI+3C]



Running process: Server 3 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8A01EF3C
OS Stack limit: 8A017000
CPU 0 (Thread 8A0244A0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: 00369EBD (SERVER.NLM|CacheUpdateProcedure+D6)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00364CC2 (SERVER.NLM|StartWorkToDo+23)
-004C18BC (SERVER.NLM|MaximumDirtyTime+2C)
00338F66 (SERVER.NLM|AnalyzeMutex+2A)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--FE0CDD80 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00214087 (SERVER.NLM|WorkerThread+B3)
-004C18BC (SERVER.NLM|MaximumDirtyTime+2C)
--34FAD275 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8A0244A0 (UHCIDRV.CAD|UHCIAbortXfer+6C5)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8A0244A0 (UHCIDRV.CAD|UHCIAbortXfer+6C5)
00221AE8 (SERVER.NLM|TcoNewSystemThreadEntryPoint+40)
--8A0244A0 (UHCIDRV.CAD|UHCIAbortXfer+6C5)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--34343434 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--245C8B53 ?
--6A006A08 ?
--B00C6800 ?
--74FF00A5 ?
--74FF2C24 ?
--438D2C24 ?
--0CE85049 ?
--83F6339C ?
--1D8918C4 ?
-00A5B68C (UHCIDRV.CAD|UHCIDRVModuleHandle+0)
--0C24448B ?
--A5B688A3 ?
--56456800 ?
--3068544E ?
--5300A5B0 ?
--19CC3BE8 ?
--0CC483F6 ?
--A5B690A3 ?
--75C08500 ?
--B0546807 ?
--7BEB00A5 ?
--7B68006A ?
--6A8A01F1 ?
--00006800 (LOADER.NLM|KernelAddressSpace+6800)
--076A7800 ?
--B69035FF ?
--09E800A5 ?
--83762785 ?
--00A318C4 (ACPIDRV.PSM|__NLM_BSS_End+22D0)
--8500A5B0 ?
--6A2474C0 ?
--F3166800 ?
--006A8A01 ?
--066A006A ?
--B69035FF ?
--E5E800A5 ?
--83762784 ?
--08A318C4 ?
--8500A5B0 ?
--680775C0 ?
-00A5B074 (UHCIDRV.CAD|RtnFromRealID+6C)
--006A29EB ?
--01F23568 ?
--6A006A8A ?
--FF056A00 ?
--A5B69035 ?
--84BAE800 ?

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.
0 Likes
jgray Absent Member.
Absent Member.

Re: Mulitple abends

Not having all of the abend, it makes it hard to see what modules are bing used. The things I would check are the following to make sure I have the latest build. NSS.NLM, TCP.NLM, and SERVER.EXE. There are new ones for SP8 that are post patches. Like what was said, it's the coredump that will tell Novell what is causing the abend.

jgray
0 Likes
ataubman Absent Member.
Absent Member.

Re: Mulitple abends

By "whole entry" I meant including the modules list, and any extra info that may be after that list.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.