From owner-freebsd-alpha Sat Nov 4 12:32:23 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C292C37B4D7; Sat, 4 Nov 2000 12:32:20 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA11754; Sat, 4 Nov 2000 13:32:17 -0700 (MST) (envelope-from ken) Date: Sat, 4 Nov 2000 13:32:17 -0700 From: "Kenneth D. Merry" To: Wilko Bulte Cc: FreeBSD-alpha mailing list , justin@freebsd.org Subject: Re: SCSI cdrom attach problems on 4-stable Message-ID: <20001104133216.A11678@panzer.kdm.org> References: <20001104200119.A13502@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001104200119.A13502@freebie.demon.nl>; from wkb@freebie.demon.nl on Sat, Nov 04, 2000 at 08:01:19PM +0100 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Nov 04, 2000 at 20:01:19 +0100, Wilko Bulte wrote: > Observed on my Miata, but also on a AS1000A at work: [ ... ] > (cd0:isp0:0:6:0): got CAM status 0x50 > (cd0:isp0:0:6:0): fatal error, failed to attach to device > (cd0:isp0:0:6:0): lost device > (cd0:isp0:0:6:0): removing device entry Status 0x50 is: CAM_AUTOSENSE_FAIL = 0x10,/* Autosense: request sense cmd fail */ and CAM_DEV_QFRZN = 0x40, /* The DEV queue is frozen w/this err */ The first one is the important thing. For some reason the command is failing but we aren't getting any sense information back. > miata#camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > at scbus0 target 2 lun 0 (pass2,da2) > at scbus0 target 6 lun 0 (pass3) > miata# > > The AS1000A has a different cdrom drive (RRD46) but I also tested a > RRD46 on it which caused the same 'lack of attach'. This is annoying at > best. Sometimes a 'camcontrol rescan' will cause 'cd' to attach. There are several things to try here. First, try this: camcontrol cmd pass3 -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4" That will issue a read capacity command to the drive. The second thing to try is booting with a CD in the drive, and without a CD in the drive, and see if one or the other causes it to probe. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message