Conference ozrock::x25_avms

506.0. "New crash on AXP4000 with DNSES" by LEMAN::GABLER () Mon Mar 24 1997 18:34

	Hi,

One of our customer experiences system crash when booting its node after
installing a dnses interface and the X25 software.

He installed this on an AlphaServer 4000 running VMS V6.2-1H3 and Decnet/OSI
V6.3 ECO 5. The symptom is really similar to the problem described by
patch AXPDRIV02_061 but supposed to be fixed in V6.2.

Any Idea or help are welcome ?

	Clark Gabler
	Software Support Geneva

=========== Crash Information follow :

**** OpenVMS (TM) Alpha Operating System V6.2-1H3 - BUGCHECK ****
** Code=000001CC: INVEXCEPTN, Exception while above ASTDEL

** Current Process = WANDD$START
** Image Name = $1$DKB0:[SYS0.SYSCOMMON.][SYSEXE]SYSMAN.EXE
**** Starting Memory Dump...
System crash information
------------------------
Time of system crash: 21-MAR-1997 10:55:36.31


Version of system: OpenVMS (TM) Alpha Operating System, Version V6.2-1H3

System Version Major ID/Minor ID: 3/0


VMScluster node: AV0103, a AlphaServer 4000 5/400 4MB

Crash CPU ID/Primary CPU ID:  00/00

Bitmask of CPUs active/available:  00000001/00000001

CPU bugcheck codes:
        CPU 00 -- INVEXCEPTN, Exception while above ASTDEL



    Press RETURN for more.
SDA>
System crash information
------------------------
System State at Time of Exception
---------------------------------
Exception Frame:
----------------
----------------
        R2  = FFFFFFFF 92AC9600  X25$ZEDRIVER+11600
        R3  = 00000000 00000880
        R4  = 00000000 00000008
        R5  = FFFFFFFF 92AC8460  X25$ZEDRIVER+10460
        R6  = 00000000 00000000
        R7  = 00000000 0000003A
        PC  = FFFFFFFF 92AB948C  X25$ZEDRIVER+0148C
        PS  = 20000000 00001504

         92AB947C:      MULL            R0,R1,R0
         92AB9480:      LDQ             R28,#XFDA0(R2)
         92AB9484:      ADDQ            R28,R0,R0
         92AB9488:      LDL             R0,#X003C(R0)
    PC => 92AB948C:      LDQ_U           R17,#X0030(R0)
         92AB9490:      LDQ_U           R16,#X0033(R0)

    Press RETURN for more.
SDA>
System crash information
------------------------
System State at Time of Exception
---------------------------------
         92AB9494:      EXTLL           R17,R0,R17
         92AB9498:      EXTLH           R16,R0,R16
         92AB949C:      BIS             R16,R17,R17

   PS =>
         MBZ SPAL      MBZ    IPL VMM MBZ CURMOD INT PRVMOD
         0   20   00000000000 15  0   0   KERN   1   KERN


Signal Array
------------
        Length = 00000005
        Type   = 0000000C
        Arg    = 00000000
        Arg    = 00000030
        Arg    = 92AB948C
        Arg    = 00001504

    Press RETURN for more.
SDA>
System crash information
------------------------
System State at Time of Exception
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000030,
PC
=92AB948C, PS=00001504

Saved Scratch Registers in Mechanism Array
------------------------------------------
R0  = 00000000 00000000   R1  = 00000000 00000238   R16 = FFFFFFFF 813B4640
R17 = 00000000 00000000   R18 = 00000000 00000420   R19 = 00000000 00000000
R20 = 00000000 00002100   R21 = FFFFFFFF FFFFFFFC   R22 = 00000000 00000001
R23 = 00000000 00000001   R24 = 00000000 00000000   R25 = 00000000 00000002
R26 = FFFFFFFF 800465A8   R27 = FFFFFFFF 92AC9600   R28 = FFFFFFFF 92AC8480
SDA>
CPU 00 Processor crash information
----------------------------------


CPU 00 reason for Bugcheck: INVEXCEPTN, Exception while above ASTDEL



Process currently executing on this CPU: WANDD$START


Current image file: $1$DKB0:[SYS0.SYSCOMMON.][SYSEXE]SYSMAN.EXE


Current IPL: 21  (decimal)


CPU database address:  81112000
CPU 00 Processor crash information
----------------------------------

CPUs Capabilities:    PRIMARY,QUORUM,RUN

General registers:

R0  = A8000000 00000000 R1  = 00000000 00000000 R2  = FFFFFFFF FFFFFFFD
R3  = FFFFFFFF 82535F60 R4  = 00000000 7FF91A40 R5  = 00000000 7FF91BA8
R6  = 00000000 7FF91C00 R7  = 20000000 00001504 R8  = 00000000 7FF95B48
R9  = 00000000 00000000 R10 = 00000000 002481E8 R11 = 00000000 002481F0
R12 = 00000000 00000001 R13 = FFFFFFFF 825267E0 R14 = 00000000 00000000
R15 = FFFFFFFF 811E1500 R16 = 00000000 000001CC R17 = 00000000 7FF91A40
R18 = 00000000 7FF91C00 R19 = 00000000 00000000 R20 = 00000000 00002100
R21 = FFFFFFFF FFFFFFFC R22 = 00000000 00000001 R23 = 00000000 00000001
R24 = 00000000 00000000 AI  = 00000000 00000002 RA  = FFFFFFFF 800465A8
PV  = FFFFFFFF 92AC9600 R28 = FFFFFFFF 92AC8480 FP  = 00000000 7FF91C60
PC  = FFFFFFFF 8004CD3C PS  = 28000000 00001500


SDA>
CPU 00 Processor crash information
----------------------------------

Processor Internal Registers:


ASN  = 00000000 0000006E                     ASTSR/ASTEN =          0000000F
IPL  =          00000015  PCBB = 00000000 0392A080  PRBR = FFFFFFFF 81112000
PTBR = 00000000 00001CA3  SCBB = 00000000 000001C0  SISR = 00000000 00000000
VPTB = 00000002 00000000  FPCR = 08000000 00000000  MCES = 00000000 00000000


        KSP    = 00000000 7FF919E8
        ESP    = 00000000 7FF95A30
        SSP    = 00000000 7FF9C100
        USP    = 00000000 7EE1D3A0

 

You didn't mention the version of WANDD (the software layered product that
provides the DNSES device driver). You should be using WANDD V1.0-G.
From the PC and failing instruction it appears that a different version 
of WANDD is in use. Please upgrade to the latest version of WANDD for 
VMS V6.2 (WANDD version V1.0-G). If the problem remains, please submit 
an IPMT with a pointer to the crash dump file.

    The ECU of **NT** was used by customer instead of VMS/UNIX ... ;-)
    
    Q1 : How to know the ECU (NT or VMS) been used for configuration ?
    
    Now ...
    
    Imagine we have an Axp with 2 system disks (1 nt and 1 vms) used
    for developpement. When switching from 1 OS to the other one ...
    
    Should we rerun the 'right' ECU before switching the OS ?
    Raymond

    Ask in the Alphaserver4100 conference. I suspect the answer is YES,
    rerun the ECU when swapping operating systems between NT and (VMS or
    UNIX).