Subject: misc/19449: Problem with ATI Rage 128 cards and xdm on 1.6K+
To: None <email@example.com>
From: None <firstname.lastname@example.org>
Date: 12/18/2002 21:52:45
>Synopsis: Problem with ATI Rage 128 cards and xdm on 1.6K+
>Arrival-Date: Wed Dec 18 19:53:00 PST 2002
>Release: NetBSD 1.6K
System: NetBSD enki.goathill.org 1.6K NetBSD 1.6K (GENERIC) #0: Tue Nov 19 12:42:29 UTC 2002 email@example.com:/autobuild/HEAD/i386/OBJ/autobuild/HEAD/src/sys/arch/i386/compile/GENERIC i386
I have seen this problem on four different i386 boxes running 1.6-current
with ATI rage gfx cards, specifically two Xpert2000 cards and on Fury MAXX:
vga1 at pci1 dev 0 function 0: ATI Technologies product 0x5446 (rev. 0x00)
(second one not available right now)
vga1 at pci1 dev 5 function 0: ATI Technologies Rage Fury MAXX AGP 4x (TMDS) (rev. 0x00)
Five different motherboards :
Athlons : one MSI Dual Athlon, one Epox 8k5a2+, one Epox 8kta3+
K6-2 : one EP-MVP3G-M, one Shuttle 591P
All running different 1.6-current builds from releng binary distributions,
as well as diffrent pkg builds for kde3, etc.
Typically, but not always, after an initial xdm session, if Ctrl-Alt
F<x> or Ctrl-Alt -/+ to select wscons screens/screen resolutions,
or sometimes simply logging out, either xdm or an xdm child process
hangs. The hung process almost (but not quite) always prevents
xdm from restarting, even if kill -9 is used. All keyboard inputs
are hung and the screen sometimes develops a banding in the lower
quadrant and a static cursor in the upper left-hand cell of the
screen. Shutdown typically cannot kill the hung process and the
system has to be reset and rebooted to recover. Kde3 may be involved,
as I often find hung kde session processes when I login from another
host to investigate.
This problem only started since 1.6-current (1.6K I think). Several
of the machines have been in use for about 2-2.5 years with no
Certain ATI Rage 128 cards are the only ones I see that exhibit
this problem. Two G200's, another Xpert2000:
vga1 at pci1 dev 5 function 0: ATI Technologies Rage 128 GL AGP 2x (rev. 0x00)
vga1 at pci1 dev 0 function 0: ATI Technologies Radeon 7500 (rev. 0x00)
two GeForce's, and some older gfx cards do not exhibit this problem.
Use xdm, login to kde3, logout, login and switch to a wscons console
using Ctrl/Alt-F2 or such.
Use something other than a Rage 128 gfx card. Problem goes away completely.
xdm & xdm child processes hang with some ati gfx cards