From owner-freebsd-scsi@FreeBSD.ORG Fri Apr 11 16:52:10 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EF5D37B401 for ; Fri, 11 Apr 2003 16:52:10 -0700 (PDT) Received: from hub.org (hub.org [64.117.224.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0560C43FBF for ; Fri, 11 Apr 2003 16:52:10 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.117.224.146]) by hub.org (Postfix) with ESMTP id 6E1C91038DF8; Fri, 11 Apr 2003 20:52:04 -0300 (ADT) Date: Fri, 11 Apr 2003 20:52:04 -0300 (ADT) From: "Marc G. Fournier" To: "Justin T. Gibbs" In-Reply-To: <2164450000.1050100997@aslan.btc.adaptec.com> Message-ID: <20030411205137.C9067@hub.org> References: <2164450000.1050100997@aslan.btc.adaptec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: Intel RAID Controller ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 23:52:10 -0000 On Fri, 11 Apr 2003, Justin T. Gibbs wrote: > >> Apr 10 10:58:05 neptune /kernel: aacp0: on aac0 > >> Apr 10 10:58:06 neptune /kernel: (probe6:aacp0:0:6:0): Vendor Specific Command. CDB: 12 1 80 0 ff 0 > >> Apr 10 10:58:06 neptune /kernel: (probe6:aacp0:0:6:0): ILLEGAL REQUEST asc:24,0 > >> Apr 10 10:58:06 neptune /kernel: (probe6:aacp0:0:6:0): Invalid field in CDB > > > > An inquiry with EVPD set is not a vendor specific command so the printf > > should be fixed. However, the response is correct if the device doesn't > > have EVPD. These messages shouldn't be relevant to your problem. > > Is this a kernel with SCSI_NO_OP_STRINGS defined? All commands print > as vendor specific if the string tables are not available. If that > option is not enabled, I don't see, from looking at the code, why > else we'd list an inquiry of any type as a vendor unique command. Since I've never heard of that option, unless its defined by default, I'll have to say no ...