Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Netware 6.5 SP8 rtvscan.nlm abends with ver 10.1.9.9000

  • 1.  Netware 6.5 SP8 rtvscan.nlm abends with ver 10.1.9.9000

    Posted Jun 06, 2011 01:40 PM

    Hello,

     

     I have about 8 Netware 6.5 SP8 servers on VM that I'm having problems abending as soon as I load or there after vpstart.nlm. In previous builds I had 1 out of that group abend with previous versions Symantec AV Corp. From all the search through Symantec forums, I've read that 10.1.9.9000 resolved the issues with abending in NetWare 6.5 SP8 with the module RTVSCAN.NLM.

     Well, seems like 10.1.9.9000 is also abending when loading or within a few mins of loading.

     

    Attached is an example of what all of my servers are doing:

     

    PVER: 6.50.08

    Server K2 halted Monday, June 6, 2011  10:52:04.968 am
    Abend 1 on P00: Server-5.70.08-1937: CPU Hog Detected by Timer

    Registers:
        CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0023 SS = 0010
        EAX = FBF17BA3 EBX = 00000000 ECX = 005127E8 EDX = 00000001
        ESI = ABE1D300 EDI = 58215D32 EBP = 58215C50 ESP = 58215AB4
        EIP = 00000000 FLAGS = 00000046
        

    Running process: RTV Timer Process
    Thread Owned by NLM: RTVSCAN.NLM
    Stack pointer: 58215488
    OS Stack limit: 5819A1A0
    Scheduling priority: 67371008
    Wait state: 5050100  Delayed
    Stack: --FBF17BA3  ?
           00013DC3  (LOADER.NLM|ASMPOPFD+5)
           00108406  (LOADER.NLM|kSpinUnlockRestore+26)
           --00000246  (LOADER.NLM|KernelAddressSpace+246)
           0026E0CA  (SERVER.NLM|NetWareAlert+56)
           -005127E8  (SERVER.NLM|VolMountID+8)
           --00000246  (LOADER.NLM|KernelAddressSpace+246)
           --ABE1D300  ?
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           002E7256  (SERVER.NLM|INWsprintf+15E)
           -00420716  ?
           --58215AFC  ?
           002E85D0  (SERVER.NLM|OutputToString+CA0)
           --58215B00  ?
           --58215AFC  ?
           --00000010  (LOADER.NLM|KernelAddressSpace+10)
           --58215D32  ?
           --ABE1D300  ?
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           --58215B5E  ?
           -0042071A  ?
           --58215C50  ?
           --58215D32  ?
           --ABE1D300  ?
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           00328D3A  (SERVER.NLM|Free+106A)
           -00135A8C  (LOADER.NLM|ServerLoadDefinitionRecord+0)
           -00431058  (SERVER.NLM|CorruptMemoryNodeDetected+0)
           --00000001  (LOADER.NLM|KernelAddressSpace+1)
           --58215B2C  ?
           --636E7546  ?
           --6E6F6974  ?
           --65724620  ?
           --65722065  ?
           --76696563  ?
           --69206465  ?
           --6C61766E  ?
           --70206469  ?
           --746E696F  ?
           --30207265  ?
           --32383578  ?
           --44433531  ?
           --89000A34  ?
           --006CA1E8  (E1000.LAN|E1000XDmiLink+98E0)
           --00000075  (LOADER.NLM|KernelAddressSpace+75)
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           --9DC922B0  ?
           --89932A00  ?
           --00000046  (LOADER.NLM|KernelAddressSpace+46)
           00108406  (LOADER.NLM|kSpinUnlockRestore+26)
           --00000046  (LOADER.NLM|KernelAddressSpace+46)
           --00000001  (LOADER.NLM|KernelAddressSpace+1)
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           --00000046  (LOADER.NLM|KernelAddressSpace+46)
           -004F7BF4  (SERVER.NLM|MaxOnLineCpu+34)
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           --58524442  ?
           -00133400  (LOADER.NLM|interruptVectorPool+6E0)
           -005127E8  (SERVER.NLM|VolMountID+8)
           0030D858  (SERVER.NLM|CheckClockForLostTicks+18)
           --58215BE4  ?
           --58215CF0  ?
           0030D858  (SERVER.NLM|CheckClockForLostTicks+18)
           0030D858  (SERVER.NLM|CheckClockForLostTicks+18)
           -005127E8  (SERVER.NLM|VolMountID+8)
           0030D858  (SERVER.NLM|CheckClockForLostTicks+18)
           --00000046  (LOADER.NLM|KernelAddressSpace+46)
           0020F775  (SERVER.NLM|PerformCallOuts+1C9)
           -004F7A10  ?
           00327CD0  (SERVER.NLM|Free+0)
           00289324  (SERVER.NLM|InitializeNetWareCommands+B5C)
           --58215C34  ?
           00233650  (SERVER.NLM|SchedTimerISR+D8)
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           --58215CD4  ?
           0030D858  (SERVER.NLM|CheckClockForLostTicks+18)
           -0013BB00  (LOADER.NLM|kVirtualInterruptTable0+0)
           00106524  (LOADER.NLM|kTimer1Interrupt+28)
           --FE00C380  (LOADER.NLM|OSAllocMemory+C380)
           00105B49  (LOADER.NLM|kProcessProtectedModeInterrupt+39)
           0020F775  (SERVER.NLM|PerformCallOuts+1C9)
           -004F7A10  ?
           5690914E  (I2_LDVP.NLM|i2__VEScanMemory+1E1E)
           00289324  (SERVER.NLM|InitializeNetWareCommands+B5C)
           --58215C6C  ?
           00233650  (SERVER.NLM|SchedTimerISR+D8)
           --00000000  (LOADER.NLM|KernelAddressSpace+0)
           --00000010  (LOADER.NLM|KernelAddressSpace+10)
           --58215C84  ?
           -00132D20  (LOADER.NLM|interruptVectorPool+0)
           -0013BB00  (LOADER.NLM|kVirtualInterruptTable0+0)
           00106524  (LOADER.NLM|kTimer1Interrupt+28)
           --FE00C380  (LOADER.NLM|OSAllocMemory+C380)
           00105B49  (LOADER.NLM|kProcessProtectedModeInterrupt+39)
           --58215C50  ?
           --58215D32  ?

    Is there anything I can do to and what too look for to resolve this issue?