From owner-freebsd-stable Fri Feb 23 14:53:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 4A94237B401 for ; Fri, 23 Feb 2001 14:53:45 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 16ECA3E6B; Fri, 23 Feb 2001 23:53:44 +0100 (CET) Date: Fri, 23 Feb 2001 23:53:44 +0100 From: Jesper Skriver To: Virtual Bob Cc: FreeBSD-STABLE listserv Subject: Re: NCR/Symbios 875 and 4.2-STABLE Message-ID: <20010223235343.A22607@skriver.dk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from hey9811@yahoo.com on Fri, Feb 23, 2001 at 03:52:27PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 23, 2001 at 03:52:27PM -0600, Virtual Bob wrote: > While (still) going through that make release @#$(!, I'm now running into > hardware problems. From syslog log, I found Symbios 875 is reporting > "Overlapped commands attempted." The drives connected are two IBM > Ultrastar XP (OEM from Quantum, I believe). Other way around, IBM makes them, Quantum OEM's them ... > I see some old posts referencing certain old NCR (and AICxxx) with some HP > drives (and others?) had this problem. Regarding NCR, the problem can be > side-stepped by entering options "SCS_NCR_DFLT_TAGS=" and/or > "SCSI_NCR_MAX_TAGS=0". Well, it doesn't seem either two are defined > options anymore in 4.2-S. > > Any suggestions? I have several 875's running 4.2-STABLE, no problem, I think you should check cables ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message