Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!mips!zaphod.mps.ohio-state.edu!think.com!yale!quasi-eli!cs.yale.edu!news
From: nathan@jacobi.biology.yale.edu (Nathan F. Janette)
Newsgroups: comp.sys.next
Subject: Re: Pixar...panic!
Message-ID: <1991May31.152817.24909@cs.yale.edu>
Date: 31 May 91 15:28:17 GMT
References: <1991May29.221324.29395@leland.Stanford.EDU>
Sender: news@cs.yale.edu (Usenet News)
Reply-To: nathan@jacobi.biology.yale.edu.com
Organization: Yale University, Department of Computer Science, New Haven, CT
Lines: 26
Nntp-Posting-Host: jacobi.biology.yale.edu

In article <1991May29.221324.29395@leland.Stanford.EDU>  
frederic@leland.Stanford.EDU (Frederic Chalot) writes:
> 
> 
>     panic: (Cpu 0) zalloc
>     NeXt ROM Monitor 2.2 v63
>     panic: NeXT Mach 2.0: Wed Nov 21 12:46:53 PST 1990;
>     /ph1_sources/projects/mk-100.1/RELEASE
> 
>     killing all processes panic: (Cpu 0) zalloc
>     NeXt ROM Monitor 2.2 v63
>     panic: NeXT Mach 2.0: Wed Nov 21 12:46:53 PST 1990;
>     /ph1_sources/projects/mk-100.1/RELEASE

We have has a lot of this happening here in our lab since we upgraded the
OS to 2.0.  Even one of our new cubes with 2.0 pre-installed has had these
crashes about once a week.  There usually was one NFS error line above the
first panic line.

We rebuilt all the disks from scratch and upgraded to 2.1, which seems to
have cleared the problem.  Except for one cube that just crashed yesterday,
even after the rebuild/upgrade; it's a rather old cube...

-- 
Nathan Janette
nathan@jacobi.biology.yale.edu