Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!pemurray From: pemurray@miavx1.acs.muohio.edu (Peter Murray) Newsgroups: comp.unix.aix Subject: Re: Flaky behavior after installing 3002 upgrade Message-ID: <3149.276bd842@miavx1.acs.muohio.edu> Date: 17 Dec 90 01:25:38 GMT References: <127@edi386.UUCP> Lines: 27 In article <127@edi386.UUCP>, eddjp@edi386.UUCP ( Dewey Paciaffi ) writes: > In article henkel@nepjt.ncsu.edu (Chuck Henkel) writes: > -Problems: > - > -1) The main problem is that dbx causes the entire system to crash with > - the flashing "888" led display. The hidden message is 102 300 0c0, > - which is supposed to mean "Data storage interrupt - processor type" > > I began getting this particular interrupt while backing up NFS file > systems. It turned out that I was running out of disk space (Data Storage) > in my /tmp filesystem. While I'm not sure exactly what the correlation > is, throwing a few more megabytes into /tmp cured my problem. > > I don't remember if this happened pre-3002 or not. We're running the "September Update" (that's 3001, isn't it?) and we see the machine crashing with the 102 300 0c0 message. We happened to narrow it down to a MS-DOS file being served to a PC over NFS (and it's reproducable), but IBM hasn't come up to look at it yet. We have 7 megs of space in the /tmp partition (the way it came installed). Peter -- Peter Murray Neat UNIX Stunts #5: pemurray@miavx1.bitnet 176 Thompson Hall sh> drink