Subject: RE: Stability of NetBSD/VAX
To: 'port-vax@netbsd.org' <port-vax@NetBSD.ORG>
From: Reinhold J. Gerharz <rgerharz@vitro.vitro.com>
List: port-vax
Date: 04/11/1997 11:42:23
I don't know about VS2000, but a uVAX II can be told to HALT by sending =
a break on the console. (This can be disable.) Could it be that random =
binary data is somehow cammanding your terminal to send a break or some =
other command sequence?

----------
From: 	Boris Gjenero[SMTP:bgjenero@undergrad.math.uwaterloo.ca]
Sent: 	Thursday, April 10, 1997 22:47
To: 	port-vax@netbsd.org
Subject: 	Stability of NetBSD/VAX

Hello,

I'm just wondering how stable is NetBSD/VAX supposed to be.  I've had
some unexplained and bad things happen on my two VAXstation 2000s.=20
First of all, it seems that if junk (eg. a binary file, accidentally) is
sent through the console port there is almost always a crash.  The
VS2000 sometimes even reboots but then doesn't work right until power
cycled.  I've also had panics due to filesystem errors such as corrupt
directories.  This was just some filesystem on /mnt.  I've also just had
fsck on boot crash the system repetedly until I booted into single user
mode and fsck completed without finding errors.  Is this normal or is
something wrong here?  Should things be better on a MicroVAX II?

BTW.  Yes, I know that this is a rather new port and support for VS2000
is especially new, so I'm not trying to lay blame.  I'm just wondering
if these errors are due to NetBSD or bad hardware or configuration.

						Boris Gjenero