From owner-aic7xxx Fri Jun 5 06:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16882 for aic7xxx-outgoing; Fri, 5 Jun 1998 06:21:17 -0700 (PDT) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from libfw.libnet.com (firewall-user@libfw.libnet.com [208.212.129.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16636 for ; Fri, 5 Jun 1998 06:20:06 -0700 (PDT) (envelope-from Srinivas.Narendula@libnet.com) From: Srinivas.Narendula@libnet.com Received: by libfw.libnet.com; id JAA00680; Fri, 5 Jun 1998 09:19:56 -0400 (EDT) Received: from liberty3.libnet.com(159.42.50.2) by libfw.libnet.com via smap (V3.1) id xma000666; Fri, 5 Jun 98 09:19:33 -0400 Received: from by libnet.com (4.1/SMI-4.1) id AB22897; Fri, 5 Jun 98 09:21:00 EDT Received: by libnotes1.libnet.com(Lotus SMTP MTA v1.05 (274.9 11-27-1996)) id 8525661A.004984FA ; Fri, 5 Jun 1998 09:23:01 -0400 X-Lotus-Fromdomain: LIBERTY To: gmetrail@scdi.org Cc: AIC7xxx@FreeBSD.ORG Message-Id: <8525661A.0048CF8B.00@libnotes1.libnet.com> Date: Fri, 5 Jun 1998 09:22:44 -0400 Subject: Re: SCSI Timeout with Adaptec 2940UW Rev. E (Bios 1.32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerard Metrailler Jr. wrote: > > Hello, > > I hope this problem has not been resolved lately as I just subscribed to > this mailinglist ;-) > > Here is my problem. I was using a Adaptec 2940 (Bios 1.16) until > recently and ervery thing was perfect. But I just changed for an Adaptec > 2940UW Rev. E (Bios 1.32) lately when I bought a Quantum 4.5Gb UW Viking > disk. Since then, I get SCSI Timeouts when I make a big access under > Linux. Try the 5.0.18 aic7xxx driver and let me know if this still happens. There are negotiation fixes in there that might make a difference, and there is still one thing I'm looking into. Specifically, I suspect some of the cards and/or motherboard chipset setups don't properly initialize the STPWLEVEL bit in the DEVCONFIG register at startup. Currently, the driver can't set this for the BIOS because at least for motherboards the proper setting of this bit is implementation specific and we have no way of checking (I've verified this on at least one motherboard chipset product where the correct STPWLEVEL setting is 0, while on most aic7xxx based cards, the correct level is 1). This can introduce problems since the correct setting of this bit is vital to making sure that when we actually enable termination on a chipset, that the termination is *really* turned on. This could also have an impact on why some systems seem to never be able to run without timeouts and reset cycles.... -- Doug Ledford Opinions expressed are my own, but they should be everybody's. NOTE: I'm just now starting to recover from the Linux-Expo. Most importantly, I'm just now getting around to answering a lot of my email. So, if your message has lain around un-answered for many days, I apologize. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message