Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!seismo.css.gov!munnari!metro.oz!jimr
From: jimr@metro.oz.UUCP
Newsgroups: mod.computers.vax
Subject: Autoreboot switch ignored after @CRASH
Message-ID: <8511070639.AA18140@seismo.CSS.GOV>
Date: Thu, 7-Nov-85 16:52:08 EST
Article-I.D.: seismo.8511070639.AA18140
Posted: Thu Nov  7 16:52:08 1985
Date-Received: Fri, 8-Nov-85 01:59:35 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 33
Approved: info-vax@ucbvax.berkeley.edu

[]

Whenever our 780 hangs (thanks to the XQP, for example) and we use @CRASH from
the console, an autoreboot occurs (after the registers have been listed and a
system dump taken), even if the autoreboot switch on the cabinet is OFF.  If
we don't want a boot straight away, we have to interrupt it using ^C and/or ^P.
According to the Guide to System Management, the switch should be respected. 

The switch itself is OK: its setting is correctly reflected in the appropriate
register on the CIB(?) board.  Moreover, after a real crash as opposed to a
hang, autoreboot seems to occur only if the switch is on, as desired.

We think the problem started about the time we upgraded to VMS V4.0 in May. But
we tried going back to a V3.7 system pack and console, and the problem occurs
there too.

Has anyone else seen this behaviour?  Any ideas?

The important part of our console CRASH. file is as follows:

		DEPOSIT PC=-1		! INVALIDATE PC
		DEPOSIT PSL=1F0000	! KERNEL MODE, IPL 31
		CONTINUE

We are running VMS V4.1.  The SYSGEN parameter BUGREBOOT is 1 (the default), if
that makes a difference.

--
Jim Richardson
Department of Pure Mathematics, University of Sydney, NSW 2006, Australia
UUCP:	...!seismo!munnari!summer.oz!jimr
ARPA:	jimr%summer.oz@seismo.arpa		CSNET:	jimr@summer.oz