system@asuvax.UUCP (02/27/87)
We recently upgraded from 4.2 to 4.3 on our VAX 780 and have not been able to get the versatec to run correctly. When the versatec starts to print, the system will respond with : uba0: uba error sr=3000002<UBSTO> fmer=0 fubar=760514 uba0: uba error sr=7000002<UBSTO> fmer=0 fubar=760100 uba0: uba error sr=7000002<UBSTO> fmer=0 fubar=760104 uba0: uba error sr=7000002<UBSTO> fmer=0 fubar=760100 uba0: too many zero vectors (5001 in <2 sec) IPL 0x15 cnfgr: 2000<UBIC> Adapter Code: 0x28 sr: 7000002<UBSTO> dcr: 8010028 (MIC OK) uba0: reset dz0 dz1 dz2 dz3 vp0 lp0 dmf0 dmf1 dmf2 dmf3 This will knock lp0, the dz's, and the dmf's offline, but vp0 will continue to print. We moved vp0 to our second unibus and it knocks the our uda and disk drives offline. In both cases, we have to hard crash the machine and reboot with the versatec turned off. If I boot under our old 4.2 disk, the versatec runs fine. Has anyone run into this problem or have a fix? ------------------------------------------------- Marc Lesure System Manager Engineering Computer Center Arizona State University Tempe, Arizona UUCP: ...!ihnp4!noao!mcdsun!lesure CSNET: lesure@asu ARPA: lesure%asu@csnet-relay
chris@mimsy.UUCP (03/10/87)
In article <120@asuvax.UUCP> system@asuvax.UUCP (Marc Lesure) writes: >uba0: uba error sr=3000002<UBSTO> fmer=0 fubar=760514 [etc., but with different fubar's] >uba0: too many zero vectors (5001 in <2 sec) UBSTO is Slave Time Out. Zero vectors are devices asking for interrupt service, then not writing a vector. This sounds like a hardware problem, but: >If I boot under our old 4.2 disk, the versatec runs fine. You might look at the probe routine in the 4.2 and 4.3 drivers, and see if you are using different vectors. Also make sure your 4.2 and 4.3 /sys/conf/PICKLE files list the same `vector's. We had an unmodified V80 on a 780, so I listed device vp0 at uba? csr 0177510 vector vpintr vpintr and made sure vpprobe() set cvec to the first vector (I forget whether this required any changes). >uba0: reset dz0 dz1 dz2 dz3 vp0 lp0 dmf0 dmf1 dmf2 dmf3 > >This will knock lp0, the dz's, and the dmf's offline, but vp0 will continue >to print. Bizarre. There are some bugs in the 4.3 uba reset code (but no more than there are in the 4.2 uba reset code), but none of the ones I know about quite explain this. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) UUCP: seismo!mimsy!chris ARPA/CSNet: chris@mimsy.umd.edu