gordon@prls.UUCP (Gordon Vickers) (03/02/88)
Ever since I installed Ultrix 2.0 (two weeks ago), I have been
occationally getting the error message:
dz1.4: silo overflow
The real source of the problem seems to be dz0, port 3 .
Looks like the discrepancy is just a differance in numbering
conventions. The source of the error messages apparently numbers
devices and ports by starting with "1" , whereas /sys/conf/MYVAX
specifications start with zero.
Gordon P. Vickers, (408) 991-5370, Signetics Corp. PO Box 3409 M/S 69
Sunnyvale, California, USA 94086
{pyramid, philabs}!prls!gordon
"Of all the things I haven't got, I like gold the best"
A lyric sung by Elmer Fudd in _The_Wacky_Wabbit_brad@bschp.UUCP (Brad Turner) (03/12/88)
> > Ever since I installed Ultrix 2.0 (two weeks ago), I have been > occationally getting the error message: > dz1.4: silo overflow Here at B-SC we have encountered the infamous ``silo overflow'' from our dmz. After speaking w/DEC we finally figured out the problem was that our dmz and the disk are on the same uba controller. The silo will consistently overflow when screen intensive programs and disk intensive programs hit the machine during peak loads. FYI: we are running ultrix 2.0 on a 750 with a ra81, a tu80, a dmf32 and a dmz32. We only have one uba so short of buying another (and we aren't) our ``fix'' has been to just deal with the situation. One thing we did do was recompile some screen intensive programs and lower their priority. Recompiling will only help marginally, but hey every little bit... brad turner asst. dir. acad. comp. @ bsc --- Brad Turner UUCP: ...!gatech!sbmsg1!scbhq!bschp!brad