From owner-freebsd-bugs Mon Oct 30 5:50:10 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3ACEE37B4FE for ; Mon, 30 Oct 2000 05:50:06 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA10884; Mon, 30 Oct 2000 14:48:44 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200010301348.OAA10884@freebsd.dk> Subject: Re: i386/22240: unstable UDMA on Iwill VD133PL v1.6 (Apollo MVP3, IDE rev 0x10) In-Reply-To: <200010301335.FAA12296@kamidake.apricot.com> from "Todd P. Whitesel" at "Oct 30, 2000 05:35:47 am" To: toddpw@apricot.com (Todd P. Whitesel) Date: Mon, 30 Oct 2000 14:48:43 +0100 (CET) Cc: ache@nagual.pp.ru ([______ ______]), freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Todd P. Whitesel wrote: > > I end up with ASUS CUSL2 (815E) motherboard witch works fine with the same > > memory/processor was not working with VIA > > Same here. I have been testing a pair of CUSL2's for over a day with no > problems whatsoever. > > Is there a PR category for "known buggy hardware" ??? I just had a mail from somebody that solved a VIA problem by overclocking the FSB, he found that in some FAQ somewhere, go figure..... Again I have run all kinds of tests on the VIA's I have access to, and none of themm have shown any problems, it could be bad MB designs too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message