From owner-freebsd-scsi  Sat May  8  9:19:16 1999
Delivered-To: freebsd-scsi@freebsd.org
Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12])
	by hub.freebsd.org (Postfix) with ESMTP id B8EB415B2A
	for <freebsd-scsi@FreeBSD.ORG>; Sat,  8 May 1999 09:19:05 -0700 (PDT)
	(envelope-from wilko@yedi.iaf.nl)
Received: from yedi.iaf.nl (uucp@localhost)
	  by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id RAA18364;
	  Sat, 8 May 1999 17:48:15 +0200 (MET DST)
Received: (from wilko@localhost)
	by yedi.iaf.nl (8.9.3/8.9.3) id RAA47601;
	Sat, 8 May 1999 17:34:56 +0200 (CEST)
	(envelope-from wilko)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199905081534.RAA47601@yedi.iaf.nl>
Subject: Re: Getting Pioneer CD changer to work
In-Reply-To: <199905080739.BAA57620@panzer.plutotech.com> from "Kenneth D. Merry" at "May 8, 1999  1:39:34 am"
To: ken@plutotech.com (Kenneth D. Merry)
Date: Sat, 8 May 1999 17:34:56 +0200 (CEST)
Cc: freebsd-scsi@FreeBSD.ORG
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4ME+ PL43 (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

As Kenneth D. Merry wrote ...
> Wilko Bulte wrote...

> > I can still get the system to lock up with the default CHANGER_MIN_BUSY_SECONDS 
> > and CHANGER_MAX_BUSY_SECONDS.
> > 
> > A kernel built with 
> > 
> > # Pioneer cdloader
> > options         CHANGER_MIN_BUSY_SECONDS=5
> > options         CHANGER_MAX_BUSY_SECONDS=15
> > 
> > works fine, no lockups. Apparantly the defaults are too low for the Pioneer.
> 
> That's not terribly surprising.  The defaults are okay for Nakamichi
> changers.  Perhaps they should be changed...

I think the current defaults are pretty low, but then again, I have this
Pioneer beast ;-) ;-)

> > All of the above was tested on a Qlogic 1040 board (isp driver).
> > 
> > The only mystery left is that I can't get it to work using the ncr
> > driver on a ncr810 board:
> > 
> > May  7 23:35:07 p100 savecore: no core dump 
> > May  7 23:35:28 p100 /kernel: ncr1: timeout nccb=0xc0789200 (skip)
> > May  7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): got CAM status 0x4b
> > May  7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): fatal error, failed to
> > attach to device
> > May  7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): lost device
> > May  7 23:35:28 p100 /kernel: (cd1:ncr1:0:5:0): removing device entry
> > May  7 23:35:50 p100 /kernel: ncr1: timeout nccb=0xc0788e00 (skip)
> > May  7 23:36:12 p100 /kernel: ncr1: timeout nccb=0xc0788e00 (skip)
> > May  7 23:36:12 p100 /kernel: (cd2:ncr1:0:5:1): got CAM status 0x4b
> > May  7 23:36:12 p100 /kernel: (cd2:ncr1:0:5:1): fatal error, failed to
> > attach to device
> > 
> > etc. If anybody has a clue why the ncr is so much more obnoxious...
> 
> Hmm, it looks like the initial read capacity is timing out.  You can try
> increasing the timeout for the read capacity in the probe case of
> cdstart() and see if that fixes the problem.
> 
> I'm not sure, though, why the timeouts work okay for the QLogic board and
> not for the NCR.  That's rather perplexing.

Well, it was not clear to me, thats for sure. I'll play around with it
next week. First there is this DLT4500 to fix (the hardware that is)

Groeten / Cheers,

|   / o / /  _  	 Arnhem, The Netherlands	- Powered by FreeBSD -
|/|/ / / /( (_) Bulte 	 WWW  : http://www.tcja.nl 	http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message