From owner-freebsd-hackers Mon May 13 10: 5:34 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from server.rucus.ru.ac.za (server.rucus.ru.ac.za [146.231.115.1]) by hub.freebsd.org (Postfix) with SMTP id B130C37B40E for ; Mon, 13 May 2002 10:05:05 -0700 (PDT) Received: (qmail 87127 invoked from network); 13 May 2002 17:05:01 -0000 Received: from shell-fxp1.rucus.ru.ac.za (HELO shell.rucus.ru.ac.za) (10.0.0.1) by server.rucus.ru.ac.za with SMTP; 13 May 2002 17:05:01 -0000 Received: (qmail 81514 invoked by uid 1040); 13 May 2002 17:05:01 -0000 Date: 13 May 2002 17:05:01 -0000 Message-ID: <20020513170501.81513.qmail@shell.rucus.ru.ac.za> From: David =?ISO-8859-1?Q?Sieb=F6rger?= To: freebsd-hackers@freebsd.org Subject: Re: What hardware do you use ? Organization: Rhodes University Computer Users' Society In-Reply-To: <20020513054139.GA85170@klapaucius.zer0.org> User-Agent: tin/1.5.11-20020130 ("Toxicity") (UNIX) (FreeBSD/4.5-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gregory Sutter wrote: > On 2002-05-11 10:49 +0800, Dinesh Nair wrote: >> On Fri, 10 May 2002, Doug White wrote: >> >> > usually have onboard everything, including dual fxp's nowadays. But they >> > have the ServerWorks curse. >> > . Tyan makes some interesting stuff, but as with all ServerWorks based >> > stuff, stay far, far away from the base ATA33 controller. Even the cheap >> >> what serverworks curse ? i may not have been aware of an issue here. could >> someone please let me know about this ? > > The Serverworks chipsets max out at ATA/33. Not very fast. That's hardly the worst of it. The ServerWorks OSB4 ATA controller has been known to cause data corruption with Seagate drives. I've just had a very frustrating experience with this problem on an Intel STL2-based 4.6-PRERELEASE system which experienced segfaults and file system corruption. We tested the memory, checked the PSU, heat in the system, replaced the IDE cable, replaced the drive (unfortunately with another Seagate!) before I heard about this issue. My testing showed that the problem only occurred while writing to disk using UltraDMA. This post on the Linux kernel list gives further details: http://marc.theaimsgroup.com/?l=linux-kernel&m=100188302723186&w=2 -- David Siebörger drs@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message