From owner-freebsd-scsi Tue Jul 3 7:31:50 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 0729B37B401 for ; Tue, 3 Jul 2001 07:31:48 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f63EVRU89661; Tue, 3 Jul 2001 08:31:31 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200107031431.f63EVRU89661@aslan.scsiguy.com> To: schilling@fokus.gmd.de Cc: ken@kdm.org, freebsd-scsi@FreeBSD.ORG, mckay@thehub.com.au Subject: Re: Problems reading burned CDs In-Reply-To: Your message of "Mon, 02 Jul 2001 15:41:40 +0200." <200107021341.PAA16435@burner.fokus.gmd.de> Date: Tue, 03 Jul 2001 08:31:27 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >>> There is no capacity reporting problem, the capacity is reported as documen >ted >>> in the CD standards. > >>Well, it's good to know it isn't a bug. :) > >It definitely _is_ a bug. Sending a Bus Device Reset message to a target when it doesn't respond in the expected amount of time is a bug? Perhaps the driver could try an abort message first, but the behavior is not completely unreasonable. Your other complaints seem to be in regard to a "bus reset", which never occurred in this situation. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message