After installing SP6 on a NW6.5 SP5 server, I am getting this abend. I
installed the SP to cure a similar problem with LIBC.NLM in SP5. (EIP in
LIBC.NLM) It seemed to cure this abend, but now I have the same one with
XDAV.NLM)
There were no abend problems prior to SP5

Has anyone seen a similar problem?

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.06

Server DSRV halted Sunday, December 3, 2006 5:17:25.209 pm
Abend 5 on P03: Server-5.70.06: Double Fault Processor Exception (Error
code 00000000)

Registers:
CS = 0008 DS = 0068 ES = 0068 FS = 0068 GS = 007B SS = 0068
EAX = 7ACC19E0 EBX = 0000004B ECX = 7AAD3CE0 EDX = 91885223
ESI = 9188524F EDI = 00000104 EBP = 9E2AA000 ESP = 9E2AA000
EIP = 9F52D2F3 FLAGS = 00010206
9F52D2F3 53 PUSH EBX
EIP in XDAV.NLM at code start +000112F3h

The violation occurred while processing the following instruction:
9F52D2F3 53 PUSH EBX
9F52D2F4 56 PUSH ESI
9F52D2F5 8B4508 MOV EAX, [EBP+08]
9F52D2F8 83780400 CMP [EAX+04], 00000000
9F52D2FC 740C JZ 9F52D30A
9F52D2FE 8B4508 MOV EAX, [EBP+08]
9F52D301 FF7004 PUSH dword ptr [EAX+04]
9F52D304 E8E7FFFFFF CALL XDAV.NLM|writeNodesHTML
9F52D309 59 POP ECX
9F52D30A 8B4508 MOV EAX, [EBP+08]



Running process: Apache_Worker 12 Process
Thread Owned by NLM: APACHE2.NLM
Stack pointer: 9E2B955C
OS Stack limit: 9E2AAAE0
Scheduling priority: 67371008
Wait state: 5050050 (Blocked on RW Writer)
Stack: --9E2AA014 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF700 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA028 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC19E0 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA03C ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF660 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA050 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF5C0 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA064 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC1920 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA078 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF520 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA08C ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF480 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA0A0 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC1860 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA0B4 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF3E0 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA0C8 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF340 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA0DC ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF2A0 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA0F0 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF200 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA104 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF160 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA118 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF0C0 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA12C ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACBF020 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA140 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC9F20 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA154 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC17A0 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA168 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC16E0 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA17C ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC1620 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)
--9E2AA190 ?
9F52D36F (XDAV.NLM|writeNodesHTML+7F)
--7ACC9E80 ?
--9188524F ?
--0000004B (LOADER.NLM|KernelAddressSpace+4B)

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