From owner-freebsd-bugs  Sun May 25 02:40:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA17506
          for bugs-outgoing; Sun, 25 May 1997 02:40:03 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id CAA17488;
          Sun, 25 May 1997 02:40:02 -0700 (PDT)
Date: Sun, 25 May 1997 02:40:02 -0700 (PDT)
Message-Id: <199705250940.CAA17488@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Helbig@BA-Stuttgart.DE
Subject: Re:kern/3671:SCSItape drive with AHA2940 locksup system.
Reply-To: Helbig@BA-Stuttgart.DE
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3671; it has been noted by GNATS.

From: Helbig@BA-Stuttgart.DE
To: freebsd-gnats-submit@freebsd.org, markd@Grizzly.COM
Cc:  Subject: Re:kern/3671:SCSItape drive with AHA2940 locksup system.
Date: Sun, 25 May 1997 11:33:11 +0200 (MET DST)

 Here are some more facts, that might help to fix the bug.
 
 This all happened on a machine with  ASUS P55T2P4 motherboard and 
 Adaptec AHA 2940 SCSI controller while trying to install
 FreeBSD 2.2.1 from a Toshiba CDROM XM-3801 TA, SCSI-ID 2 to
 Seagate ST52160N harddisk, SCSI-ID 0.
 
 Installing with 2.2.1 boot.flp went fine till copying started
 to the HD. The system hang after about two seconds.
 
 The same happened when installing with a 2.2.2 boot.flp.
 
 <ALT F4> or <ALT F2> did not work - no panic messages.
 
 Trying to install with a 2.1.7 (*not* 2.1.7.1) boot.flp
 gave us a panic message with approximately these wordings:
 
 Target did not send identify ...
 
 A workaround consisted of setting   
 "Initiating Sync Negotiation"
 to "NO" on all SCSI-ID w/o devices and setting
 "Enable Disc Connection"
 to "YES" on all SCSI-IDs w/o devices in the Adaptec BIOS.
 Menu "Additinal Options", Submenu "SCSI Device Configuration".
 
 After this, the installation worked like a charm.
 
 Hope this helps.
 
 Wolfgang