I have done a little bit more testing on my Cats running X
and whatever the problem is, it appears to be in the NetBSD
kernel. I telnet'ed in and ran 'top' whilst trying to start X
in another session. The telnet session ran for about five
seconds or so after I typed in 'startx' and then the machine
locked up solid. It would not respond to a 'ping' and the only
way out was to hit reset.

Here are some messages from the Xwindows log file
(XFree86.0.log) concerning the driver:

	[0] -1	0	0x00000000 - 0xffffffff (0x0) MX[B]
(--) PCI:*(0:10:0) S3 Inc. ViRGE/DX or /GX rev 1, Mem @ 0x08000000/26,
  BIOS @ 0x0c000000/16

(II) LoadModule: "s3virge"
(II) Loading /usr/X11R6/lib/modules/drivers/s3virge_drv.o
(II) Module s3virge: vendor="The XFree86 Project"
	compiled for 4.5.0, module version = 1.8.6
	Module class: XFree86 Video Driver
	ABI class: XFree86 Video Driver, version 0.8
(II) LoadModule: "mouse"
(II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="The XFree86 Project"
	compiled for 4.5.0, module version = 1.0.0
	Module class: XFree86 XInput Driver
	ABI class: XFree86 XInput driver, version 0.5
(II) S3VIRGE: driver (version 1.8.6) for S3 ViRGE chipsets: virge, 86C325,
	virge vx, 86C988, virge dx, virge gx, 86C375, 86C385, virge gx2,
	86C357, virge mx, 86C260, virge mx+, 86C280, trio 3d, 86C365,
	trio 3d/2x, 86C362, 86C368
(II) Primary Device is: PCI 00:0a:0
(--) Assigning device section with no busID to primary device
(--) Chipset virge dx found

(II) S3VIRGE(0): initializing int10
(II) S3VIRGE(0): No legacy BIOS found -- trying PCI
(II) Truncating PCI BIOS Length to 32768

The 'Truncating PCI BIOS' message is the last one in the log.
I guess that there might be more messages in a buffer that were
not written to disk and so were lost when the Kernel froze.

Should I send-pr this?

Dave Daniels