Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!mit-eddie!uw-beaver!rice!sun-spots-request From: selig@xanth.msfc.nasa.gov Newsgroups: comp.sys.sun Subject: Re: sun4 / xylogics 753 problem Keywords: Hardware Message-ID: <8904111622.AA00290@xanth.msfc.nasa.gov> Date: 27 Apr 89 05:54:14 GMT Sender: usenet@rice.edu Organization: Sun-Spots Lines: 38 Approved: Sun-Spots@rice.edu Original-Date: Tue, 11 Apr 89 11:22:56 CDT X-Sun-Spots-Digest: Volume 7, Issue 257, message 7 of 16 In v7n227 nassio%cfassp12@harvard.harvard.edu (George Nassiopoulos) writes: >Our problem is with a SUN 4/260 (which we have just upgraded from a SUN3). >When we try to do *heavy* transferring of files from a disk on the >machine's xylogics 451 controller to a disk on the machine's xylogics 753 >controller we get the following message on our console: > > spurious VME interrupt at processor level 5 > VME level 3, VME vector 0xffffffff > Additionally, other people have been indicating similar problems. Well, I am finally getting to pay back some of the help I have received on this net. We also had this problem in trying to install a xylogics 753/CDC 1.2GB drive combination in a 4/280. What we finally discovered was that the problem was a recently (I was told) discovered problem by xylogics with this combination. They pretty much indicate those exact symptoms (including system crashes that Nassiopoulos later refers to) in the notice I was read by my system integrator tech. The solution is to get the latest rev controller from xylogics (our new board has 753-107-03; I think the -03 is the rev). As I understand it, this is not a problem with sun 3's (we tried a 3/260 board and it worked fine). Hope this helps folks. MAIL: Bill Selig NASA/MSFC ES53 Huntsville, Al 35812 USA TPC: (205)-544-7608 FTS: 824-7608 SPAN: sam::selig INTERNET: selig@xanth.msfc.nasa.gov [128.158.1.31] selig%sam.span@fedex.msfc.nasa.gov BITNET: selig%sam.span@star.stanford.edu UUCP: uunet!selig@sam.SPAN -OR- uunet!sam.span!selig