Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site yetti.UUCP
Path: utzoo!utcs!mnetor!yetti!eriks
From: eriks@yetti.UUCP (Eriks Rugelis)
Newsgroups: net.unix-wizards,net.bugs.4bsd
Subject: Re: panic: tbuf par fault
Message-ID: <149@yetti.UUCP>
Date: Wed, 10-Apr-85 21:01:41 EST
Article-I.D.: yetti.149
Posted: Wed Apr 10 21:01:41 1985
Date-Received: Thu, 11-Apr-85 02:46:29 EST
References: <632@dataio.UUCP>
Reply-To: eriks@yetti.UUCP (Eriks Rugelis)
Organization: York U. Comp.Sci. Downsview, ONT.
Lines: 32
Xref: utcs net.unix-wizards:12100 net.bugs.4bsd:1362
Summary: 

In article <632@dataio.UUCP> bossert@dataio.UUCP (John Bossert) writes:
>I've not seen any discussion on this subject for quite some time.  Has
>anyone fixed this bug on 750's/4.2bsd?  Thanks much.
>-- 
>			John Bossert
>			Data I/O Corporation
>			Redmond, WA
>			uw-beaver!entropy!dataio!{bossert,usenet}

The USENIX 84.2 tape, that contains nothing but bug-fixes from UCB
also contains an update that claims to take care of this panic.
I'm not convinced that it has the desired effect (since our
'tbuf par fault' panics were reducing in frequency anyway (ANYONE know why?).

The installation notes that come with the hardware rev. 7 kit also make
reference to this problem and seem to imply that rev. 7 fixes it.
We haven't yet had rev. 7 installed so again I have no conclusive evidence.

Get DEC to let you read the rev. 7 installation manual and if you have
a source license, get USENIX to send you the tape.  Hopefully, between
the two of them this problem gets resolved.

P.S. RE: the earlier posting about 'how to load rev. 7 micro-code in UNIX'

Chalk me up as another interested party.  I wanna know!!  In the rev. 7 kit
notes DEC writes that ULTRIX machines should first load the diagnostic
supervisor before starting ULTRIX.  UUGGHHH!!!   Is there SOMEBODY out
there that knows which registers to hit, and how to read the micro-code file?

Eriks Rugelis
USENET: {decvax,linus,ihpn4,allegra}!utzoo!yetti!eriks
BITNET: eriks@yuorion