Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!news.arc.nasa.gov!haven.umd.edu!wam.umd.edu!mikec
From: mikec@wam.umd.edu (Michael D. Callaghan)
Newsgroups: comp.sys.next
Subject: System Panic: (Cpu 0) lock_set_recursive: don't have write lock
Message-ID: <1991Jun16.233418.8700@wam.umd.edu>
Date: 16 Jun 91 23:34:18 GMT
Sender: usenet@wam.umd.edu (USENET Posting)
Organization: University of Maryland at College Park
Lines: 18
Originator: mikec@wor.umd.edu
Nntp-Posting-Host: wor

Our NeXTStation running NeXTStep 2.1, booting off a NeXTCube, does this
about once every 10-15 minutes.

And when we reboot the NeXTStation, both its 105 internal disk is damaged,
and its external disk. 

The system panic usually occurs while the NeXTStation is writing to an
NFS mounted directory from the Cube.

Any suggestions will be greatly appreciated.

Thanks,
MikeC

-- 
---------------------------------------------------------
Michael D. Callaghan, MDC Designs, University of Maryland
---------------------------------------------------------