>Number:         11346
>Category:       kern
>Synopsis:       1.5_BETA fails to boot when Quantum AtlasIV is on SCSI bus
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 30 14:49:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Jonathan Fuerth
>Release:        1.5_BETA
>Organization:
	
>Environment:
NetBSD 1.5_BETA and 1.5_ALPHA2 GENERIC and INSTALL prebuilt kernels.
(On the i386 port).

Quantum AtlasIV drive on Adaptec AHA4950UW scsi host adapter:
(This is dmesg output from 1.4.2 GENERIC, which does boot fine)

ahc1: target 8 using 16Bit transfers
ahc1: target 8 synchronous at 10.0MHz, offset = 0x8
sd0 at scsibus0 targ 8 lun 0: <QUANTUM, ATLAS IV 9 WLS, 9312> SCSI3 0/direct fixed
sd0: 8761MB, 13816 cyl, 4 head, 324 sec, 512 bytes/sect x 17942584 sectors

>Description:
When trying to boot the 1.5_ALPHA2 and the 1.5_BETA kernels, either
directly from the AtlasIV or from an install floppy, I see the following
output and then the system wedges with the SCSI activity LED on solidly:

ahc1: target 8 using 16Bit transfers
ahc1: target 8 synchronous at 20.0MHz, offset = 0x8
ahc1: target 8 using tagged queuing
sd0 at scsibus0 targ 8 lun 0: <QUANTUM, ATLAS IV 9 WLS, 9312> SCSI3 0/direct fixed

(This output was transcribed by hand)

I've searched through the pr database, and this problem seems similar
to kern/7694.  In that case, the AtlasIV was at fault for not properly
supporting tagged command queuing.  (Note also that 1.4.2 doesn't
report the use of tagged queuing on my drive)

>How-To-Repeat:
Try booting 1.5_BETA on a system with a Quantum AtlasIV attached to an
Adaptec scsi host adapter?

>Fix:
My system will boot 1.5_BETA iff the AtlasIV is not connected.  (But I
don't particularly want a diskless workstation).
>Release-Note:
>Audit-Trail:
>Unformatted: