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

Conference kernel::csguk_systems

Title:CSGUK_SYSTEMS
Notice:No restrictions on keyword creation
Moderator:KERNEL::ADAMS
Created:Wed Mar 01 1989
Last Modified:Thu Nov 28 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:242
Total number of notes:1855

196.0. "New SYSBUGCHECK Template." by KERNEL::ADAMS (Brian Adams CSC-Viables '833-3026) Thu Dec 08 1994 05:30

    
    Topic for discussion of a new SYSBUGCHECK template for group use
T.RTitleUserPersonal
Name
DateLines
196.1A suggestionKERNEL::ADAMSBrian Adams CSC-Viables '833-3026Sun Dec 18 1994 18:4916
    Hello 'Customer',
    
    This is the Digital CSC at Basingstoke.
    System, ****** has reached the Vaxsim threshold for Non-Fatal Bugchecks.
    
    The problem is usually due to a user process. Only the user process,
    fails, rather than the system, so there is no requirement for remedial 
    action from Digital, unless a Digital product is involved. If so you
    may wish to log a specific call, to resolve any problem.
    
    Early versions of VaxSIM/SDD may sometimes report "Unknown entries"
    from the errorlog as System Bugchecks. If you are running  SDD, prior
    to V3, you may request the updated kit from DSN, or alternatively, Digital 
    will be pleased to arrange the installation for you.
    
    I will now close this call. Thank you for using our services.
196.2another exampleKERNEL::PETTETNorm Pettet CSC BasingstokeSun Dec 18 1994 18:5238
Dear Customer,

	I have received this VAXsim generated service request reporting
NON-fatal System bugchecks on node !@#$%&. These errors are normally caused by
a Software problem, and only VERY rarely is a hardware problem involved. They
can be isolated by using the following commands. 

    $ vaxsim/merge/entry=(40,37,2,112)/sin=-7-00:00:00/bin=x.x
    $ anal/error x.x
or

    $anal/err/include=bug/since="recent date"

	This will display a number of errorlog entries that will include those
reporting this problem. They will have " NON-FATAL BUGCHECK " in the entry. It
is normally possible to identify a common pattern in these errors. If you have
process accounting enabled, then the information stored there can be of use in
identifying what is causing this problem. It may be necessary to:- 

$ SET PROCESS/DUMP

and wait for the error to re-occur, then analyse the process dump to find out 
what is causing the problem. 

	If the bugchecks are caused by a product you have maintained by
Digital, then please let us know the details and we will pass this call on to
the appropriate support group. If not supported by Digital, then contact your
support group for assistance. 

	If the request has been caused by something else, or you would like
more help, we will be pleased to help in any way we can. Please contact the
Support Centre. 

		In the meantime, I will close this call.


		        Regards,

196.3umCOMICS::GLEDHILLWed Dec 28 1994 15:566
As I mentioned in another note, I dont THINK that process dumps are generated 
for non-fatal bugchecks, I said think, havent tested.

Does anyone know for sure?