From owner-freebsd-current Sat Oct 5 12:12:51 2002 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 7E29A37B401; Sat, 5 Oct 2002 12:12:50 -0700 (PDT) Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id F21E443E42; Sat, 5 Oct 2002 12:12:49 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.3/8.12.1) with ESMTP id g95JCmC7014793; Sat, 5 Oct 2002 15:12:48 -0400 (EDT) Date: Sat, 5 Oct 2002 15:12:48 -0400 (EDT) From: Daniel Eischen To: Peter Wemm Cc: "Brian F. Feldman" , German Tischler , freebsd-current@FreeBSD.ORG, Daniel Eischen , Jonathan Mini Subject: Re: SSE In-Reply-To: <20021005181632.28EC92A896@canning.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 5 Oct 2002, Peter Wemm wrote: > "Brian F. Feldman" wrote: > > "Brian F. Feldman" wrote: > > > German Tischler wrote: > > > > Hi. > > > > > > > > I can panic my current system compiled from sources of yesterday > > > > by just starting mozilla or ogg123 if I don't include > > > > options CPU_DISABLE_SSE > > > > in my kernel configuration file. Is anyone else seeing any > > > > SSE code related problems ? (P III based SMP system here) > > > > > > I seem to have the same problem on my currently-UP Athlon system, whether o > r > > > not SSE is enabled; I'm trying to track it down... > > > > On further reflection, this DEFINITELY has to do with the work done on > > npx(4)/signals/etc. in the past week. I _must_ be getting a GPF because the > > fpu state that it's attempting to restore is corrupt (i.e.: the control word > > is incorrect), so something is not being initialized somewhere that it used > > to be, or is being initialized incorrectly. > > The last few commits to machdep.c bother me, rev 1.539 in particular. > > If you are in a position to be able to quickly test it, it would be great > to know if backing out the last few changes fixes this, and which change in > particular. There have been two commits since 1.539; what version of machdep.c is being used? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message