From owner-freebsd-stable Tue Jan 15 9:31: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 8138F37B405 for ; Tue, 15 Jan 2002 09:30:58 -0800 (PST) Received: from colt.ncptiddische.net (ppp-239.wobline.de [212.68.69.250]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g0FHUjw06692; Tue, 15 Jan 2002 18:30:45 +0100 Received: from tisys.org (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g0FHW9X85421; Tue, 15 Jan 2002 18:32:10 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g0FHVDs96400; Tue, 15 Jan 2002 18:31:13 +0100 (CET) (envelope-from nils) Date: Tue, 15 Jan 2002 18:31:13 +0100 From: Nils Holland To: Brady Montz Cc: freebsd-stable@FreeBSD.ORG Subject: Re: VIA crahes - solved (it seems)! Message-ID: <20020115183113.A96245@tisys.org> Mail-Followup-To: Brady Montz , freebsd-stable@FreeBSD.ORG References: <20020113224800.A82744@tisys.org> <3C42F7E1.3040508@magpage.com> <200201152200.g0FM0lT28843@mail.hydrologue.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200201152200.g0FM0lT28843@mail.hydrologue.com>; from bradym@mail.hydrologue.com on Tue, Jan 15, 2002 at 02:00:47PM -0800 X-Operating-System: FreeBSD jodie.ncptiddische.net 4.5-RC FreeBSD 4.5-RC X-Machine-Uptime: 6:19PM up 8:38, 1 user, load averages: 0.14, 0.04, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 15, 2002 at 02:00:47PM -0800, Brady Montz stood up and spoke: > > Sadly, as of yesterday's version of the source, my crashes still > persist. I have the VIA 586 chipset. The VIA 586 chipset (I guess you are referring to something like the Apollo MVP3) is not affected by the data corruption bug that is present on the 686B Southbridge. In fact, I have a MVP3 based machine myself and it runs fine. I don't know about any known problems with this chipset either. I guess that your problem may be caused by some hardware problem. It may be the RAM, the CPU, or even some flaw in your board. Extensive hardware testing will probably be the best method to try to track down the problem. I know that it can be time consuming, but it's basically best to do it before assuming that there's something wrong with the software ;-) Greetings Nils -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message