From owner-freebsd-scsi Thu Aug 15 9: 7:41 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69E1D37B401 for ; Thu, 15 Aug 2002 09:07:37 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1864B43E88 for ; Thu, 15 Aug 2002 09:06:43 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id g7FG5sKD062725; Thu, 15 Aug 2002 10:05:54 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id g7FG5sZT062724; Thu, 15 Aug 2002 10:05:54 -0600 (MDT) (envelope-from ken) Date: Thu, 15 Aug 2002 10:05:54 -0600 From: "Kenneth D. Merry" To: Kurt Seel Cc: freebsd-scsi@FreeBSD.org Subject: Re: pioneer DRM-600 problem Message-ID: <20020815100553.A62621@panzer.kdm.org> References: <3D5B17A4.D2862CA6@utcorp.com> <20020814213546.A59783@panzer.kdm.org> <3D5BCB6F.535DFE78@utcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3D5BCB6F.535DFE78@utcorp.com>; from kseel@utcorp.com on Thu, Aug 15, 2002 at 11:40:31AM -0400 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 [ CCing the -scsi list, so this gets in the archive to (potentially) help other folks, hope you don't mind ] On Thu, Aug 15, 2002 at 11:40:31 -0400, Kurt Seel wrote: > "Kenneth D. Merry" wrote: > > To switch from one CD to another, with one of these devices, you typically > > have to try to do I/O to one CD or another. > > > > Is that the way it works with this changer? Or is there some manual method > > you have to go through to change things around? > > > > > And : > > > mount -t cd9660 /dev/cd0c /conf/tmpmnt > > > Gives me : > > > cd9660: /dev/cd0c: Device busy > > > > Is there anything printed in the dmesg when you try that? If not, boot > > with -v and see if you get more verbose error messages. > > I did this. I made a mistake in my original post, let me explain. > It gives me 'cd9660: /dev/cd0c: Device busy' the second time I try > to mount, after having broken out ^C the first time (it was late at > night ... sorry). The first time it does nothing, forever. I let it > sit 45 minutes while I had dinner. > I booted -v, same results : does nothing, prints nothing. I have > my case open and I don't even see the SCSI controller blink (an > adaptec 2940, bios 1.23 BTW). No lights on the drive either It is very strange that it is sitting there for 45 minutes without doing anything. At the very least you should see a command timeout, since the longest timeout of anything in the open() path in the cd driver is 60 seconds. So, let's see if we can figure out what's going on with the changer. Recompile your kernel with the CAMDEBUG option. Then, before you try mounting a CD in any of the slots in the changer, do this: camcontrol debug -Ic 0:0:0 That should print out every SCSI CDB that goes to that particular LUN on the changer. Hopefully we can figure out which command is hanging. > > > I have tried it with evey permutation of option switches, > > > e.g. parity on, parity off ... no dice. > > > Is there any hope for this unit? I'de really like to put > > > 6 CD's of mp3'ed music on a (atapi) cdrom booted (if you > > > look at the dmesg you'll see root is cd9660:acd0c - could > > > this be causing the problem?) network music server. > > > > Sure, it should work. My guess is that you probably just need to tweak the > > timeouts some. There are two sysctl variables: > > > > kern.cam.cd.changer.min_busy_seconds > > and > > kern.cam.cd.changer.max_busy_seconds > > I set these to 7 (I read this in the documentation I got from > the pioneer web site somewhere) and 20 respectively. Still the > same. Shoulds I maybe turn them down? No, if anything you should crank them higher. Typically these only come into play, though, when you are switching from one LUN to another. Since your problem is coming when you try to access the first LUN, there is probably something else going on. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message