From owner-freebsd-scsi@FreeBSD.ORG Thu Nov 16 06:11:59 2006 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 D9F3516A407; Thu, 16 Nov 2006 06:11:59 +0000 (UTC) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 689A943D5C; Thu, 16 Nov 2006 06:11:59 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.13.6/8.13.6) with ESMTP id kAG6BwXU037469; Wed, 15 Nov 2006 23:11:58 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.13.6/8.13.6/Submit) id kAG6Bw1c037468; Wed, 15 Nov 2006 23:11:58 -0700 (MST) (envelope-from ken) Date: Wed, 15 Nov 2006 23:11:58 -0700 From: "Kenneth D. Merry" To: mjacob@freebsd.org Message-ID: <20061116061158.GA37070@nargothrond.kdm.org> References: <20061115211433.R8053@ns1.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061115211433.R8053@ns1.feral.com> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.88.1/2199/Wed Nov 15 20:54:28 2006 on nargothrond.kdm.org X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: amusing stumble for the 6 to 10 byte checking code X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 06:11:59 -0000 On Wed, Nov 15, 2006 at 21:15:01 -0800, mjacob@freebsd.org wrote: > > This caught my eye this morning: > > > (da0:isp1:0:0:0): WRITE(06). CDB: a 8 68 90 80 0 > (da0:isp1:0:0:0): CAM Status: SCSI Status Error > (da0:isp1:0:0:0): SCSI Status: Check Condition > (da0:isp1:0:0:0): UNIT ATTENTION asc:29,1 > (da0:isp1:0:0:0): Power on occurred > (da0:isp1:0:0:0): Retrying Command (per Sense Data) > (da0:isp1:0:0:0): READ(6)/WRITE(6) not supported, increasing > minimum_cmd_size to > 10. That shouldn't have happened in response to a unit attention. It should only happen if the SIM comes back with CAM_REQ_INVALID, or if the target comes back with an illegal request sense code. So there may have been another intervening error that caused the switchover. > (da0:isp1:0:0:0): WRITE(10). CDB: 2a 0 0 8 68 90 0 0 80 0 > (da0:isp1:0:0:0): CAM Status: SCSI Status Error > (da0:isp1:0:0:0): SCSI Status: Check Condition > (da0:isp1:0:0:0): ILLEGAL REQUEST asc:24,0 > (da0:isp1:0:0:0): Invalid field in CDB > (da0:isp1:0:0:0): Unretryable error Hmm. Illegal field, and not invalid command operation code? That's odd. What kind of drive is this? The CDB looks valid at first glance... > I'm still trying to figure out what happened here. Anyone else seen > this? Never seen it. Ken -- Kenneth Merry ken@kdm.org