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

Conference vaxaxp::alphanotes

Title:Alpha Support Conference
Notice:This is a new Alphanotes, please read note 2.2
Moderator:VAXAXP::BERNARDO
Created:Thu Jan 02 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:128
Total number of notes:617

115.0. "AlphaServer 4100 5/466" by KAOT01::GU_LAROCQUE () Fri May 23 1997 15:18

	I have a customer that has a system that we are trying to force a
crash dump on, but for whatever reason, we never get a valid dump.  
I am unable to determine why, and am wondering if anyone has any ideas.

System information:

This is a AlphaServer 4100 5/466 4MB, hardware model type 1595 running V6.2-1H3.

SYSGEN>
Parameter Name            Current    Default     Min.     Max.     Unit  Dynamic
--------------            -------    -------    -------  -------   ----  -------
DUMPSTYLE                       1          0         0        -1 Bitmask
DUMPBUG                         1          1         0         1 Boolean
BUGREBOOT                       1          1         0         1 Boolean    D
BUGCHECKFATAL                   0          0         0         1 Boolean    D

There is a sysdump file.

$ Directory SYS$SYSROOT:[SYSEXE]

SYSDUMP.DMP;1         512000  29-MAY-1995 11:16:07.36

Total of 1 file, 512000 blocks.



>>> auto_action is now set to restart, it was set to halt.

I have no other ideas.

	/Guy
T.RTitleUserPersonal
Name
DateLines
115.1Questions, No Answers...XDELTA::HOFFMANSteve, OpenVMS EngineeringFri May 23 1997 15:3310
   Can you tell us what you do get in the dump file, if anything?
   What error messages (if any) are displayed during the crash?
   Any dumpfile-related messages during the bootstrap? 
   Any message(s) during the dump?
   Is the system disk shadowed?

   I assume you are following the documented manual crash procedure,
   via the >>> console.

115.2BSS::JILSONWFH in the Chemung River ValleyFri May 23 1997 15:334
Please post the output from the console when the system is crashing.  Also 
how are you forcing the crash?  Is the system disk a shadow set?

Jilly
115.3KAOT01::GU_LAROCQUEFri May 23 1997 17:1422
Sorry, I meant to include this in the base note

Tried the following 

>>> CRASH

also 

>>> d pc ffffffffffffff00
>>> d ps 1f00

%SDA-E-DUMPEMPTY, dump file contains no valid dump

When either of the above are entered into the system, it looks like
the VGA is being reset.  There then appears to be a VERY brief message
indicating memory dump, VGA appears to be reset again, system then reboots.

Unable to get a printer on this system to see the msg.

And yes, system I think it is a 2 member shadow set for the system disk.

/Guy
115.4KAOT01::GU_LAROCQUEFri May 23 1997 18:4025
Customer was able to capture the following:

00>>>crash

CPU 0 restarting

x
**** Boot driver initialization routine returned failure = 00000000

**** OpenVMS (TM) Alpha Operating System V6.2-1H3 - BUGCHECK ****
** Code=0000064C: unloadable
** Crash CPU: 00    Primary CPU: 00    Active CPUs: 00000003
** Current Process = NULL
** Image Name =
**** Memory dump canceled. IOVector = 00000000, Flags = 02016874

halted CPU 0

halt code = 5
HALT instruction executed
PC = ffffffff800561dc

CPU 0 booting
                         
(boot dra0.0.0.3.1 -flags 0,0)
115.5BSS::JILSONWFH in the Chemung River ValleySun May 25 1997 13:385
IMHO this looks like a problem writing to the SWXCR (??) disk set ie DRA0 
but to rule out shadowing have you tried dismounting the nonboot member of 
the system disk shadow set before doing the ANA/CRASH ?

Jilly
115.6EEMELI::MOSEROrienteers do it in the bush...Tue May 27 1997 07:124
    since you have shadow sets, how are your DUMP_DEV environment variables
    setup?
    
    /cmos
115.7KAOT01::GU_LAROCQUETue May 27 1997 12:5010

	Found the problem.

There were 2 new images installed on the system to try and resolve a shadowing
problem.  The images in question were SHADOW_SERVER.EXE;1 & SYS$SHDRIVER.EXE;1 .
Both images were from ALPSHADS_062.BCK;1.

Thanks for the replies.
		/Guy
115.8if caused by ALPSHADS_062.BCK - pls IPMT !HAN::HALLEVolker Halle MCS @HAO DTN 863-5216Tue May 27 1997 13:1310
    Guy,
    
    are you telling us that those 2 images cause the dump to NOT be
    correctly written ?!
    
    If so, please ESCALATE THIS PROBLEM IMMEDIATELY ! Those images are the
    MOST RECENT SHADOWING 'patches' and supposed to show up in the next
    TIMA shadowing kit !
    
    Volker.
115.9KAOT01::GU_LAROCQUETue May 27 1997 15:2710

	Not so Volker.
The patch has apparently been installed on several other systems without any
problems.  It is being looked at specifically from the customer's system.

I will or I am sure that someone else will post the findings as soon
as we know what is going on.

	/Guy
115.10This may be site-specific, it may not...XDELTA::HOFFMANSteve, OpenVMS EngineeringTue May 27 1997 15:308
:	Not so Volker.
:The patch has apparently been installed on several other systems without any
:problems.  It is being looked at specifically from the customer's system.

   Volker is right -- please escalate this first, before we ship out
   a buggy ECO, then the questions can be asked.

115.11KAOT01::GU_LAROCQUETue May 27 1997 16:5810
	No problem with the ECO.

Customer had not properly installed ALPCLUSIO01_062.

Customer will do so later this evening. 

Problem should then be resolved.

	/Guy