[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2766.0. "uvax crashes." by ECADSR::MARTINO (M. Martino DTN 223-5816, PK03-1/21H) Tue May 15 1990 16:40

    I am having problems with my uvax crashing and then rebooting itself.
    So far I have had most of the boards replaced without any success.  
    I'm beginning to suspect decwindows as the possible culprit.  
    If anyone has had this problem and has found it to be a decwindows 
    please let me know the fix.
    
    	Thanks,
    	Mike.
T.RTitleUserPersonal
Name
DateLines
2766.1STAR::MCLEMANJeff McLeman, VMS developmentTue May 15 1990 17:053
One would need a little more context. Is it a machine check? Is it a
system service exception? is it an access violation? 

2766.2Same exact problem...system crashes upon loginLEZAH::MCHIASSONWed May 16 1990 10:3612
    I have a similar problem I am exepriencing right now. I have a VSII
    with 9meg of memory and I am booting it into a cluster. Soon after I
    log in thru decwindows I get my file view. As soon as I try and create
    my first DECTERM, boom! The system crashes with a stack dump. I've had
    everything in this system replaced from the memory boards, cpu boards,
    that F/S is totally stumped. I'm now thinking this may have something
    to do with the software. My gblpages are set at 40000 and gblsections
    at 400. My page/swap files are huge (60K and 10K respectively). I'm
    looking forward to the responses.
    
    mc
    
2766.3What KIND of crash??CSC32::RESKELife's a mystery & I haven't a clueWed May 16 1990 11:475
    
    Again, what kind of crash is it??? 
    
    
    DR
2766.4SSRVEXCEPT, system service exceptionLEZAH::MCHIASSONWed May 16 1990 12:197
    Sorry, 
    		SSRVEXCEPT, unexpected system service exception.
    
    
    thanks,
    
    mc
2766.5DECWIN::JMSYNGEJames M Synge, VMS DevelopmentThu May 17 1990 17:565
    Please enter a QAR on this problem.  You may also wish to post what
    SDA produces when you do a SHOW CRASH, SHOW SUMMARY and SHOW STACK (not
    too many lines, please).  (Include that same info in the QAR.)
    
    James
2766.6SEAPEN::PHIPPSDo not take internally.Thu May 17 1990 19:3012
     I know there is probably no connection but... 

     I got an additional disk recently. My system crashed every 20
     minutes.

     Not knowing any better I ran SYSGEN and did an AUTOCONFIGURE. I also
     did an AUTOGEN. It had been a while and the environment and the ways
     I used the system had changed a great deal.

     Seems ok now.

             Mike
2766.7Here is the crash/stack/summaryLEZAH::MCHIASSONThu May 24 1990 13:55251
    
    Re: .5
    		Here is my summary/crash/stack. I've never entered a QAR so 
    I'm entering this info here. If you still want me to enter one, I will
    but if you can see anything before hand, I won't bother filling one out
    and hopefully I can take of this. If you still want me to fill out a
    QAR, I'll do it...Hopefully, someone can see a problem beforehand, this
    has been going on for months.
    
    mc
    
    
    
SDA> show crash
System crash information
------------------------
Time of system crash: 24-MAY-1990 11:46:16.07


Version of system: VAX/VMS VERSION V5.3    

System Version Major ID/Minor ID: 1/0


VAXcluster node: CUPTRX, a VAXstation II

Crash CPU ID/Primary CPU ID:  00/00

Bitmask of CPUs active/available:  00000001/00000001


CPU bugcheck codes:
	CPU 00 -- SSRVEXCEPT, Unexpected system service exception


    Press RETURN for more.
CPU 00 Processor crash information
----------------------------------


CPU 00 reason for Bugcheck: SSRVEXCEPT, Unexpected system service exception


Process currently executing on this CPU: NETACP


Current image file: YAKNOW$DUA3:[SYS15.SYSCOMMON.][SYSEXE]NETACP.EXE;1


Current IPL: 0  (decimal)


CPU database address:  8053C000



    Press RETURN for more.
CPU 00 Processor crash information
----------------------------------

General registers:

	R0  = 00000000   R1  = 80002398   R2  = 6E8B3E35   R3  = 00006710
	R4  = 0000008C   R5  = 00000057   R6  = 7FFE77A0   R7  = 00000006
	R8  = 00028B82   R9  = 02020057   R10 = 0000DB7E   R11 = 0000648C
	AP  = 7FFE76E4   FP  = 7FFE76CC   SP  = 7FFE76CC   PC  = 8000239E
	PSL = 00000000






    Press RETURN for more.
CPU 00 Processor crash information
----------------------------------
Processor registers:


	P0BR   = 8072F800     SBR    = 008EAA00     ASTLVL = 00000004
	P0LR   = 000020E0     SLR    = 00005200     SISR   = 00000000
	P1BR   = 7FF49600     PCBB   = 0038EE20     ICCS   = 00000040
	P1LR   = 001FFCA6     SCBB   = 008E6200     SID    = 08000000

	TODR   = 59E5342C     SYSTYPE= 01010000

	ISP    = 8053D200
	KSP    = 7FFE76CC
	ESP    = 7FFE9800
	SSP    = 7FFED800
	USP    = 7FF97390


    Press RETURN for more.
CPU 00 Processor crash information
----------------------------------

                No spinlocks currently owned by CPU 00
SDA> sh summary
Current process summary
-----------------------
 Extended Indx Process name    Username    State   Pri   PCB      PHD    Wkset
-- PID -- ---- --------------- ----------- ------- --- -------- -------- ------
 34C00041 0001 SWAPPER                      HIB     16 80137998 80137800      0
 34C00082 0002 DECW$TE_1       SYSTEM       LEF      5 802E1380 8053E400    500
 34C00083 0003 _TWA2:          SYSTEM       LEFO     4 802E18E0 00000000    108
 34C00084 0004 _TWA3:          SYSTEM       LEFO     4 802E2140 00000000    136
 34C00085 0005 _TWA4:          SYSTEM       LEFO     4 802D1E10 00000000    128
 34C00086 0006 DNS$ADVER       SYSTEM       HIB      5 802E2CA0 8076C400    279
 34C00047 0007 ERRFMT          SYSTEM       HIB      8 802939C0 806E0C00    116
 34C00048 0008 CACHE_SERVER    SYSTEM       HIBO    16 80289790 00000000     92
 34C00049 0009 CLUSTER_SERVER  SYSTEM       HIB     10 8028A2A0 805C9C00    209
 34C0004A 000A OPCOM           SYSTEM       HIB      7 8028A420 80655400    141
 34C0004B 000B AUDIT_SERVER    AUDIT$SERVER HIB     10 8028A5A0 8060F800    209
 34C0004C 000C JOB_CONTROL     SYSTEM       HIBO    10 80292C90 00000000    310
 34C0004D 000D CONFIGURE       SYSTEM       HIB     10 80296F00 80561200    161
 34C0004E 000E SMISERVER       SYSTEM       HIB      9 8029BF70 80584000    312
 34C0004F 000F RDMS_MONITOR    SYSTEM       LEF     15 8029EC00 80678200     36
 34C00050 0010 RPC$SWL         SYSTEM       HIBO     8 8029F110 00000000    162
 34C00051 0011 VPA_DC          SYSTEM       HIB     15 802A0850 806BDE00   1014


    Press RETURN for more.
Current process summary
-----------------------
 Extended Indx Process name    Username    State   Pri   PCB      PHD    Wkset
-- PID -- ---- --------------- ----------- ------- --- -------- -------- ------
 34C00053 0013 RSM$INSTALL     SYSTEM       LEFO     5 802BC4A0 00000000     93
 34C00054 0014 NETACP          DECNET       CUR      8 802BC6F0 80726800   5974
 34C00095 0015 DFS$COM_ACP     <dfs$comacp> HIB     10 802F31D0 8069B000    164
 34C00056 0016 EVL             DECNET       HIB      4 802CD3A0 805A6E00     35
 34C00097 0017 DFS$00010001_1  DFS$00010001 HIB      8 802F4C80 80703A00    524
 34C00059 0019 REMACP          SYSTEM       HIBO     8 8029BB40 00000000     35
 34C0005A 001A DECW$SERVER_0   SYSTEM       HIB      8 802D3C80 807F7C00   1300
 34C0005B 001B SYSTEM          SYSTEM       LEF      5 802DE670 8081AA00    334
 34C0005E 001E DECW$SERVER_1   SYSTEM       HIB      7 802DD710 80749600    505
 34C00060 0020 INSPECT$Exec    SYSTEM       HIB      8 8028CE80 80632600     64
 34C00061 0021 DECW$WM_1       SYSTEM       LEF      7 802DEE80 807B2000    650
 34C00062 0022 SYSTEM_SM1      SYSTEM       LEF      6 802DF2B0 8083D800    500
SDA> sh stack
Process stacks (on CPU 00)
--------------------------
Current operating stack (KERNEL):

		7FFE76AC  02020057	
		7FFE76B0  0000DB7E	
		7FFE76B4  0000648C	
		7FFE76B8  7FFE76E4	CTL$GL_KSTKBAS+004E4
		7FFE76BC  7FFE76CC	CTL$GL_KSTKBAS+004CC
		7FFE76C0  7FFE76C4	CTL$GL_KSTKBAS+004C4
		7FFE76C4  8000239E	EXE$EXCPTN+00006
		7FFE76C8  00000000	

	 SP =>  7FFE76CC  00000000	
		7FFE76D0  00000000	
		7FFE76D4  7FFE7750	CTL$GL_KSTKBAS+00550
		7FFE76D8  7FFE77D0	CTL$GL_KSTKBAS+005D0
		7FFE76DC  80000014	EXE$QIOW_3+00004
		7FFE76E0  8010D8F2	EXCEPTION+022F2
		7FFE76E4  00000002	
		7FFE76E8  7FFE7708	CTL$GL_KSTKBAS+00508


    Press RETURN for more.
Process stacks (on CPU 00)
--------------------------
		7FFE76EC  7FFE76F0	CTL$GL_KSTKBAS+004F0
		7FFE76F0  00000004	
		7FFE76F4  7FFE77E4	CTL$GL_KSTKBAS+005E4
		7FFE76F8  FFFFFFFD	
		7FFE76FC  00000000	
		7FFE7700  000158DA	
		7FFE7704  000008F8	BUG$_INVCTERMMSG+00028
		7FFE7708  00000005	
		7FFE770C  0000000C	
		7FFE7710  00000001	
		7FFE7714  6E8B3E35	
		7FFE7718  0001AB98	
		7FFE771C  00C00000	
		7FFE7720  6E8B3E35	
		7FFE7724  0001AB9D	
		7FFE7728  00287600	
		7FFE772C  0001AB9D	
		7FFE7730  00289A00	
		7FFE7734  0001AB9D	


    Press RETURN for more.
Process stacks (on CPU 00)
--------------------------
		7FFE7738  0028E220	
		7FFE773C  0001AB9D	
		7FFE7740  002B2280	
		7FFE7744  0001AB9D	
		7FFE7748  002FA320	
		7FFE774C  000158DA	
		7FFE7750  0000CA26	
		7FFE7754  00010296	SYS$K_VERSION_NETWORKS+00294
		7FFE7758  0001ABA8	
		7FFE775C  000158DA	
		7FFE7760  00285200	
		7FFE7764  0000DB7E	
		7FFE7768  000092A0	
		7FFE776C  00010284	SYS$K_VERSION_NETWORKS+00282
		7FFE7770  00000000	
		7FFE7774  7FFE77A0	CTL$GL_KSTKBAS+005A0
		7FFE7778  0001CDC4	
		7FFE777C  00028B8C	
		7FFE7780  0001CDA0	


    Press RETURN for more.
Process stacks (on CPU 00)
--------------------------
		7FFE7784  00028B40	
		7FFE7788  804AAEB0	
		7FFE778C  00000006	
		7FFE7790  00028B82	
		7FFE7794  02020057	
		7FFE7798  00000000	
		7FFE779C  00010224	SYS$K_VERSION_NETWORKS+00222
		7FFE77A0  02020057	
		7FFE77A4  00000000	
		7FFE77A8  00000006	
		7FFE77AC  00028B82	
		7FFE77B0  00000000	
		7FFE77B4  00018B0E	
		7FFE77B8  000284C0	
		7FFE77BC  00006734	
		7FFE77C0  0000FF08	
		7FFE77C4  0000FBD0	
		7FFE77C8  0000E28B	
		7FFE77CC  0000CA22	


    Press RETURN for more.
Process stacks (on CPU 00)
--------------------------
		7FFE77D0  00000000	
		7FFE77D4  00000000	
		7FFE77D8  7FF973AC	
		7FFE77DC  7FFE77E4	CTL$GL_KSTKBAS+005E4
		7FFE77E0  8013547D	PROCESS_MANAGEMENT+0087D
		7FFE77E4  00000000	
		7FFE77E8  00000000	
		7FFE77EC  7FF973AC	
		7FFE77F0  7FF97390	
		7FFE77F4  8010B9D0	EXCEPTION+003D0
		7FFE77F8  7FFEDE96	P1SYSVECTORS+00096
		7FFE77FC  03C00000	
SDA> exit
2766.8STAR::MCLEMANJeff McLeman, VMS developmentThu May 24 1990 14:341
Aren't you missing some more info?
2766.9Don't know, what did you want?LEZAH::MCHIASSONThu May 24 1990 15:122
    what else were you looking for?
    
2766.10STAR::MCLEMANJeff McLeman, VMS developmentThu May 24 1990 17:137
All I saw in your note was the following:


SDA> show crash
System crash information
------------------------
Time of system crash: 24-MAY-1990 11:46:16.07
2766.11ABSZK::SZETOSimon Szeto, Asian Base-Systems @ZKOThu May 24 1990 23:2514
>All I saw in your note was the following:


>SDA> show crash
>System crash information
>------------------------
>Time of system crash: 24-MAY-1990 11:46:16.07
                                              ^
    I saw a ...                             <NUL> right there after the
    timestamp followed by 200+ more lines.  Anybody else having a problem
    seeing the rest of the note?

    --Simon

2766.12TLE::ROUTLEYKevin Routley - VAX/VMS &amp; XD DEBUGFri May 25 1990 11:508
re .11, .10:

This is another feature of the brain-dead text widget (or is a brain-dead
U*X feature? :-) .  All the info is there, you just have to keep banging on 
the down arrow of the scroll bar until it shows up.  <NUL>s get the text
widget confused, probably because they are expecting zero-terminated strings
or something of that sort.

2766.13Looks like a DECNET problemCSC32::B_HIBBERTWhen in doubt, PANICTue May 29 1990 17:0316
       Your crash was in the NETACP program at PC 1AB98 due to an access
    violation. I suspect that you have found a NETACP bug rather than a
    DECwindows bug. There are a few things you should do to make shure you
    don't have a hardware problem. 
       First you should do an SDA> EXAMINE/INSTRUCTION 1AB98 to make sure that
    the CPU executed the instruction correctly. From the stack I suspect
    that your instruction will make a stack reference since the failing VA
    was on the stack just before the signal array.
       Also do an SDA> SHOW DECNET/DATALINK and look at the fatal error count
    field for your DEQNA/DELQA to see if it is logging errors. Also, since
    this is a NETACP process, it is possible that you are crashing because
    you are receiving garbage from another node. Check your line counters
    under NCP to see if there is a problem. 
    
    Brian Hibbert