Upon returnung from vacations I have upgraded my SUN SLC system to 1.2_BETA

NetBSD ctps01.mit.edu 1.2_BETA NetBSD 1.2_BETA (ctp-sun-slc) #1: 
Wed Jul 17 11:34:21 EDT 1996 

(The sources was updated by sup few hours before the kernel was built)

It booted well but when the time came to SCSI probe I got the following:


sd0 at scsibus0 targ 3 lun 0: <MAXTOR, XT-8760S SUN0669, SUNC> SCSI1 0/direct fixed
sd0: 639MB, 1632 cyl, 15 head, 53 sec, 512 bytes/sec
sd1 at scsibus0 targ 3 lun 1: <, , > SCSI0 0/direct fixed
sd1: 1MB, 16384 cyl, 15 head, 0 sec, 1036576 bytes/sec
sd2 at scsibus0 targ 3 lun 2: <, , > SCSI0 0/direct fixed
sd2: 1MB, 16384 cyl, 15 head, 0 sec, 1036576 bytes/sec
sd3 at scsibus0 targ 3 lun 3: <, , > SCSI0 0/direct fixed
sd3: 1MB, 16384 cyl, 15 head, 0 sec, 1036576 bytes/sec
sd4 at scsibus0 targ 3 lun 4: <, , > SCSI0 0/direct fixed
sd4: 1MB, 16384 cyl, 15 head, 0 sec, 1036576 bytes/sec
sd5 at scsibus0 targ 3 lun 5: <, , > SCSI0 0/direct fixed
sd5: 1MB, 16384 cyl, 15 head, 0 sec, 1036576 bytes/sec
sd6 at scsibus0 targ 3 lun 6: <, , > SCSI0 0/direct fixed
sd6: 1MB, 16384 cyl, 15 head, 0 sec, 1036576 bytes/sec
sd7 at scsibus0 targ 3 lun 7: <, , > SCSI0 0/direct fixed
sd7: 1MB, 16384 cyl, 15 head, 0 sec, 1036576 bytes/sec
st0 at scsibus0 targ 4 lun 0: <ARCHIVE, VIPER 150  21531, -004> SCSI1 1/sequential removable
st0: drive empty

Of course, I have only 1 drive/1 tape external box with SCSI ID
3/4. What all that information about sd2-7 mean? Is it a bug, a
feature that I do not understand or some hardware pecularities?

Another problem: That system at first took down the whole ethernet
segment, other machines on the same segment complain about lost
carrier, could not connect to one another and so on. When I replaced
the transiever all problems disappeared. I do not know if it was just
a broken transiever or the system itself was at fault. The problems
seemed to appear only under heavy load like net swapping from 4 other
diskless machines. 

	Taras Ivanenko <ivanenko@ctpa03.mit.edu>