From owner-freebsd-hackers Tue Oct 31 15:27:48 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA01512 for hackers-outgoing; Tue, 31 Oct 1995 15:27:48 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA01507 for ; Tue, 31 Oct 1995 15:27:42 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id PAA05805; Tue, 31 Oct 1995 15:25:53 -0800 Date: Tue, 31 Oct 1995 15:25:52 -0800 (PST) From: -Vince- To: Stefan Esser cc: hackers@freebsd.org Subject: Re: machine reboot & kernel maxusers option In-Reply-To: <199510312241.AA00362@Sysiphos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk On Tue, 31 Oct 1995, Stefan Esser wrote: > On Oct 31, 13:47, -Vince- wrote: > } Subject: machine reboot & kernel maxusers option > } Hi everyone, > } > } I am experiencing the following problem and the machine just > } reboots under FreeBSD-current, anyone have any ideas? > } > } MAND FAILED (4 28) @f0b4aa00. > } assertion "cp" failed: file "../../pci/ncr.c", line 5560 > } sd0(ncr0:0:0): COMMAND FAILED (4 28) @f0b4aa00. > > Well, I thought this would indicate an overrun of the driver > supplied start queue (which is protected by the generic SCSI > code by having the opennings value be bounded by the queue > size), but now I found that the driver sends this return code > in case of an overflow of the command queue in the drive, too. > > The drive seems to either not support the default number of > four tags, and thus 4 commands issued to the drive, or it > does not allow the whole range of 0..255 as tag values. > The driver uses the low numbers as far as possible, but in > certain situations chooses a new range of tag IDs in order > to always have them unique (this was my idea more than a > year ago, but I can't remember when this can happen :) > > Anyway, in this case I'd disable tagged command queues: > > # ncrcontrol -s tags=0 > > and if this makes a difference, it might be a good idea to > try to get a firmware upgrade for that DSP5400 drive ... Hmmm, how much slower will the drive be with tags disabled and how do I find out the revision for the firmware and since this is a drive we just bought a month ago, is there really a need for a firmware upgrade? Does anyone else have this same drive and know if four tags will work? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin