| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi,
is there anyone help me ?
My customer has VAXstation Mod. 4000-90 that shows system crash many
time every day.
The following pages describes hardware and software environment as wel
a typical crash dump.
VAXstation Mod. 4000-90 hardware configuration:
-----------------------------------------------
KA49-A V1.0-006-V4.0
64MB main memory
VRT19-HA
TZ30 storage device
VAXstation Mod. 4000-90 software configuration:
-----------------------------------------------
CDD V5.0
DECmcc V1.3
UCX V2.0
RDB V4.2
DTR V6.0
MOTIF V1.1
System crash information
------------------------
Time of system crash: 5-AUG-1993 12:01:16.42
Version of system: VAX/VMS VERSION V5.5-2
System Version Major ID/Minor ID: 1/0
System type: VAXstation 4000-90
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 or on interrupt
stack
CPU 00 Processor crash information
----------------------------------
CPU 00 reason for Bugcheck: INVEXCEPTN, Exception while above ASTDEL or on
inter
rupt stack
Process currently executing on this CPU: _FTA4:
Current image file: VSSE03$DKA300:[SYS0.SYSCOMMON.][SYSEXE]SET.EXE
Current IPL: 8 (decimal)
CPU database address: 8111A000
CPU 00 Processor crash information
----------------------------------
General registers:
R0 = 00000008 R1 = 00080000 R2 = 00000001 R3 = 00000001
R4 = 80B91CD0 R5 = 80FDC880 R6 = 00013E28 R7 = 00000002
R8 = 00900828 R9 = 7FEF2F94 R10 = 00000050 R11 = 0C040007
AP = 7FEF2EF4 FP = 7FFE77E4 SP = 7FFE7770 PC = 80579442
PSL = 00080009
CPU 00 Processor crash information
----------------------------------
Processor registers:
P0BR = 828A5600 SBR = 03E19C00 ASTLVL = 00000004
P0LR = 00000206 SLR = 00067080 SISR = 00000100
P1BR = 821CA600 PCBB = 01FA1020 ICCS = 00000041
P1LR = 001FF785 SCBB = 03E12A00 SID = 13000202
TODR = 7F7E9DF5 BPCR = ECC80024 PAMODE = 00000000
MMEPTE = 040309E8 MMESTS = 1C004005 PCSCR = 01000200
ICSR = 00000001 ECR = 0000008E TBSTS = 800001D0
PCCTL = FFFFFC13 PCSTS = FFFFF800 CEFSTS = 00007EA0
CCTL = 00000011 BCEDSTS= 00000000 BCETSTS= 00000000
NESTS = 00000000 NEOCMD = 0000FF14 NEICMD = 00000000
MESR = 00000000 MMCDSR = 08BDD800
CESR = 00000000 CMCDSR = 0000F108 MEAR = 08406010
CPU 00 Processor crash information
----------------------------------
CIOEAR1= 00000000 CIOEAR2= 00000000 CFG/INT= 00000000
CSEAR1 = 00000000 CSEAR2 = 00000000 CNEAR = 00000000
ISP = 8111B200
KSP = 7FFE7770
ESP = 7FFE9800
SSP = 7FFECA48
USP = 7FEF2E9C
No spinlocks currently owned by CPU 00
SDA> sho stack
Process stacks (on CPU 00)
--------------------------
Current operating stack (KERNEL):
7FFE7750 7FEF2F94
7FFE7754 00000050
7FFE7758 0C040007
7FFE775C 7FEF2EF4
7FFE7760 7FFE77E4 CTL$GL_KSTKBAS+005E4
7FFE7764 7FFE7768 CTL$GL_KSTKBAS+00568
7FFE7768 80579442 EXCEPTION+00242
7FFE776C 00080009 UCB$M_MNTVERPND+00009
SP => 7FFE7770 00000004
7FFE7774 7FFE77E4 CTL$GL_KSTKBAS+005E4
7FFE7778 FFFFFFFD
7FFE777C 00000018
7FFE7780 00000008
7FFE7784 00000001
7FFE7788 00000005
7FFE778C 0000000C
7FFE7790 00000005
7FFE7794 90B6F514
7FFE7798 805CADCA PROCESS_MANAGEMENT+023CA
7FFE779C 00C80000
7FFE77A0 805BE123 EVENT_FLAGS_AND_ASTS+00123
7FFE77A4 00000001
7FFE77A8 805BE04F EVENT_FLAGS_AND_ASTS+0004F
7FFE77AC 00000001
7FFE77B0 00000008
7FFE77B4 805C1952 IO_ROUTINES+01F52
7FFE77B8 80B327C4 FTDRIVER+00344
7FFE77BC 80B91E80
7FFE77C0 00013E28
7FFE77C4 80BCA37F TTDRIVER+0594F
7FFE77C8 00000008
7FFE77CC 805C479C IO_ROUTINES+04D9C
7FFE77D0 80B91E80
7FFE77D4 00000008
7FFE77D8 805C4579 IO_ROUTINES+04B79
7FFE77DC 00000002
7FFE77E0 805C4383 IO_ROUTINES+04983
7FFE77E4 00000000
7FFE77E8 00000000
7FFE77EC 7FEF2ED8
7FFE77F0 7FEF2E9C
7FFE77F4 80579620 EXCEPTION+00420
7FFE77F8 7FFEDE06 P1SYSVECTORS+00006
7FFE77FC 03C00000
typically whenever system crash occours, I see running a batch which
starts an alarm setting command procedure by user account MCC_MANAGER.
The DCL command $ SHOW PROC/CONT shows a process in MUTEX state and
continuous deplention of BYTLM quota.
Increase BYTLM doesn't fix the problem but I suspect that behaviour has
some connection with system crash because if the alarm setting command
procedure doesn't start system crashes don't occur.
THANKs in advance
Pino.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5444.1 | MCC exception? | GLDOA::DSMITH | Fri Aug 06 1993 13:01 | 8 | |
I have seen a similar crash footprint in the middle of a batch job doing a large number of historical mcc>sho snmp entity tot utilization commands. The process had a Kernel mode AST (QIO) outstanding. I can't see how MCC could cause a crash, though. Does MCC have any code running that could generate an exception in kernel mode? Doug | |||||