From owner-aic7xxx Sat Apr 24 11:11:49 1999 Delivered-To: aic7xxx@freebsd.org Received: from lacrosse.redhat.com (lacrosse.redhat.com [207.175.42.154]) by hub.freebsd.org (Postfix) with ESMTP id 8DCAF15062 for ; Sat, 24 Apr 1999 11:11:45 -0700 (PDT) (envelope-from dledford@redhat.com) Received: from redhat.com ([10.0.0.25]) by lacrosse.redhat.com (8.8.7/8.8.7) with ESMTP id OAA25743; Sat, 24 Apr 1999 14:11:41 -0400 Message-ID: <37220959.32A95D39@redhat.com> Date: Sat, 24 Apr 1999 14:11:37 -0400 From: Doug Ledford Organization: Red Hat Software X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.2.5 i686) X-Accept-Language: en MIME-Version: 1.0 To: Venkatesh Krishnamurthi Cc: nelson@imat.com, AIC7xxx@FreeBSD.ORG Subject: Re: Adaptec 2940U2W and new 2.110 bios References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Venkatesh Krishnamurthi wrote: > > > Doug Ledford wrote: > > [ stuff deleted ] > > > I think you need to find out how/why you aren't using a kernel with the > > 5.1.15 driver and then update to it and your problem should go away. > > The latest kernel (2.2.6) still uses the 5.1.10 version of the aic7xxx > driver. As fas as I can tell, the 5.1.15 version still has not made it > into the "official" kernel source. That's not the point. Read his email. In his email he said he was using 5.1.15 but the logs he attached to the email with the reset condition clearly showed he was using 5.1.14. There was a discrepancy there and that's what I was pointing out. Further, the exact log he attached to his email is one that I could have told you before hand would happen with 5.1.14 and the IBM drive he has in his computer. What version of the aic7xxx driver is in Linus' official kernel tree is irrelevant when someone says they are using 5.1.15 and the logs instead show 5.1.14. -- Doug Ledford Opinions expressed are my own, but they should be everybody's. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message