Date: Sun, 28 Sep 1997 09:07:50 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: langfod@dihelix.com (David Langford) Subject: Re: Possible ncr problem? Message-ID: <19970928090750.FH40216@uriah.heep.sax.de> In-Reply-To: <199709280439.SAA00307@caliban.dihelix.com>; from David Langford on Sep 27, 1997 18:39:31 -1000 References: <199709280439.SAA00307@caliban.dihelix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970928090750.FH40216>