From owner-freebsd-current Mon Mar 11 07:11:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA13838 for current-outgoing; Mon, 11 Mar 1996 07:11:55 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA13829 for ; Mon, 11 Mar 1996 07:11:49 -0800 (PST) Received: by Sisyphos id AA01381 (5.67b/IDA-1.5); Mon, 11 Mar 1996 15:26:36 +0100 Message-Id: <199603111426.AA01381@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 11 Mar 1996 15:26:35 +0100 In-Reply-To: "Jordan K. Hubbard" "Re: NCR disk controller, hp disk" (Mar 10, 13:53) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Jordan K. Hubbard" Subject: Re: NCR disk controller, hp disk Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 10, 13:53, "Jordan K. Hubbard" wrote: } Subject: Re: NCR disk controller, hp disk } > This particular HP drive (the C3724S) is known } > to cause problems with tagged commands. Please } } Any chance of adding this to a `rogues list', Stefan? My suggested FAILSAFE define will disable tags and permit an install to succeed. The default number of tags can be set in the kernel config file. The clean solution to this problem is to move the TAG code into the generic SCSI driver, and to have that code react to the ASC/ASCQ values returned by the drive. In the case of the HP, the command would be retried without TAG and would succeed, then ... This is the prefered solution, since it doesn't even require a "rogues" list entry for the drive ... 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