From owner-freebsd-current@FreeBSD.ORG Wed Aug 20 07:23:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 286BD16A4BF for ; Wed, 20 Aug 2003 07:23:01 -0700 (PDT) Received: from godel.mtl.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 635FF43FB1 for ; Wed, 20 Aug 2003 07:23:00 -0700 (PDT) (envelope-from bmilekic@technokratis.com) Received: from godel.mtl.distributel.net (localhost [127.0.0.1]) h7KANKr2074411 for ; Wed, 20 Aug 2003 10:23:20 GMT (envelope-from bmilekic@technokratis.com) Received: (from bmilekic@localhost) by godel.mtl.distributel.net (8.12.9/8.12.9/Submit) id h7KANKof074410 for current@freebsd.org; Wed, 20 Aug 2003 10:23:20 GMT X-Authentication-Warning: godel.mtl.distributel.net: bmilekic set sender to bmilekic@technokratis.com using -f Date: Wed, 20 Aug 2003 10:23:20 +0000 From: Bosko Milekic To: current@freebsd.org Message-ID: <20030820102320.GA74358@technokratis.com> References: <20030811100549.GA33392@technokratis.com> <010801c36023$6198c6b0$be0fa8c0@MJOHNSTON> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <010801c36023$6198c6b0$be0fa8c0@MJOHNSTON> User-Agent: Mutt/1.4.1i Subject: Re: 5.1, Data Corruption, Intel, Oh my! [patch] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Aug 2003 14:23:01 -0000 All of the Email I have received from the many people testing this patch (THANKS!!!) has been positive so far with respect to the data corruption problem. There remains one outstanding issue to be resolved prior to committing this and due to the nature of the problem, it's been taking a little longer for me to fix it. The issue has to do with running the patch in combination with APM (I am told that the APM problem actually existed in the past as well but was somehow only apparent when running with DISABLE_PSE). I *think* that the problem has to do with our bios code switching to the page 0 stack which somehow leads to problems when this patch is applied (or when stock -current is used but with DISABLE_PSE). Because I don't have any machine that use the APM code, debugging the problem consists of me changing something, then providing a patch to someone with APM, and then waiting for the results. This is a time-consuming process, but as soon as the problem is addressed, I will commit the changes. Thanks to everyone who has helped test this so far. Regards, -- Bosko Milekic * bmilekic@technokratis.com * bmilekic@FreeBSD.org TECHNOkRATIS Consulting Services * http://www.technokratis.com/