Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site drivax.UUCP
Path: utzoo!linus!philabs!prls!amdimage!amdcad!amdahl!drivax!alan
From: alan@drivax.UUCP (Alan Fargusson)
Newsgroups: net.unix-wizards
Subject: Re: System V is Crashing
Message-ID: <218@drivax.UUCP>
Date: Tue, 27-Aug-85 13:31:59 EDT
Article-I.D.: drivax.218
Posted: Tue Aug 27 13:31:59 1985
Date-Received: Fri, 30-Aug-85 00:24:42 EDT
References: <666@brl-tgr.ARPA> <53@qfdts.oz>
Organization: Digital Research, Monterey, CA
Lines: 20

> By using crash(1m) I discovered zillions of entries in the callout array
> which were to restart the printer's tty driver.  I can't remember the
> exact circumstances, but I know that the callouts looked suspect and the
> use of fill characters (add OFILL to tio.c_oflag above) for delays rather
> than callouts cured the problem immediately.

I had forgotten about that one. There is a bug in the DZ driver (dz.c)
in dzproc. The case T_OUTPUT there is a line like:
		if (tp->t_state & (BUSY|TTSTOP))

It should be:
		if (tp->t_state & (TIMEOUT|BUSY|TTSTOP))

I told someone at AT&T about it over a year ago, but I don't think they
wanted to know.
-- 

Alan Fargusson.

{ ihnp4, amdahl, mot }!drivax!alan