From pst@Shockwave.COM  Tue Mar 28 21:36:00 1995
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA21999 for <FreeBSD-gnats-submit@freebsd.org>; Tue, 28 Mar 1995 21:35:59 -0800
Received: (from pst@localhost) by precipice.shockwave.com (8.6.11/8.6.9) id VAA00349; Tue, 28 Mar 1995 21:35:22 -0800
Message-Id: <199503290535.VAA00349@precipice.shockwave.com>
Date: Tue, 28 Mar 1995 21:35:22 -0800
From: Paul Traina <pst@Shockwave.COM>
Reply-To: pst@Shockwave.COM
To: FreeBSD-gnats-submit@freebsd.org
Subject: messages printed when checking CD ROM device too verbose
X-Send-Pr-Version: 3.2

>Number:         281
>Category:       kern
>Synopsis:       Messages printed when checking CD ROM device too verbose
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    gibbs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 28 21:40:00 1995
>Closed-Date:    Thu Feb 6 08:16:13 PST 1997
>Last-Modified:  Thu Feb  6 08:17:26 PST 1997
>Originator:     Paul Traina
>Release:        FreeBSD 2.1.0-Development i386
>Organization:
>Environment:

FreeBSD 2.1.0-current as of last night

>Description:

(bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1
cd0(bt0:4:0): CD-ROM 
cd0(bt0:4:0): NOT READY csi:20,b,0,0 asc:b,0
cd0: could not get size
drive empty

I loaded up the new boot blocks and am NOT booting with -v, so verbose is
turned off.  This is way too much information, and the "drive empty" line
doesn't refer to the device.

In my opinion, the output in this case should have simply been:

(bt0:4:0): "NEC CD-ROM DRIVE:210 1.0" is a type 5 removable SCSI 1
cd0: drive empty

>How-To-Repeat:

Boot a kernel on a system with a CDROM drive with nothing in it.

>Fix:
	
Lose the following lines:

cd0(bt0:4:0): CD-ROM
cd0(bt0:4:0): NOT READY csi:20,b,0,0 asc:b,0
cd0: could not get size

Add the device name to the line:

drive empty
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->ache 
Responsible-Changed-By: scrappy 
Responsible-Changed-When: Sun May 26 13:35:50 PDT 1996 
Responsible-Changed-Why:  
Andrey seems to have done most of the recent work on the SCSI CD code 
Responsible-Changed-From-To: ache->freebsd-bugs 
Responsible-Changed-By: ache 
Responsible-Changed-When: Tue May 28 17:51:56 PDT 1996 
Responsible-Changed-Why:  
It is related to general SCSI subsystem diagnostic style, not to me 
State-Changed-From-To: open->feedback 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:28:27 PDT 1996 
State-Changed-Why:  

Dust off the cobwebs - Confirm Status 
State-Changed-From-To: feedback->open 
State-Changed-By: scrappy 
State-Changed-When: Mon Oct 21 23:28:46 PDT 1996 
State-Changed-Why:  

Problem Still Exists 
Responsible-Changed-From-To: freebsd-bugs->gibbs 
Responsible-Changed-By: scrappy 
Responsible-Changed-When: Tue Oct 22 14:30:28 PDT 1996 
Responsible-Changed-Why:  
seems this is gibbs' area...? 
State-Changed-From-To: open->closed 
State-Changed-By: mpp 
State-Changed-When: Thu Feb 6 08:16:13 PST 1997 
State-Changed-Why:  
The recent changes to the scsi boot messages have improved 
this situation. 
>Unformatted:


