Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!csfst1
From: csfst1@unix.cis.pitt.edu (Charles S. Fuller)
Newsgroups: comp.sys.apollo
Subject: Re: Why do I need a "sfcb hash table mutex lock"?
Summary: vtserver, possibly?
Message-ID: <74111@unix.cis.pitt.edu>
Date: 28 Dec 90 19:35:47 GMT
References: <9012280914.AA03633@duc220.uni-duisburg.de>
Organization: Univ. of Pittsburgh, Computing & Information Services
Lines: 21

In article <9012280914.AA03633@duc220.uni-duisburg.de>, hj412fr@duc220.uni-duisburg.de (Martin Anantharaman) writes:

> 	At the press of a key the system (display AND processes) suddenly
> 	freezes  [...]
>
> 	Occasionally tcpd crashes [...] in tcp_$ucblookup [...]
> 	
> 	AND, [...] the following message appears [...] 
> 	"unable to obtain sfcb hash table mutex lock (stream manager/sfcb)"
>	The same message also generally appears in the procdump 
> 	for the vtserver.

Just a hunch, but you may want to verify that you've got the latest
vtserver.  I seem to recall problems with the version released with
10.2.  

Hope this helps.
Chuck Fuller

[Sorry about the cryptic editing, but postnews dutifully refused to post
my suggestion otherwise.]