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

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

253.0. "Crash of DECmcc with HUBWATCH" by BACHUS::VANDENBERGHE () Fri May 28 1993 06:08

 Hubwatch is crashing DECmcc :-((

                Launching  HUBwatch (Version 1.1) from DECmcc (Version 1.3) on
                a Agent which is disconnected of the network (but well registered)
                result in a crash of DECmcc.

                The following info is displayed:

%CMA-F-EXCCOP, exception raised; VMS condition code follows
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000018, PC=002407B8, PSL=03C00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0004B4C4  0004B4C4
	                                                   0007C382  0007C382
                                                           000771DC  000771DC
                                                           0007A878  0007A878

                Hope that can help !
		Robert

T.R Title User Personal
Name Date Lines

253.1 open a(nother) CLD!!!! GIDDAY::DRANSFIELD Mike Dransfield, Sydney RSSG Sun May 30 1993 05:29 17

T.R	Title	User	Personal Name	Date	Lines
253.1	open a(nother) CLD!!!!	GIDDAY::DRANSFIELD	Mike Dransfield, Sydney RSSG	`Sun May 30 1993 05:29`	17
	re: .0 This has nothing to do with HUBwatch. It is a problem with either DECmcc or CMA. I have seen this at two sites (with HUBwatch on a VAX 4000/60 it is totally reproduceable) and have got one CLD open (the second site I wasn't real interested in reproducing it ) I suggest that you open a high priority CLD with as much information as possible (the CLD I have open has just requested more information) My guess is that you can probably reproduce this problem if you have a fast enough machine with DECmcc on it and given that it crashes DECmcc, I consider it to be pretty much a show-stopper.... either that or sell a slower machine ;-) cheers, Mike

    re: .0
    This has nothing to do with HUBwatch.
    It is a problem with either DECmcc or CMA.
    I have seen this at two sites (with HUBwatch on a VAX 4000/60 it is
    totally reproduceable) and have got one CLD open (the second site I
    wasn't real interested in reproducing it )
    
    I suggest that you open a high priority CLD with as much information as
    possible (the CLD I have open has just requested more information)
    
    My guess is that you can probably reproduce this problem if you have a
    fast enough machine with DECmcc on it and given that it crashes DECmcc,
    I consider it to be pretty much a show-stopper....
    
    either that or sell a slower machine ;-)
    cheers,
    Mike