From owner-freebsd-scsi Wed Oct 28 03:39:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19599 for freebsd-scsi-outgoing; Wed, 28 Oct 1998 03:39:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from loviatar.webcom.com (loviatar.webcom.com [209.1.28.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19593 for ; Wed, 28 Oct 1998 03:39:00 -0800 (PST) (envelope-from graeme@echidna.com) Received: from kigal.webcom.com (kigal.webcom.com [209.1.28.57]) by loviatar.webcom.com (8.9.1/8.9.1) with SMTP id CAA18398; Wed, 28 Oct 1998 02:38:22 -0800 Received: from [199.183.207.131] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 4998187; Wed Oct 28 03:36 PST 1998 Message-Id: <36372BA7.402@echidna.com> Date: Wed, 28 Oct 1998 06:35:19 -0800 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: "Justin T. Gibbs" , scsi@FreeBSD.ORG Cc: info@boatbooks.com Subject: Re: CAM question 3.0-RELEASE References: <199810280447.VAA21943@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > > In article <3636A466.5222@echidna.com> you wrote: > >> This is normal. The system tries to figure out how many tags each unit > >> can support by experimentation and observation. Some disks are > >> broken here and have to be quirk'd to turn off or reduce tags. > > > > Is there some reason why these messages are desirable and need to be on by > > default? > > They help us (the SCSI developers) diagnose problems. They also give the > user an idea of the capabilities of their hardware. I guess it would help if I understood what they were telling me. > > They certainly get annoyingly voluminous at times. The following comment > > is from the freebsd-scsi archives: > > They will stop as soon as the minimum tag count is achieved. Do you reboot > your system all the time or something? Actually, yes ;-) Well, I have a couple of new systems sitting on my desk, and between two systems (which for the moment get powered down / rebooted often) and multiple disks, I've been seeing a lot of such messages. Somehow I had got the impression that the messages recurred within a single run period, but I gather now that's not supposed to be the case. For some reason also I get multiple copies to a console logged in as root, like ... (da0:ahc0:0:0:0) tagged openings now 51 (da0:ahc0:0:0:0) tagged openings now 52 (da0:ahc0:0:0:0) tagged openings now 49 in bright text, followed by ... Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 51 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 51 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 50 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 50 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 49 Oct 28 06:11:25 install7 /kernel: (da0:ahc0:0:0:0) tagged openings now 49 in regular text. Whatever context I was in gets scrolled right off the screen. It would be nice if these messages could be tamed in some way (like only the last in a count-down sequence issued), or made optional, or issued only when critical. -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message