From owner-freebsd-stable Wed Apr 5 12:27:35 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 8F47337BA38 for ; Wed, 5 Apr 2000 12:27:19 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id VAA06739; Wed, 5 Apr 2000 21:08:34 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200004051908.VAA06739@zibbi.mikom.csir.co.za> Subject: Re: How stable is the ATA code? In-Reply-To: <20000405131452.A6538@evil.2y.net> from Coleman Kane at "Apr 5, 2000 01:14:52 pm" To: cokane@one.net (Coleman Kane) Date: Wed, 5 Apr 2000 21:08:34 +0200 (SAT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm pretty sure the problem is not the disks in my case. I have tried a Seagate ST36531A and a Samsung SW0434A. Both do work without a problem in another motherboard with a different chipset. Here are a few reasons why it can work for you and not some others: Maybe VIA changed something in the chip and didn't change the number of the chip. (On the 596 they only changed the revision number and added 66M DMA if I understand the code correctly.) Maybe the ata driver don't configure all registers and assume the BIOS will do some and the BIOSes do it different. Maybe the motherboard designers screwed up somewhere which make 33M DMA not work on those boards. John -- John Hay -- John.Hay@mikom.csir.co.za > Yeah, I saw those. I have not noticed any problems with 4.x. The MVP3 is the > 82c586B. I have updated on about a bi-daily basis with the kernel and have not > noticed any corruption or other problems. Many people were blaming the > controller, but it is probably rooted in the mix of their hard drives and the > MVP3 I'll bet. One person mentioned using a JTS Champ hard drive. These drives > were all recalled osme time ago because of faulty circuitry...and the cheap end > of the MAxtor line has always caused problems for me, no matter what the > controller. Cheap seagates were also troublesome, especially the LP drives. > > --cokane > > Warner Losh had the audacity to say: > > > > In message <20000405024521.B4835@evil.2y.net> Coleman Kane writes: > > : am using ata with an FIC-VA503+ (VIA Apollo MVP3) mobo and a WD Expert > > > > There have been reports that this is massive unstable with the current > > (4.x and 5.x) code in DMA mode. I may have confused this with the VIA > > 82C586B chipset in other mail. > > > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message