From owner-freebsd-questions Mon Feb 26 07:09:13 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA23366 for questions-outgoing; Mon, 26 Feb 1996 07:09:13 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA23357 for ; Mon, 26 Feb 1996 07:09:00 -0800 (PST) Received: by Sysiphos id AA04154 (5.67b/IDA-1.5 for questions@freebsd.org); Mon, 26 Feb 1996 16:08:06 +0100 Message-Id: <199602261508.AA04154@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 26 Feb 1996 16:08:05 +0100 In-Reply-To: Dave Andersen "Ncr scsi: overlapped commands attempted" (Feb 23, 19:10) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Dave Andersen Subject: Re: Ncr scsi: overlapped commands attempted Cc: questions@freebsd.org Sender: owner-questions@freebsd.org Precedence: bulk On Feb 23, 19:10, Dave Andersen wrote: } Subject: Ncr scsi: overlapped commands attempted } I'm wondering if anyone could lend me a quick clue here. When I boot } up, I get: } } ABORTED COMMAND asc:4e,0 Overlapped commands attempted } } from an HP 2gb SCSI drive. This happens under both -release and } -current. I'd prefer to run -release or -stable on this machine. } } Hardware: } P133 - 32 MB, 2 1gb NEC SCSI drives, 1 2gb HP SCSI drive } NCR wide SCSI controller } SMC EtherPower 10/100 } No-name 512k VGA card. } } The other two hard drives work perfectly. The HP is detected by the NCR, } doesn't have a SCSI ID conflict, is the first drive in the chain. The } last drive (one of the NECs) is terminated properly. I can install the } system on the two NECs, but I'd really rather not go without the /usr } partition. :-) } } Any suggestions? Yes: Switch off tagged commands ... :( The HP drive is known to cause problems when used with tagged commands. The problem is diagnosed, but the solution isn't obvious, yet ... Can you rebuild your kernel ? Please add the following line to your kernel config file (for -current): options "SCSI_NCR_DFLT_TAGS=0" If you want to build a kernel for -stable, then add another options "SCSI_NCR_MAX_TAGS=0" You can selectively enable tagged commands for the other drives from /etc/rc.local: ncrcontrol -t0 -t1 -s tags=4 configures the driver to use 4 tags with both target 0 and 1, leaving all others alone (assuming the HP is target 2). If this works for you, then I can provide you with another patch, which might allow enabling tags on the HP drive, too. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se