freebsd stable - Mar 2004 - Possible regression in -STABLE with DRI/OpenGL apps

I had been running a 4.9-STABLE build from the middle of 2004 February 
or so, up until I decided to upgrade to the latest yesterday. Now, the 
game Critical Mass (/usr/ports/games/criticalmass, executable is named 
"critter") crashes my X server every time with a signal 6 (Abort
trap).
Unfortunately it appears my X server isn't built with debugging symbols 
(yet), but I thought I'd ask if anyone else has noticed a similar 
problem?

VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6974 (c0006974)
VESA: Matrox Graphics Inc.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 7 entries at 0xc00f82b0
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <AMD-751 host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
agp0: <AMD 751 host to AGP bridge> mem 
0xeedff000-0xeedfffff,0xec000000-0xedffffff at device 0.0 on pci0
pcib1: <AMD-751 PCI-PCI (1x/2x AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
drm0: <Matrox G400/G450 (AGP)> mem 
0xef000000-0xef7fffff,0xefefc000-0xefefffff,0xe8000000-0xe9ffffff irq 
11 at device 5.0 on pci1
info: [drm] AGP at 0xec000000 32MB
info: [drm] Initialized mga 3.1.0 20021029 on minor 0

-- 
Shawn K. Quinn

> I had been running a 4.9-STABLE build from the middle of 2004 February 
> or so, up until I decided to upgrade to the latest yesterday. Now, the 
> game Critical Mass (/usr/ports/games/criticalmass, executable is named 
> "critter") crashes my X server every time with a signal 6 (Abort
trap).
> Unfortunately it appears my X server isn't built with debugging symbols
> (yet), but I thought I'd ask if anyone else has noticed a similar 
> problem?
> 
> VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6974 (c0006974)
> VESA: Matrox Graphics Inc.
> Pentium Pro MTRR support enabled
> md0: Malloc disk
> Using $PIR table, 7 entries at 0xc00f82b0
> npx0: <math processor> on motherboard
> npx0: INT 16 interface
> pcib0: <AMD-751 host to PCI bridge> on motherboard
> pci0: <PCI bus> on pcib0
> agp0: <AMD 751 host to AGP bridge> mem 
> 0xeedff000-0xeedfffff,0xec000000-0xedffffff at device 0.0 on pci0
> pcib1: <AMD-751 PCI-PCI (1x/2x AGP) bridge> at device 1.0 on pci0
> pci1: <PCI bus> on pcib1
> drm0: <Matrox G400/G450 (AGP)> mem 
> 0xef000000-0xef7fffff,0xefefc000-0xefefffff,0xe8000000-0xe9ffffff irq 
> 11 at device 5.0 on pci1
> info: [drm] AGP at 0xec000000 32MB
> info: [drm] Initialized mga 3.1.0 20021029 on minor 0
My FreeBSD 4.9-STABLE was updated 26 February 2004. It runs Criticall Mass
built today using ports with XFree86 4.3.0 (X server updated to 4.3.99.15)
correctly.

VESA: v2.0, 65536k memory, flags:0x1, mode table:0xc0356582 (1000022)
VESA: ATI RADEON 9200
agp0: <Intel 82443BX (440 BX) host to PCI bridge> mem
0xe8000000-0xebffffff at device 0.0 on pci0
drm0: <ATI Radeon RV280 9200 SE> port 0xd000-0xd0ff mem
0xed000000-0xed00ffff,0xd8000000-0xdfffffff at device 0.0 on pci1
info: [drm] AGP at 0xe8000000 64MB
info: [drm] Initialized radeon 1.8.0 20020828 on minor 0

I plan to update to recent STABLE today and will report how it will run.

NB: I've patched device radeondrm to enable DRI.

Eugene Grosbein

On Saturday 2004 March 06 01:03, Shawn K. Quinn wrote:
> I had been running a 4.9-STABLE build from the middle of 2004
> February or so, up until I decided to upgrade to the latest
> yesterday. Now, the game Critical Mass
> (/usr/ports/games/criticalmass, executable is named "critter")
> crashes my X server every time with a signal 6 (Abort trap).
> Unfortunately it appears my X server isn't built with debugging
> symbols (yet), but I thought I'd ask if anyone else has noticed a
> similar problem?
It's worse than I thought. Heroes also caused the X server to crash upon 
exit; this could mean any SDL program will cause the X server to croak.

-- 
Shawn K. Quinn