Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ames!sgi!jeremy@perf2.asd.sgi.com
From: jeremy@perf2.asd.sgi.com (Jeremy Higdon)
Newsgroups: comp.sys.sgi
Subject: Re: IPI erros msgs.
Message-ID: <109429@sgi.sgi.com>
Date: 10 Jun 91 21:26:23 GMT
References: <9106101327.AA19391@masig4.ocean.fsu.edu>
Sender: guest@sgi.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 13

In article <9106101327.AA19391@masig4.ocean.fsu.edu>, davis@MASIG4.OCEAN.FSU.EDU (Alan Davis) writes:
> I get these error messages intermittently in the SYSLOG about a problem with
> our IPI drive.  When I reported this to the HOTLINE the last time they
> suggested putting in a new IPI drive which we did but obviously did not
> cure the problem.  Can someone at SGI (Dave Olson?) comment on this.
> 
> Jun  7 09:33:04 masig4 unix: ipi0: timeout, resetting
> Jun  7 09:33:04 masig4 unix: ipi0 registers: 84 1C 12 0 B 81 0
> Jun  7 09:33:04 masig4 unix:      Please report the registers to the SGI hotline

I would look into replacing the controller (or making sure that it is up
to date.)  It could be cabling (total cable length is under 50 feet, right?),
but I would check the controller first.