kaser@ee.rochester.edu (Bob Kaser) (04/12/91)
I have recently installed an SPARCstation SLC SunOS 4.1.1, replacing a
SUN 3/50, using a CDC Wren IV disk. We now see scsi error messages comming
from the esp0 scsi comtroller.
What is going on? I am using a GENERIC kernal right now. Should I
configure a new kernal? Is there something that I missed when installing
the asyncronous Wren IV onto the SLC.
Any and all help would be appreciated. Below is a listing of the error
messages that I am getting.
Thanks in advance.
Bob Kaser
System Programer
Univ of Rochester
Dept of Elect. Eng.
---------------------------------------------------------------------------
Why did the Lord give us so much {) kaser@ee.rochester.edu
quickness of movement unless it //\\ or
was to avoid responsibility with? ///\\\ ...!rochester!ur-valhalla!kaser
/\
Apr 1 08:52:29 : esp0:^Idata transfer overrun
Apr 1 08:52:29 : esp0:^Idata transfer overrun
Apr 1 08:52:29 : ^IState=DATA Last State=DATA_DONE
Apr 1 08:52:29 : ^IState=DATA Last State=DATA_DONE
Apr 1 08:52:29 : ^ILatched stat=0x10<XZERO> intr=0x10<BUS> fifo 0x0
Apr 1 08:52:29 : ^ILatched stat=0x10<XZERO> intr=0x10<BUS> fifo 0x0
Apr 1 08:52:29 : ^Ilast msg out: <unknown msg 0xff>; last msg in: COMMAND COMPLETE
Apr 1 08:52:29 : ^Ilast msg out: <unknown msg 0xff>; last msg in: COMMAND COMPLETE
Apr 1 08:52:29 : ^IDMA csr=0x80000000
Apr 1 08:52:29 : ^IDMA csr=0x80000000
Apr 1 08:52:29 : ^Iaddr=ff07a000 last=ff078000 last_count=2000
Apr 1 08:52:29 : ^Iaddr=ff07a000 last=ff078000 last_count=2000
Apr 1 08:52:29 : ^ICmd dump for Target 0 Lun 0:
Apr 1 08:52:29 : ^ICmd dump for Target 0 Lun 0:
Apr 1 08:52:29 : ^Icdb=[ 0xa 0x0 0x52 0x0 0x10 0x0 0x0 0x0 0x0 0x0 ]
Apr 1 08:52:29 : ^Icdb=[ 0xa 0x0 0x52 0x0 0x10 0x0 0x0 0x0 0x0 0x0 ]
Apr 1 08:52:29 : ^Ipkt_state 0xf<XFER,CMD,SEL,ARB> pkt_flags 0x0 pkt_statistics 0x0
Apr 1 08:52:29 : ^Ipkt_state 0xf<XFER,CMD,SEL,ARB> pkt_flags 0x0 pkt_statistics 0x0
Apr 1 08:52:29 : ^Icmd_flags=0x27 cmd_timeout 35
Apr 1 08:52:29 : ^Icmd_flags=0x27 cmd_timeout 35
Apr 1 08:52:29 : ^IMapped Dma Space:
Apr 1 08:52:29 : ^IMapped Dma Space:
Apr 1 08:52:29 : ^I^IBase = 0xff078000 Count = 0x2000
Apr 1 08:52:29 : ^I^IBase = 0xff078000 Count = 0x2000
Apr 1 08:52:29 : ^ITransfer History:
Apr 1 08:52:29 : ^ITransfer History:
Apr 1 08:52:29 : ^I^IBase = 0xff078000 Count = 0x2000
Apr 1 08:52:29 : ^I^IBase = 0xff078000 Count = 0x2000
Apr 1 08:52:29 : sd3: SCSI transport failed: reason 'data_ovr': retrying command
Apr 1 08:52:29 : sd3: SCSI transport failed: reason 'data_ovr': retrying command
--
Bob Kaser
System Programer
Univ of Rochester
Dept of Elect. Eng.keithl@loop.uucp (Keith Lofstrom;;;628-3645) (04/15/91)
In article <1991Apr12.165103.23099@ee.rochester.edu> kaser@ee.rochester.edu (Bob Kaser) writes: > >I have recently installed an SPARCstation SLC SunOS 4.1.1, replacing a >SUN 3/50, using a CDC Wren IV disk. We now see scsi error messages coming >from the esp0 scsi controller. This may not be relevant, but ... I recently put a Falcon 760 Mbyte external drive on a SPARC IPC. The cable supplied was 1 meter long. The IPC already had an external tape and CD-ROM drive. With all that cabling, the drive gave errors. Removing the other two peripherals made the external drive work without errors. I custom ordered a half meter cable, and it worked with all the peripherals. Falcon now sells the shorter cable for SPARC class machines. Modern SCSI hosts push the cabling to full speed, and many cabling setups that used to work won't go fast enough - the magic buzzwords are impedance mismatch, stub reflection, dispersive dielectric, and so on. It's surprising things work as well as they do. If you run into problems that seem to be software, but won't go away, take a tip from an old electron wrangler and make your cables shorter. Good luck, Keith -- Keith Lofstrom keithl@loop.uucp ...!sun!nosun!loop!keithl (503)628-3645 KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon" Design Contracting in Bipolar and CMOS - Analog, Digital, and Power ICs