Subject: SCSI weirdness
To: None <port-sun3@netbsd.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: port-sun3
Date: 09/03/1998 12:26:07
I'm trying to set up NetBSD/sun3 on a new machine, and am seeing some
problems.
I'm having to create the disk on a NetBSD/sparc machine. Fortunately,
both are big-endian, and I have the data from another NetBSD/sun3
machine available, so I could build the filesystem just fine. I first
tried using the sparc installboot; when that didn't work, I compiled
the sun3 installboot on the sparc and used that. That got me a disk
that would boot far enough for the kernel to load, but then....
...
memerr0 at obio0 addr 0x80000 level 7: (Parity memory)
intreg0 at obio0 addr 0xa0000
le0 at obio0 addr 0x120000 level 3: address 08:00:20:06:9f:e1
le0: 8 receive buffers, 2 transmit buffers
si0 at obio0 addr 0x140000 level 2: options=0x1000f
scsibus0 at si0: 8 targets
At this point it appeared to hang. I played with the SCSI bus a
little, fiddling with termination and the like, to no avail. But then
I left it sitting at that point and looking at it several minutes
later, I saw
...
scsibus0 at si0: 8 targets
si0: no REQ for next phase, abort
si0: no REQ while aborting, reset
si0: reset SCSI bus for TID=0 LUN=0
si0: no REQ for next phase, abort
si0: no REQ while aborting, reset
si0: reset SCSI bus for TID=0 LUN=0
Anybody know what this could mean? The machine is a -3/60 and the
kernel is admittedly slightly old (its version string calls it 1.3).
That kernel works fine on another -3/60; I'm wondering if this means
this machine has a fried scsi controller, or there's something wrong
with the cabling, or what. Note that SCSI worked well enough to get
the kernel loaded.
der Mouse
mouse@rodents.montreal.qc.ca
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B