Red Hat Bugzilla – Bug 24860
X server (voodoo 3) dies
Last modified: 2007-04-18 12:30:53 EDT
If I leave the X server running and as the active virtual console, it will
lock after some random period of time. Like hours. The screensaver is
active when this happens. If I leave a text vc active, I get some error
that I forgot to write down on the console I started X from. If X was the
active console the machine is dead.
Server is whatever I got from RH7, which I got from the Dummies book.
This is pissing me off. The old server I used on RH6 ( I got the XF3.xxxx
server from 3dfx) would freeze during use occasionaly, I was hoping XF4
would behave better.
Is this an AGP or PCI card? How much RAM, of what type?
Can you do a file attach above of the entire output of your
X server's error log? Please include any details that might
help track this down.
Have you tried the latest Rawhide RPM's at all?
Also, could you do a query on all voodoo bugs in bugzilla and see if your
symptoms match anyone else's problems with these cards?
Try disabling the screen saver and let me know what happens overnight.
OK, no rawhide RPMS, AGP card, haven't seen anything similar searching for
In the good news department, disabling the screensaver leads to :
9:58pm up 4 days, 11:29, 3 users, load average: 1.12, 1.15, 1.09
Since I haven't rebooted, I haven't recalled the specifics of the voodoo3. It is
a pretty basic one though.
Created attachment 8540 [details]
Your log doesn't show any crash occuring. Can you attach a log from
after a crash/hang? Check /var/log/messages as well, it could be a
kernel hang with DRI. Attach both logs please.
Also, make sure if you use 3D that you are using 16bit depth. 8/24/32
does not work I do not believe.
Yep, Voodoo 3 does 3D at 16bpp (which you're using) and Voodoo5 at 16/32bpp.
Can you attach your config file?
Unable to reproduce, closing bug due to lack of required
requested information in reasonable time frame.