From arnej@math.ntnu.no  Fri May 29 05:51:20 1998
Received: from romberg.math.ntnu.no (153@romberg.math.ntnu.no [129.241.15.150])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA24366
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 29 May 1998 05:51:17 -0700 (PDT)
          (envelope-from arnej@math.ntnu.no)
Received: (qmail 18994 invoked from network); 29 May 1998 12:51:08 -0000
Received: from cauchy.math.ntnu.no (129.241.15.128)
  by romberg.math.ntnu.no with SMTP; 29 May 1998 12:51:07 -0000
Received: (from arnej@localhost)
          by cauchy.math.ntnu.no (8.8.8/8.8.4)
	  id OAA25573; Fri, 29 May 1998 14:51:06 +0200 (CEST)
Message-Id: <199805291251.OAA25573@cauchy.math.ntnu.no>
Date: Fri, 29 May 1998 14:51:06 +0200 (CEST)
From: Arne H Juul <arnej@math.ntnu.no>
Reply-To: arnej@math.ntnu.no
To: FreeBSD-gnats-submit@freebsd.org
Subject: exabyte changer doesn't grok LUNs
X-Send-Pr-Version: 3.2

>Number:         6781
>Category:       kern
>Synopsis:       [PATCH] exabyte changer doesn't grok LUNs
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 29 06:00:02 PDT 1998
>Closed-Date:    Sun May 27 17:07:33 PDT 2001
>Last-Modified:  Sun May 27 17:08:32 PDT 2001
>Originator:     Arne Henrik Juul
>Release:        FreeBSD 2.2.6-STABLE i386
>Organization:
Norwegian University of Technology and Science
>Environment:

	This was on a -stable kernel, with the exabyte 8mm tape+changer
	on a symbios (ncr) 810 scsi adapter, in case it matters.

>Description:

	Here's yet another SCSI-device that doesn't support LUNs.
	The "EXABYTE EXB-10i 3.1" identified as a type 8 removable SCSI 2,
	Medium-Changer 10 slots, 1 drive, 1 picker.
	I got very nice and understandable errror messages, though,
	and it doesn't really cause any problems. (I got lots of
	"offline" changers :-)

>How-To-Repeat:

	Borrow one of these antiques and connect to your FreeBSD
	system.

>Fix:
	
	It would be nice with a comment that says explicitly what
	SC_SHOWME, SC_ONE_LU and SC_MORE_LUS should be used for.
	I still don't understand what most of the entries in scsiconf.c
	are needed for at all.
	I guessed that SC_ONE_LU would inhibit probing of LUNs > 0,
	and that seems to be the case.  With the below patch I just
	get one ch0 device and no warnings/errors during boot.

Index: src/sys/scsi/scsiconf.c
===================================================================
RCS file: /usr/cvs/src/sys/scsi/scsiconf.c,v
retrieving revision 1.64.2.26
diff -u -r1.64.2.26 scsiconf.c
--- scsiconf.c	1998/03/08 06:53:13	1.64.2.26
+++ scsiconf.c	1998/05/29 12:43:30
@@ -357,6 +357,10 @@
 		T_CHANGER, T_CHANGER, T_REMOV, "SONY", "TSL-7000", "*",
 		"ch", SC_MORE_LUS
 	},
+	{
+		T_CHANGER, T_CHANGER, T_REMOV, "EXABYTE", "EXB-10i", "*",
+		"ch", SC_ONE_LU
+	},
 #endif /* NCH */
 #if NCD > 0
 #ifndef UKTEST	/* make cdroms unrecognised to test the uk driver */
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->suspended 
State-Changed-By: phk 
State-Changed-When: Tue Jun 2 02:51:39 PDT 1998 
State-Changed-Why:  
awaiting test & commit 
State-Changed-From-To: suspended->closed 
State-Changed-By: jesper 
State-Changed-When: Sun May 27 17:07:33 PDT 2001 
State-Changed-Why:  
No test occured, and this has been obsoleted by CAM, if the 
problem still exist with CAM, please subnet new PR. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6781 
>Unformatted:
