From owner-aic7xxx Mon Feb 15 09:48:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06274 for aic7xxx-outgoing; Mon, 15 Feb 1999 09:48:45 -0800 (PST) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from lacrosse.redhat.com (lacrosse.redhat.com [207.175.42.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06269 for ; Mon, 15 Feb 1999 09:48:43 -0800 (PST) (envelope-from dledford@redhat.com) Received: from redhat.com (dledford@kabal.redhat.com [207.175.42.20]) by lacrosse.redhat.com (8.8.7/8.8.7) with ESMTP id MAA15277; Mon, 15 Feb 1999 12:48:31 -0500 Message-ID: <36C85E09.34A9583@redhat.com> Date: Mon, 15 Feb 1999 12:48:57 -0500 From: Doug Ledford Organization: RedHat Softwarem, Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth P. Persing" CC: "aic7xxx@FreeBSD.ORG" Subject: Re: aic7xxx v. 5.1.11 on 2.2.1 broken for plain old vanilla 2940. References: <36C7147D.B9CD7E69@intac.com> Content-Type: multipart/mixed; boundary="------------F13EF8AF24D83A528A695247" Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------F13EF8AF24D83A528A695247 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Kenneth P. Persing" wrote: > > Hey folks, > If I have missed something obvious, please let me know (like if > there has been a fundamental change in the way the aic7xxx driver works > between 5.1.10 and 5.1.11, and the it is necessary to pass it a command > from the kernel, or the like). However, I am running a plain old 2940 > with three scsi harddrives. Two Seagate ST32430N 2 gig harddives, and > one Connor CFP2105S. It also has a tandberg tape drive, a plextor 12x, > and an hp cd writer. I've been using all the 2.2.0 pre kernels, and > everything has worked fine. After I got 2.2.1, before compiling it, I > upgraded the aic7xxx driver from 5.1.10 to 5.1.11. Everything began > booting fine. It mounted all the drives on my system, but after initd > loaded, and it entered runlevel 5, when it began to load the system > loggers the scsi bus froze. The led hooked up to the 2940 went on solid, > but the HD lights were all off. I then entered an endless loop of scsi > timeout, and attempted bus resets. > Believing this was a problem with my hardware, I then began checking > the termination on all of my devices, the termination was all correct. I > then disconnected every device but one hard drive (I turned on the > termination of that drive and put in last on the cable) Time out errors > still plagued me. I've done these test on both a 2940 with bios > revision 1.11 and 1.16, same problem. However, previously, running 5.1.9 > everything has worked great, similarly when I compiled the 2.2.1 kernel > without upgrading the aic driver from 5.1.10 to 5.1.11, it worked also. > This all leads me to believe that something has changed between > revisions 5.1.10 and 5.1.11 that messes up the support for the plain old > 2940. > > If you have any questions about my system, or if there are any other > tests you would like me to run to help fix this problem, please let me > know. Try the attached patch. If it helps, then please send me the output of "cat /proc/pci" on your system. -- Doug Ledford Opinions expressed are my own, but they should be everybody's. --------------F13EF8AF24D83A528A695247 Content-Type: text/plain; charset=us-ascii; name="test.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="test.patch" --- linux/drivers/scsi/aic7xxx.c.old Mon Feb 15 12:46:41 1999 +++ linux/drivers/scsi/aic7xxx.c Mon Feb 15 12:47:36 1999 @@ -9219,7 +9219,7 @@ * on the 789x cards. Also, read the SEEPROM as well. */ aic_outb(temp_p, (aic_inb(temp_p, DSCOMMAND0) | - CACHETHEN | MPARCKEN) & ~DPARCKEN, + DPARCKEN | MPARCKEN) & ~CACHETHEN, DSCOMMAND0); case AHC_AIC7895: aic7xxx_load_seeprom(temp_p, &sxfrctl1); --------------F13EF8AF24D83A528A695247-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message