Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!uw-beaver!uw-june!uw-entropy!uw-apl!srg
From: srg@uw-apl.UUCP (Spencer Garrett)
Newsgroups: comp.bugs.4bsd,comp.unix.wizards
Subject: problems with microvax ethernet
Message-ID: <170@uw-apl.UUCP>
Date: Fri, 1-May-87 01:30:47 EDT
Article-I.D.: uw-apl.170
Posted: Fri May  1 01:30:47 1987
Date-Received: Sat, 2-May-87 17:07:53 EDT
Organization: UW Applied Physics, Seattle
Lines: 16
Xref: mnetor comp.bugs.4bsd:332 comp.unix.wizards:2110


I've just installed 4.3 BSD on a Microvax II.  Everything seems happy except
the ethernet.  If I do an ifconfig in rc.local then the system hangs on boot.
If I let the system come up without that and do the ifconfig manually then
the ethernet works for a while before the system hangs.  The cpu seems healthy
and the DEQNA board is an F1 revision and works in another Microvax running
Ultrix.  The processor doesn't halt (CR to a waiting getty elicits another
login prompt) but the system will stop processing commands.  I suspect
that some critical system resource is remaining locked, so trivial syscalls
like a write to the terminal succeeds, but not fork or exec.  I haven't
gotten named working yet, but /etc/hosts seems to suffice in its absense.
I can't believe the Berkeley code would be DOA like this, but then the
generic kernel on our tapes claimed it hadn't been configured for this
cpu type.  Simply building a new kernel solved that, but I've run out
of ready ideas about the ethernet problem.  Does anyone out there have
any ideas?

srg@june.cs.washington.edu  or  beaver.cs.washington.edu!uw-apl!srg