From naddy@bigeye.rhein-neckar.de  Wed Jan  6 15:18:42 1999
Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21093
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 6 Jan 1999 15:18:40 -0800 (PST)
          (envelope-from naddy@bigeye.rhein-neckar.de)
Received: from mips.rhein-neckar.de (uucp@localhost)
	by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id AAA24456
	for FreeBSD-gnats-submit@freebsd.org; Thu, 7 Jan 1999 00:18:21 +0100 (CET)
	(envelope-from naddy@bigeye.rhein-neckar.de)
Received: from bigeye.rhein-neckar.de ([193.197.90.235]) by mips.rhein-neckar.de
	 with esmtp id m0zy1Pb-000WyWC
	(Debian Smail-3.2.0.101 1997-Dec-17 #2); Wed, 6 Jan 1999 23:26:47 +0100 (CET)
Received: (from naddy@localhost)
	by bigeye.rhein-neckar.de (8.9.1/8.9.1) id XAA01703;
	Wed, 6 Jan 1999 23:26:37 +0100 (CET)
	(envelope-from naddy)
Message-Id: <199901062226.XAA01703@bigeye.rhein-neckar.de>
Date: Wed, 6 Jan 1999 23:26:37 +0100 (CET)
From: Christian Weisgerber <naddy@bigeye.rhein-neckar.de>
Reply-To: naddy@bigeye.rhein-neckar.de
To: FreeBSD-gnats-submit@freebsd.org
Subject: [PATCH] CAM driver spews debug messages
X-Send-Pr-Version: 3.2

>Number:         9354
>Category:       kern
>Synopsis:       [PATCH] CAM driver spews debug messages
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    ken
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan  6 15:20:01 PST 1999
>Closed-Date:    Wed Jan 6 16:41:13 PST 1999
>Last-Modified:  Wed Jan  6 16:43:47 PST 1999
>Originator:     Christian Weisgerber
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
>Environment:

Asus SC200 (NCR53C810) SCSI adapter, Quantum XP32275S LXY4 disk.

>Description:

The kernel keeps spewing annoying debugging messages along the lines of

(da0:ncr0:0:0:0): tagged openings now 31
(da0:ncr0:0:0:0): tagged openings now 29
(da0:ncr0:0:0:0): tagged openings now 28

Apparently there is a snippet of debugging code left in
/sys/cam/cam_xpt.c.

>How-To-Repeat:

Heavy disk activity, e.g. cvsup'ing /usr/src, make world,
rm -r /usr/obj, etc.

>Fix:

--- /sys/cam/cam_xpt.c.orig	Wed Jan  6 02:10:40 1999
+++ /sys/cam/cam_xpt.c	Wed Jan  6 23:09:44 1999
@@ -2955,7 +2955,7 @@
 					xpt_dev_ccbq_resize(crs->ccb_h.path,
 							    crs->openings);
 
-					if (bootverbose || 1) {
+					if (bootverbose) {
 						xpt_print_path(crs->ccb_h.path);
 						printf("tagged openings "
 						       "now %d\n",

>Release-Note:
>Audit-Trail:

From: "Kenneth D. Merry" <ken@plutotech.com>
To: naddy@bigeye.rhein-neckar.de
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/9354: [PATCH] CAM driver spews debug messages
Date: Wed, 6 Jan 1999 17:38:04 -0700 (MST)

 Christian Weisgerber wrote...
 > 
 > >Number:         9354
 > >Category:       kern
 > >Synopsis:       [PATCH] CAM driver spews debug messages
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          change-request
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Wed Jan  6 15:20:01 PST 1999
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Christian Weisgerber
 > >Release:        FreeBSD 3.0-CURRENT i386
 > >Organization:
 > >Environment:
 > 
 > Asus SC200 (NCR53C810) SCSI adapter, Quantum XP32275S LXY4 disk.
 > 
 > >Description:
 > 
 > The kernel keeps spewing annoying debugging messages along the lines of
 > 
 > (da0:ncr0:0:0:0): tagged openings now 31
 > (da0:ncr0:0:0:0): tagged openings now 29
 > (da0:ncr0:0:0:0): tagged openings now 28
 > 
 > Apparently there is a snippet of debugging code left in
 > /sys/cam/cam_xpt.c.
 > 
 > >How-To-Repeat:
 > 
 > Heavy disk activity, e.g. cvsup'ing /usr/src, make world,
 > rm -r /usr/obj, etc.
 
 This is a feature, not a bug.  We left the messages in there because they
 often expose drive firmware bugs, and sometimes expose CAM bugs.  As a side
 effect, it also tells you how many concurrent transactions your drive can
 handle.
 
 Your particular drive (Quantum Atlas II with LXY4 firmware) is known to
 have buggy firmware.  It will work okay, but under high load, it will "go
 out to lunch" and not come back on the bus.  Generally, the Adaptec driver
 sends a BDR to the device to wake it up, I'm not sure what the NCR driver
 does.
 
 If you can, I suggest you upgrade to the LYK8 firmware revision for your
 drive.  It will not prevent the drive from interminably returning queue
 full, but it will solve the "drive goes out to lunch" problem that you may
 see under high load.
 
 Ken
 -- 
 Kenneth Merry
 ken@plutotech.com
State-Changed-From-To: open->closed 
State-Changed-By: ken 
State-Changed-When: Wed Jan 6 16:41:13 PST 1999 
State-Changed-Why:  
The "bug" in question is actually a known feature.  As I explained in 
my email attached to this PR, we intend for those messages to be printed. 
This might change in the future, but for now, that's the way it is. 
Users can, of course, make local modifications to disable the message. 


Responsible-Changed-From-To: freebsd-bugs->ken 
Responsible-Changed-By: ken 
Responsible-Changed-When: Wed Jan 6 16:41:13 PST 1999 
Responsible-Changed-Why:  
I co-wrote CAM, I answered the PR, and I'm closing it. 
>Unformatted:
