davis@MASIG4.OCEAN.FSU.EDU (Alan Davis) (06/10/91)
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
_______________________________________________________________________________
Alan Davis | INTERNET davis@masig1.ocean.fsu.edu
MS B-174, Love 008A | SPAN fsu1::davis
Mesoscale Air-Sea Inter. Group | BITNET davis%masig1.ocean.fsu.edu@fsuavm
Florida State University | Phone 904-644-3798
Tallahassee, FL 32306-3041 | FAX 904-644-8579
_______________________________________________________________________________jeremy@perf2.asd.sgi.com (Jeremy Higdon) (06/11/91)
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.