From owner-cvs-all@FreeBSD.ORG Sun Jun 6 02:18:09 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F15A316A4CE; Sun, 6 Jun 2004 02:18:08 -0700 (PDT) Received: from VARK.homeunix.com (ar59.lsanca2-4.27.98.47.lsanca2.dsl-verizon.net [4.27.98.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D7C843D48; Sun, 6 Jun 2004 02:18:08 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.11/8.12.10) with ESMTP id i569HwcE006371; Sun, 6 Jun 2004 02:17:58 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.11/8.12.10/Submit) id i569Hwar006370; Sun, 6 Jun 2004 02:17:58 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Sun, 6 Jun 2004 02:17:58 -0700 From: David Schultz To: src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG Message-ID: <20040606091758.GA6354@VARK.homeunix.com> Mail-Followup-To: src-committers@FreeBSD.ORG, cvs-src@FreeBSD.ORG, cvs-all@FreeBSD.ORG References: <200406060916.i569G2m2097113@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406060916.i569G2m2097113@repoman.freebsd.org> Subject: Re: cvs commit: src/sys/amd64/amd64 fpu.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2004 09:18:09 -0000 On Sun, Jun 06, 2004, David Schultz wrote: > das 2004-06-06 09:16:02 UTC > > FreeBSD src repository > > Modified files: > sys/amd64/amd64 fpu.c > Log: > Back out revision 1.150, since dwmalone reports that it causes a panic > upon startup on his machine. It would be great if someone could pick this up and devise the appropriate fix. I want to see this bug fixed, but I don't have the hardware to do amd64 kernel hacking. I'm happy to help anyone who is interested. So far I have one report that the patch I just backed out seems to work, and another that it panics on startup, so this seems to point to a CPU-specific problem. ldmxcsr is supposed to fail if an attempt is made to set unsupported bits in the CSR, but at the same time, the defaults in the AMD64 architecture manual ought to work! If this is indeed the problem, there is a simple way to work around it.