From andre.albsmeier@mchp.siemens.de  Thu Feb 19 22:27:09 1998
Received: from david.siemens.de (david.siemens.de [192.35.17.14])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24766
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 19 Feb 1998 22:27:08 -0800 (PST)
          (envelope-from andre.albsmeier@mchp.siemens.de)
Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13])
	by david.siemens.de (8.8.8/8.8.8) with ESMTP id HAA20989
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 20 Feb 1998 07:26:47 +0100 (MET)
Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23])
	by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id HAA10264
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 20 Feb 1998 07:26:49 +0100 (CET)
Received: (from daemon@localhost)
	by curry.mchp.siemens.de (8.8.8/8.8.8) id HAA15858
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 20 Feb 1998 07:26:49 +0100 (CET)
Message-Id: <199802200626.HAA02378@intern>
Date: Fri, 20 Feb 1998 07:26:45 +0100 (CET)
From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
To: FreeBSD-gnats-submit@freebsd.org
Subject: boot messages crewed up due to conflicting flags in scsiconf.c
X-Send-Pr-Version: 3.2

>Number:         5799
>Category:       kern
>Synopsis:       boot messages crewed up due to conflicting flags in scsiconf.c
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 19 22:30:01 PST 1998
>Closed-Date:    Tue Feb 24 07:19:31 PST 1998
>Last-Modified:  Tue Feb 24 07:20:13 PST 1998
>Originator:     Andre Albsmeier
>Release:        FreeBSD 2.2.5-STABLE i386
>Organization:
>Environment:

	FreeBSD 2.2.5-STABLE
	iomega jaz drive and iomega zip drive

>Description:

	The iomega jaz drive now is in scsiconf.c with SD_Q_NO_TAGS. These
	have an equal value as SC_SHOWME. This causes the kernel boot
        messages to look like:

	ahc0: target 3 Tagged Queuing Device
	(ahc0:3:0): "iomega jaz 1GB J^77" type 0 removable SCSI 2

	iomega-
	iomega- 
	jaz*-
	jaz 1GB-
	*-
	J^77-sd3(ahc0:3:0): Direct-Access
	sd3(ahc0:3:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB
	sd3 could not mode sense (4). Using ficticious geometry

	sd3(ahc0:3:0): NOT READY asc:3a,0 Medium not present
	sd3: could not get size
	0MB (0 512 byte sectors) 
	sd3(ahc0:3:0): with 0 cyls, 64 heads, and an average 32 sectors/track
	ahc0:A:4: refuses synchronous negotiation. Using asynchronous transfers
	(ahc0:4:0): "IOMEGA ZIP 100 E.08" type 0 removable SCSI 2

	iomega-
	IOMEGA-sd4(ahc0:4:0): Direct-Access
	sd4(ahc0:4:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB
	sd4 could not mode sense (4). Using ficticious geometry

	sd4(ahc0:4:0): NOT READY asc:3a,0 Medium not present
	sd4: could not get size
	0MB (0 512 byte sectors)
	sd4(ahc0:4:0): with 0 cyls, 64 heads, and an average 32 sectors/track

	
>How-To-Repeat:

	make a new 2.2.5 kernel and boot it with iomega drives

>Fix:
	
	unknown, maybe change SC_SHOWME to something different.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: eivind 
State-Changed-When: Tue Feb 24 07:19:31 PST 1998 
State-Changed-Why:  
PR closed at the request of the originator. 
>Unformatted:
