From owner-freebsd-stable Sun Jan 13 13:48:22 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 0A5BD37B419 for ; Sun, 13 Jan 2002 13:48:19 -0800 (PST) Received: from colt.ncptiddische.net (ppp-199.wobline.de [212.68.69.210]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g0DLmBv04073 for ; Sun, 13 Jan 2002 22:48:12 +0100 Received: from tisys.org (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g0DLnRX75502 for ; Sun, 13 Jan 2002 22:49:28 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g0DLm1l82952 for freebsd-stable@freebsd.org; Sun, 13 Jan 2002 22:48:01 +0100 (CET) (envelope-from nils) Date: Sun, 13 Jan 2002 22:48:00 +0100 From: Nils Holland To: freebsd-stable@freebsd.org Subject: VIA crahes - solved (it seems)! Message-ID: <20020113224800.A82744@tisys.org> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Operating-System: FreeBSD poison.ncptiddische.net 4.5-RC FreeBSD 4.5-RC X-Machine-Uptime: 10:38PM up 12:20, 1 user, load averages: 0.24, 0.10, 0.04 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 Hi folks, this may well be my last report on the system crashes I (and probably also other people) have seen on VIA 686B boards. Basically, ever since I did my latest CVSup on Saturday and rubilt world as well as the kernel, even the most demanding tests would not allow me to crash my machine. The strange thing is that my previous kernel was exactly from one week ago. At that time Soren's 686B fixes were already in place, and a message about the fix being applied even showed up in my dmesg.boot. So, I don't really know why this week's sources work so well, as there were basically no dramatic changes since the week before. But instead of wondering about it, I'll be happy that it works instead ;-) I'll keep my eyes on this and in case new problem should occur with any of my future (weekly) updates, I will report them. I do, however, think that the problem may now be successfully fixed *for good*, and would like to thank the people who worked on this. Special thanks to Soren, who created the fix, and of course to Matt, who worked hard on debugging my problems, when initially it seemed as if something was wrong with the NFS code. Thanks folks ;-) 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