From owner-freebsd-scsi Sun Jul 4 18:21:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 091D815013; Sun, 4 Jul 1999 18:21:28 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id TAA73301; Sun, 4 Jul 1999 19:21:26 -0600 (MDT) (envelope-from ken) Message-Id: <199907050121.TAA73301@panzer.kdm.org> Subject: Re: ncr0: queue is empty In-Reply-To: <19990704224907.A2698@dialup124.mi.uni-koeln.de> from Stefan Esser at "Jul 4, 1999 10:49:07 pm" To: se@FreeBSD.ORG Date: Sun, 4 Jul 1999 19:21:26 -0600 (MDT) Cc: oppermann@pipeline.ch (Andre Oppermann), freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stefan Esser wrote... > On 1999-07-04 12:31 +0200, Andre Oppermann wrote: > > Stefan Esser wrote: > > > > > > On 1999-07-02 10:26 +0200, Andre Oppermann wrote: > > > > scbus0 on ncr0 bus 0: > > > > at scbus0 target 0 lun 0 (pass0,da0) > > > > at scbus0 target 2 lun 0 (pass1,cd0) > > > > at scbus0 target 4 lun 0 (pass2,da1) > > > > at scbus0 target 4 lun 1 (pass3,cd1) > > > > > > Many Quantum drives show erratic behaviour if confronted with too many > > > simultanous commands. For that reason, you may want to add a Quirk entry > > > for your drive to "/sys/cam/cam_xpt.c", similar to the existing entries > > > for all kinds of Atlas drives ... > > > > What is an reasonable value for that drive? > > I guess you want to try the values that work with other Quantum drives: > > { > /* Reports QUEUE FULL for temporary resource shortages */ > { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP34550*", "*" }, > /*quirks*/0, /*mintags*/24, /*maxtags*/32 > }, > > The "reducing number of tags" message has been disabled on popular demand > a few months ago, IIRC. But you can re-enable it, though I don't remember > how ... (kernel config option ? verbose boot ? You'll find out easily by > greping for the origin of that message in the CAM sources ;-) Just boot verbose, that'll re-enable the message. Don't be alarmed at the other "error" messages that pop up as well. Verbose is, as its name implies, verbose. :) You can also find out how many tags your device is using like this: $ camcontrol tags da1 -v (pass1:ahc1:0:1:0): dev_openings 64 (pass1:ahc1:0:1:0): dev_active 0 (pass1:ahc1:0:1:0): devq_openings 64 (pass1:ahc1:0:1:0): devq_queued 0 (pass1:ahc1:0:1:0): held 0 (pass1:ahc1:0:1:0): mintags 2 (pass1:ahc1:0:1:0): maxtags 255 dev_openings + dev_active == total number of available tags The Atlas I had some firmware problems similar to the Atlas II, namely that it would lock up under high load. I think the L915 firmware fixed that problem. I'm not sure whether the Atlas I had the queue full problems that the Atlas II and III have, though. Justin might remember. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message