Date: Sat, 8 May 1999 02:37:45 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: eagle <eagle@eagle.phc.igs.net> Cc: Lee Cremeans <lcremeans@erols.com>, hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: G200 GLX and SIGFPU Message-ID: <19990508023745.20308@hydrogen.nike.efn.org> In-Reply-To: <Pine.BSF.3.96.990508042226.1394B-100000@eagle.phc.igs.net>; from eagle on Sat, May 08, 1999 at 04:24:03AM %2B0000 References: <19990508050945.A4995@erols.com> <Pine.BSF.3.96.990508042226.1394B-100000@eagle.phc.igs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
eagle scribbled this message on May 8: > > > 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. > > I've seen similar error messages with mesa in particalur in relation to > flightgear, I don't have a solution as of yet though. use fpsetmask to mask the SIGFPE's that you don't want... usually this is all of them as FreeBSD has them turned on my default while other OS's don't... if you do a search of the mailing lists on SIGFPR and fpsetmask your bound to turn up many postings on the subject... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990508023745.20308>