From owner-freebsd-scsi Sun Sep 28 06:14:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA00722 for freebsd-scsi-outgoing; Sun, 28 Sep 1997 06:14:49 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA00715 for ; Sun, 28 Sep 1997 06:14:45 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id XAA14224 for freebsd-scsi@freebsd.org; Sun, 28 Sep 1997 23:14:40 +1000 Received: from localhost.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with SMTP id XAA16851; Sun, 28 Sep 1997 23:09:13 +1000 (EST) Message-Id: <199709281309.XAA16851@ogre.dtir.qld.gov.au> X-Authentication-Warning: ogre.dtir.qld.gov.au: localhost.dtir.qld.gov.au [127.0.0.1] didn't use HELO protocol To: freebsd-scsi@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: Re: Possible ncr problem? References: <199709280439.SAA00307@caliban.dihelix.com> <19970928090750.FH40216@uriah.heep.sax.de> In-Reply-To: <19970928090750.FH40216@uriah.heep.sax.de> from J Wunsch at "Sun, 28 Sep 1997 07:07:50 +0000" Date: Sun, 28 Sep 1997 23:09:13 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sunday, 28th September 1997, J Wunsch wrote: >As David Langford wrote: > >> Any thought on what this means? > >> assertion "cp" failed: file "../../pci/ncr.c", line 6228 >> sd1: COMMAND FAILED (4 28) @f0497000. >> assertion "cp" failed: file "../../pci/ncr.c", line 6228 >> sd1: COMMAND FAILED (4 28) @f0497000. > >Please, re-read the answers Stefan gave to this question in the >mailing list archives for freebsd-scsi. > >Basically, the IBM drives seem to dislike tagged commands when it >comes to START STOP UNIT. Removing the scsi_start_unit() from >sdopen() probably solves your (and my :) problem, but i didn't try so >far. > >The upcoming CAM code is supposed to handle this situation better. If there is a rough hack that could be applied to 2.2.5, I think we should. This problem is becoming more widespread (with the growing popularity of NCR controllers and IBM disks) and the CAM code will not be here in time. If we could make the message a little bit less horrifying, it would be a start. I can test any fixes, but I don't think I'll be able to generate any in time. Stephen.