From owner-freebsd-hackers Sat May 8 2:24:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201]) by hub.freebsd.org (Postfix) with ESMTP id B6D9E153AB; Sat, 8 May 1999 02:24:34 -0700 (PDT) (envelope-from eagle@eagle.phc.igs.net) Received: by eagle.phc.igs.net (Postfix, from userid 1003) id 69C471897; Sat, 8 May 1999 04:24:03 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by eagle.phc.igs.net (Postfix) with SMTP id 63E1A38; Sat, 8 May 1999 04:24:03 +0000 (GMT) Date: Sat, 8 May 1999 04:24:03 +0000 (GMT) From: eagle To: Lee Cremeans Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: G200 GLX and SIGFPU In-Reply-To: <19990508050945.A4995@erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 May 1999, Lee Cremeans wrote: > I'm playing with the GLX (server-side OpenGL-to-hardware interface) drivers > for the Matrox G200 2D/3D chip (very good chip, btw), and the good news is > that they work in FreeBSD. > > Mostly. > > My problem is that sometimes, the driver (which loads into a XFree86 3.3.x > server as a module, and also comes with a Mesa-based libGL.so) likes to kill > the X server with a SIGFPU at a certain point in the code (in the hardware > pixel/texel-smoothing routines, to be exact). When I run the SGI logo.c > demo, it will kill the server, eventually, with SIGFPU, and when I play > q3test through the driver, it'll drop the server at or near the same place > in the code as logo.c. This doesn't happen when Mesa itself is doing the > rendering in software. > > The reason I'm asking here on the FreeBSD lists about this is because I > remember some rumblings a while back about differences in the way FreeBSD > and Linux handle the FPU, and whether they'd be pertinent to this. It'd > appear, from what I've seen, that all development on these drivers (until > now) has been done on Linux, so a lot of these SIGFPU issues would be > "invisible" to them. > > If anyone wants a look at the code, the CVS information is at > > http://lists.openprojects.net/mailman/listinfo/g200-dev > > and I can also get crash dumps and backtraces for anyone who wants them. > > -lee I've seen similar error messages with mesa in particalur in relation to flightgear, I don't have a solution as of yet though. Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message