Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Serve abend- problem executing code in BSDSOCK.NLM

Status
Not open for further replies.

sajikm

IS-IT--Management
May 31, 2007
4
I am getting server abened because of ' The CPU encountered a problem executing code in BSDSOCK.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM'

Can Some one help me to resolve. Is there any Preventive repair I can do? I am running Netware 6.5 and less experienced admin.


Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.04

Server DAS-SMY-CN-01 halted Thursday, August 2, 2007 7:38:40.802 am
Abend 1 on P01: Server-5.70.04: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0068 ES = 0068 FS = 0068 GS = 007B SS = 0068
EAX = 00000000 EBX = 7EAB6118 ECX = 7EAB61E8 EDX = 00000002
ESI = 7EAB61E8 EDI = 00000000 EBP = 715E6580 ESP = BF6D2C04
EIP = 7F871FEA FLAGS = 00010082
7F871FEA 8B4808 MOV ECX, [EAX+08]=?
EIP in BSDSOCK.NLM at code start +00002FEAh
Access Location: 0x00000008

The violation occurred while processing the following instruction:
7F871FEA 8B4808 MOV ECX, [EAX+08]
7F871FED 51 PUSH ECX
7F871FEE 53 PUSH EBX
7F871FEF FF10 CALL near ptr [EAX]
7F871FF1 83C408 ADD ESP, 00000008
7F871FF4 56 PUSH ESI
7F871FF5 E816748980 CALL LOADER.NLM|kSpinLock
7F871FFA 83C404 ADD ESP, 00000004
7F871FFD 31C0 XOR EAX, EAX
7F871FFF 5D POP EBP



Running process: Server 01:8 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: BF6D2F80
OS Stack limit: BF6CB040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --BFC86F44 ?
--000004B5 ?
--00000000 ?
--7EAB6118 ?
7F871F21 (BSDSOCK.NLM|getBsdDebugInfo+6F1)
--7EAB6118 ?
--00000001 ?
--7EAB6118 ?
--00000000 ?
7F8737FE (BSDSOCK.NLM|remove_thread_from_skt_operation+174E)
--7EAB6118 ?
--00000002 ?
--7EA9B6B8 ?
--00040000 (LOADER.NLM|PSD_LibraryErrno+FF0)
--00000000 ?
--000004B5 ?
--BFA7B938 ?
--7EAB6118 ?
--00001068 ?
--00000886 ?
--BF6D2C84 ?
7E86A91A (TCP.NLM|TCPAnyAddrCheck+11F6)
--7EAB6218 ?
--00000886 ?
7E87389C (TCP.NLM|TCPMPUnsafeConnectionLookup+5B0)
--00000014 ?
--7EA9B6B8 ?
--00000004 ?
--7EA9B6B8 ?
7E86981A (TCP.NLM|TCPAnyAddrCheck+F6)
--7EA9B6B8 ?
--BF6D2C84 ?
--BF9654A4 ?
--BF6D2CB0 ?
--BF6D2CC0 ?
-9EBE3795 (JVM.NLM|_active_table$AbstractInterpreter+DFD)
--82161706 ?
--00000000 ?
--00000000 ?
--00000014 ?
--FC000010 (LOADER.NLM|AllocSlabStruct+10)
--0000FFFF ?
--00000000 ?
--980B0210 ?
--3904A8C0 ?
--00000000 ?
--00000000 ?
--0B040210 ?
--B404A8C0 ?
--00000000 ?
--00000000 ?
--0000002A ?
--B889D8F0 (SERVER.NLM|HYPERVISOR_multicall+3D14)
--00000000 ?
--000000F0 ?
--0000001F ?
--00000026 ?
-7E701734 (NCPIP.NLM|replyVector+0)
--9F0302C0 ?
--BF6D2D10 ?
7DC08349 (DS.NLM|DSMPNCPHandler+76)
--00000000 ?
--00000000 ?
--00000000 ?
--00000000 ?
--9F0302C0 ?
--BF6D2D30 ?
--0000002E ?
7C11A688 (NCP.NLM|ProcessNCPPacketWithLength+5C)
--9F0302C0 ?
-7E701734 (NCPIP.NLM|replyVector+0)
--00000000 ?
--0000002E ?
--BF6D2D30 ?
--0000021A ?
BF67943D (CIOS.NLM|ObjectObjectEntry+1AA)
-7FC377B8 (CIOS.NLM|ClassClass+0)
-7FC377E8 (CIOS.NLM|ClassClass+30)
-7FC2FB90 (CIOS.NLM|deviceInsertedInDebugger+C8)
--00000001 ?
-7FC377E8 (CIOS.NLM|ClassClass+30)
-7FC2FB90 (CIOS.NLM|deviceInsertedInDebugger+C8)
BF671428 (CIOS.NLM|ClassClassEntry+FA)
-7FC2FB90 (CIOS.NLM|deviceInsertedInDebugger+C8)
--0000001D ?
--00000001 ?
--0000003F ?
--0000001D ?
BF67228F (CIOS.NLM|GetObjectInDatabaseWithHandle+52)
--0000000A ?
--BF88FA18 (NWPALOAD.NLM|ExitProcedure+4A14)
--00000001 ?
--00000004 ?
--00030402 (LOADER.NLM|XENSharedInfo+F402)
BF672497 (CIOS.NLM|DatabaseObjectEntry+95)
--BF88FA18 (NWPALOAD.NLM|ExitProcedure+4A14)
BF678F33 (CIOS.NLM|MouseClsNew+180)
-7FC377D4 (CIOS.NLM|ClassClass+1C)
--00000000 ?
BF67943D (CIOS.NLM|ObjectObjectEntry+1AA)

Additional Information:
The CPU encountered a problem executing code in BSDSOCK.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.

Loaded Modules:
NAVENG.NLM NAVENG NLM
Version 1.00.20 June 23, 2007
Code Address: A2DEB000h Length: 00015A93h
Data Address: A1E25000h Length: 00002600h
NAVEX15.NLM NAVEX15
Version 1.00 June 23, 2007
Code Address: 746B5000h Length: 000FDE0Ah
Data Address: A2D5F000h Length: 00019618h
ECOMSRVR.NLM ECOMSRVR
Version 1.00 July 11, 2007
Code Address: A2C04000h Length: 0002BAFCh
Data Address: A1B1F000h Length: 00003904h
ECOMLODR.NLM ECOMLODR
Version 1.00 June 27, 2003
Code Address: 73BF1000h Length: 00000BB1h
Data Address: A29D2000h Length: 000100D0h
I2_LDVP.NLM Symantec NAVAPI Interface NLM
Version 10.00 September 27, 2006
Code Address: 73D65000h Length: 000C54F5h
Data Address: 73E2B000h Length: 000568C4h
SCSCOMMS.NLM Symantec ScsComms NLM
Version 1.00 September 27, 2006
Code Address: 73E86000h Length: 000BFF4Fh
Data Address: 73C2D000h Length: 00041E74h
RTVSCAN.NLM Symantec Runtime Virus Protect NLM
Version 10.00 September 27, 2006
Code Address: 73682000h Length: 000DAC10h
Data Address: 7308E000h Length: 000C77A0h
SNMPHNDL.NLM Intel LANDesk SNMP Trap Alert Handler
Version 6.12 November 16, 2005
Code Address: 73B14000h Length: 00000B77h
Data Address: A11BC000h Length: 00001922h
NLMXHNDL.NLM Intel LANDesk Load NLM Handler
Version 6.12 November 16, 2005
Code Address: 73AF9000h Length: 00000377h
Data Address: 73AFA000h Length: 000004FCh
BCSTHNDL.NLM Intel LANDesk Broadcast Alert Handler
Version 6.12 November 16, 2005
Code Address: 73AF8000h Length: 00000437h
Data Address: A11AD000h Length: 00001114h
IAO.NLM Intel LANDesk Alert Originator
Version 6.12 November 16, 2005
Code Address: A215D000h Length: 0000A657h
Data Address: A2168000h Length: 000370C0h
NDPSGW.NLM NDPS Gateway
Version 3.02 July 14, 2005
Code Address: A1EAE000h Length: 00015901h
Data Address: A1EC4000h Length: 000092D8h
HNDLRSVC.NLM Intel LANDesk Handler Manager
Version 6.12 November 16, 2005
Code Address: A0DFA000h Length: 00002F3Ch
Data Address: 739BF000h Length: 00000AE0h
AMSLIB.NLM Intel LANDesk AMS Library
Version 6.12 November 16, 2005
Code Address: A0BD4000h Length: 00002827h
Data Address: 738C1000h Length: 000007D8h
RMANSRVR.NLM NDPS Resource Manager
Version 3.06 July 13, 2005
Code Address: A2EE4000h Length: 0001D2AFh
Data Address: A1C0B000h Length: 000045F0h
NIPPZLIB.NLM General Purpose ZIP File Library for NetWare
Version 1.00.01 December 20, 2002
Code Address: A0DD1000h Length: 00002A23h
Data Address: 7379C000h Length: 00000048h
ZLIB.NLM ZLIB 1.1.4 General Purpose Compression Library for NetWare
Version 1.01.04 December 20, 2002
Code Address: A2E9C000h Length: 0000BAB4h
Data Address: A0DCB000h Length: 000014D8h
DBNET6.NLM Debug Network IO Support
Version 1.44 July 12, 2005
Code Address: A2D8F000h Length: 0001B658h
Data Address: A2DAB000h Length: 000125A8h
IPMCFG.NLM Web Interface for IP Address Management
Version 1.01.15 December 2, 2004
Code Address: A2D29000h Length: 0000A479h
Data Address: A2D34000h Length: 0000B610h
NTFYDPOP.ENM Directed Pop-Up Delivery Method
Version 2.00.03 February 26, 1999
Code Address: A1B77000h Length: 000049C5h
Data Address: 7345E000h Length: 000002F5h
NIRMAN.NLM TCPIP - NetWare Internetworking Remote Manag
 
I would put SP6 + there are some LIBc patches you need. I wouldn't even try to troubleshoot this till you get patched. SP4 had some nasty problems.

Marvin Huffaker, MCNE
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top