| Title: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Notice: | Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server |
| Moderator: | CPEEDY::KENNEDY |
| Created: | Fri Dec 18 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4319 |
| Total number of notes: | 18478 |
Hi,
VAX 7000-610 running SEPS97 often hangs with notrace to
debug. The sytem comes up automatically but pathworks do not
start during the system startup procedure.
Several times I ran pathworks manually until the system is up
for 4 or 5 hrs only. Do I need to upgrade pathworks and Ucx.
BATVX0: ANA/CRASH sys$system:sysdump.dmp
OpenVMS (TM) VAX System dump analyzer
Dump taken on 3-JUN-1997 20:03:02.98
INVEXCEPTN, Exception while above ASTDEL or on interrupt stack
SDA> show crash
System crash information
------------------------
Time of system crash: 3-JUN-1997 20:03:02.98
Version of system: OpenVMS (TM) VAX Version V6.2
System Version Major ID/Minor ID: 1/0
System type: VAX 7000-610
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
Press RETURN for more.
SDA>
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: None
Current IPL: 8 (decimal)
CPU database address: 88250000
MPB address: 00000000
Press RETURN for more.
SDA>
CPU 00 Processor crash information
----------------------------------
General registers:
R0 = 00000008 R1 = 04080000 R2 = 8718BD80 R3 =
87169840
R4 = 8721E5C0 R5 = 87194C00 R6 = 8647A8F0 R7 =
00000034
R8 = 01E9BE8B R9 = 7FFEE490 R10 = 0000BF6E R11 =
0000B8C3
AP = 7FF4B1B4 FP = 7FF4B190 SP = 88251D80 PC =
865CD278
PSL = 04080009
Press RETURN for more.
SDA>
CPU 00 Processor crash information
----------------------------------
Processor registers:
P0BR = 8AB4B000 SBR = 07E0C600 ASTLVL = 00000004
P0LR = 000002B6 SLR = 0007CE00 SISR = 00000100
P1BR = 8A452E00 PCBB = 0476EA20 ICCS = 00000000
P1LR = 001FFA46 SCBB = 07DEE200 SID = 17000202
LDEV = 00108002 LBER = 00000000 LCNR = 00000000
LCON0 = DF0007ED LCON1 = 00000000 TODR = 5F390A7C
LBECR0 = 0040003A LBECR1 = 00008060 LMODE = 000332A4
LMERR = 00000000 BIU_STAT = F00E2070 BIU_ADDR = 00000298
MMESTS = 1C004005 TBSTS = 800001D0 PCSTS = FFFFF800
Press RETURN for more.
SDA>
CPU 00 Processor crash information
----------------------------------
ISP = 88251D80
KSP = 7FFE7800
ESP = 7FFE9800
SSP = 7FFED800
USP = 7FF4B190
No spinlocks currently owned by CPU 00
SDA>
SDA> show stack
CPU 00 Processor stack
----------------------
Current operating stack (INTERRUPT):
88251D60 7FFEE490 P1SYSVECTORS+00690
88251D64 0000BF6E
88251D68 0000B8C3
88251D6C 7FF4B1B4
88251D70 7FF4B190
88251D74 88251D78
88251D78 865CD278 EXCEPTION+00278
88251D7C 04080009
SP => 88251D80 00000004
88251D84 7FF4B190
88251D88 FFFFFFFD P1LR+00181
88251D8C 00000001
88251D90 87169956
88251D94 00000001
88251D98 00000005
88251D9C 0000000C
Press RETURN for more.
SDA>
CPU 00 Processor stack
----------------------
88251DA0 00000005
88251DA4 FFFA6744
88251DA8 8724D042 EXDRIVER+01BC2
88251DAC 04080000
88251DB0 8724C9D7 EXDRIVER+01557
88251DB4 8724C8B8 EXDRIVER+01438
88251DB8 88250210
88251DBC 00000034
88251DC0 01E9BE8B
88251DC4 7FFEE490 P1SYSVECTORS+00690
88251DC8 0000BF6E
88251DCC 0000B8C3
88251DD0 866CFB18 SYSTEM_PRIMITIVES_MIN+00B18
88251DD4 8724C64C EXDRIVER+011CC
88251DD8 00000001
88251DDC 00000000
88251DE0 00000005
88251DE4 88250000
88251DE8 8718EB80
Press RETURN for more.
SDA>
CPU 00 Processor stack
----------------------
88251DEC 8AB28400
88251DF0 00000210 BUG$_MACHINECHK
88251DF4 00000000
88251DF8 8662E147 PROCESS_MANAGEMENT+00147
88251DFC 04C30004
SDA>
SDA> exit
BATVX0:
I am running on VMS 6.2 with DECNET V6.3 ECO06, UCX
Version V4.0 - ECO
Level 2
Pathworks version:
==================
BATVX0: @sys$update:pwrk$versions
Information on PATHWORKS for OpenVMS images installed on this
system:
Image Name Image Version Link date
Linker ID
------------------------------ ---------------- -----------------
-------------
PWRK$LMSRV V5.0-430D 5-SEP-1996 23:09
05-13
PWRK$LMMCP V5.0-430D 5-SEP-1996 23:08
05-13
PWRK$LMDMN V5.0-430D 5-SEP-1996 23:07
05-13
PWRK$MASTER V5.0-430D 5-SEP-1996 20:34
05-13
PWRK$MONITOR V5.0-430D 5-SEP-1996 20:55
05-13
PWRK$NBDAEMON V5.0-430D 5-SEP-1996 20:50
05-13
PWRK$KNBDAEMON V5.0-430D 5-SEP-1996 20:50
05-13
PWRK$STREAMSOS_V5 V5.0-430D 5-SEP-1996 20:46
05-13
PWRK$STREAMSOS_V6 V5.0-430D 5-SEP-1996 20:46
05-13
PWRK$ADMIN V5.0-430D 5-SEP-1996 23:11
05-13
NETBIOS V5.0-430D 5-SEP-1996 20:47
05-13
NETBIOSSHR V5.0-430D 5-SEP-1996 20:48
05-13
I applied the patch MUPA A for OpenVMS yesterday and rebooted the
system but it just hang after one hour and the system came up
but PATHWORKS never comes up during the startup phase.
If any one has any clues on what is going wrong .
Regards!
ANTHONY
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4315.1 | Starting point | VMSNET::L_GULICK | Lew Gulick | Wed Jun 04 1997 11:15 | 12 |
Anthony, There is nothing in the system dump to indicate that PW is a cause of the crash. PW not starting on boot can be caused by a number of conditions. Look at log files in pwrk$logs or pwrk$lmlogs directories to see why PW doesn't start at boot. The UCX version needs to be updated. PW should also be upgraded, but that is probably not the source of these troubles. Lew | |||||
| 4315.2 | Pool corruption by UCX ? | MUNICH::OBERWAGNER | Gerhard Oberwagner CSC-Munich | Fri Jun 06 1997 11:00 | 46 |
re. 1 This really does not look like a PWRK problem.
I also would recommend to install latest ECO for UCX.
Looks as corruption of data structures for the Ethernet Device Driver.
What instruction is at
SDA> e/i EXDRIVER+01BC2
is it REMQUE, INSQUE ?
sho the output of
SDA> show lan/full/device=ex
LAN Data Structures
-------------------
-- EXA Queue Information 6-JUN-1997 15:50:30 --
Control hold queue 80CE4620 Status: Valid, empty
Control request queue 80CE4628 Status: Valid, empty
Control pending queue 80CE4630 Status: Valid, empty
Transmit request queue 80CE4618 Status: Valid, empty
Transmit pending queue 80CE4638 Status: Valid, empty
Receive buffer queue 80CE4640 Status: Valid, 1 element
Receive pending queue 80CE4648 Status: Valid, 16 elements
Post process queue 80CE4650 Status: Valid, empty
Delay queue 80CE4658 Status: Valid, empty
Auto restart queue 80CE4660 Status: Valid, empty
Netwrk mgmt hold queue 80CE4668 Status: Valid, empty
*****
are all these queue structures valid ?
I have seen crashes, where UCX destroyed these queues, but I also have
seen this caused by failing Hardware.
The failing virtual address in the Signal Array shows FFFA6744,
this might come from a self relative link.
But these queue structures have absolute links:
SDA> v q 80CE4648
Queue is complete, total of 16 elements in the queue
A specialist with experience in crashdump analysis might take a look.
/gerhard
| |||||