Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!yale!mintaka!spdcc!tauxersvilli!alphalpha!nazgul
From: nazgul@alphalpha.com (Kee Hinckley)
Newsgroups: comp.sys.apollo
Subject: Re: Why do I need a "sfcb hash table mutex lock"?
Message-ID: <1990Dec30.194240.17416@alphalpha.com>
Date: 30 Dec 90 19:42:40 GMT
References: <9012280914.AA03633@duc220.uni-duisburg.de>
Organization: asi
Lines: 36

In article <9012280914.AA03633@duc220.uni-duisburg.de> hj412fr@duc220.uni-duisburg.de (Martin Anantharaman) writes:
>	AND, (here comes...) at some stage the following message appears in the
>	DM ouput pad: "unable to obtain sfcb hash table mutex lock from (stream
>	manager/sfcb)" The same message also generally appears in the proc_dump for
>	the vtserver.

This used to happen to me quite often when I was running out of
processes, but I don't know why it would occur when you press a
key (I have trouble imagining that it has anything to do with the
display controler though).  Maybe someone wired the keypress to
invoke dozens of processes????

Anyway, at SR10.2, at least on my 3500, the following code clears
the lock.  If you run it you should promptly shutdown (whether it
works or not :-).  I'm not sure if it will work on any other machines or
any other revs - it seems unlikely.  At best it will save you that 20
minute shutdown time.

I didn't write it, no one will support it, and God knows what it will do
if it doesn't clear the lock.

main()
{
    char *p;
    p = (char *) 0x3B6F8072;
    *p = 0;
}

-- 
Alphalpha Software, Inc.	|	motif-request@alphalpha.com
nazgul@alphalpha.com		|-----------------------------------
617/646-7703 (voice/fax)	|	Proline BBS: 617/641-3722

I'm not sure which upsets me more; that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.