Subject: Re: glxgears
To: NetBSD port-sparc64 mailing list <>
From: Jochen Kunz <>
List: port-sparc64
Date: 08/23/2007 17:29:16
On Sun, 19 Aug 2007 22:13:07 -0400
Michael Lorenz <> wrote:

> in recent -current glxgears seems to trigger a crash of the Xserver -=20
> used to work about a year ago. Is it just me or does that happen to=20
> anyone else too?
Same here. I start glxgears and I am back at the XDM login.

[jkunz@Kriggle jkunz]$ uname -a                                            =
NetBSD Kriggle 4.99.25 NetBSD 4.99.25 (GENERIC) #0: Mon Jul 23 01:17:42 PDT=
 2007  builds@wb34:/home/builds/ab/HEAD/sparc64/200707220002Z-obj/home/buil=
ds/ab/HEAD/src/sys/arch/sparc64/compile/GENERIC sparc64

=46rom dmesg:
mainbus0 (root): SUNW,Ultra-60
cpu0 at mainbus0: SUNW,UltraSPARC-II @ 360.011 MHz, UPA id 0
cpu0: 32K instruction (32 b/l), 16K data (32 b/l), 4096K external (64 b/l)
ffb0 at mainbus0 addr 0xfebc0000: Elite3D, model SUNW,XXX-XXXX, dac 10
ffb0: attached to /dev/fb0
wsdisplay0 at ffb0 kbdmux 1: console (sunffb, sun emulation)
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 1-3 added (sunffb, sun emulation)

(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing fr=
om list!

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 4.  Server aborting
FatalError re-entered, aborting
Caught signal 11.  Server aborting