From owner-freebsd-scsi Fri Sep 18 09:05:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13814 for freebsd-scsi-outgoing; Fri, 18 Sep 1998 09:05:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13801 for ; Fri, 18 Sep 1998 09:05:44 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA15014; Fri, 18 Sep 1998 09:58:49 -0600 (MDT) Date: Fri, 18 Sep 1998 09:58:49 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809181558.JAA15014@narnia.plutotech.com> To: Chris Csanady cc: scsi@FreeBSD.ORG Subject: Re: Verbosity of CAM.. Newsgroups: pluto.freebsd.scsi In-Reply-To: <199809181446.JAA05183@friley-185-114.res.iastate.edu> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199809181446.JAA05183@friley-185-114.res.iastate.edu> you wrote: > > Would it be possible to remove this 1 before the 3.0 release? > Perhaps. Perhaps not. The messages should stop after the tag count has settled. Right now, these messages have already helped diagnose at least one problem the NCR driver. They also provide a good indication of the load on the SCSI system that leads up to errors. I don't want to remove a useful diagnostic utility until we're sure the kinks are worked out. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message