From owner-freebsd-scsi Tue Jul 14 13:07:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05778 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 13:07:02 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05772 for ; Tue, 14 Jul 1998 13:06:59 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id OAA09972; Tue, 14 Jul 1998 14:06:50 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807142006.OAA09972@panzer.plutotech.com> Subject: Re: disappearing cdrom w/ Bt948+CAM In-Reply-To: from Shafeeq Sinnamohideen at "Jul 14, 98 02:31:57 pm" To: shafeeq@cyrus.watson.org (Shafeeq Sinnamohideen) Date: Tue, 14 Jul 1998 14:06:50 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Shafeeq Sinnamohideen wrote... > > options SCSI_DELAY=15 > > > > The default bus settle delay in CAM is 2 seconds, if you don't have > > SCSI_DELAY defined. (it is set to 15 seconds in GENERIC, though) > > > > 0x4a means that we're getting a selection timeout when we try to > > access the device. (and that the queue is frozen, but that's another > > matter) > > > So here is the full dmesg with SCSI_DELAY=15 (it was 5 before) : [ ... ] > bt0: rev 0x08 int a irq 17 on pci0.19.0 > bt0: BT-948 FW Rev. 5.06I Ultra Narrow SCSI Host Adapter, SCSI ID 7, 192 CCBs That looks right -- ID 7. > SMP: AP CPU #1 Launched! > got an error back while probing the CDROM > (probe6:bt0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 > (probe6:bt0:0:6:0): error code 0 > CAM status is 0x4a And that's as expected -- selection timeout. [ ... ] > This is still with the 980520 CAM snap, I haven't yet gotten to try the > latest one, but will probably do so very soon. If you do, let me know how it goes. I'm really not sure what your problem is. If things don't work properly for you with the new snapshot, my guess is that the only way to find out what's going on will be to send us the drive. (we can hook it up to a bus analyzer and try to see what the problem is) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message