Red Hat Bugzilla – Bug 76763
XF86 deadlocks with Voodoo 5500 PCI & DRI
Last modified: 2007-04-18 12:47:57 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 Description of problem: When running 'startx', the screen blanks and the machine deadlocks completely (keybd LEDs do not respond, network ping does not respond). This happens when DRI is enabled (and it is enabled by default). Removing the "DRI" section at the top of /etc/X11/CF86Config and also commenting out the 'Load "dri"' line in the Module section of the same file allows X to start successfully. This bug has been around since at least RH 7.3. Version-Release number of selected component (if applicable): XFree86-4.2.0-72 How reproducible: Always Steps to Reproduce: 1. Just run 'startx' with the default XF86Config file provided by the RH 8.0 installer. Actual Results: System deadlocks as described. Expected Results: X desktop should have eventually appeared. Additional info: Hardware configuration is a little 'interesting': 2 CPU SMP P2-450 XEON Intel 440 GX chipset PCI Voodoo 5500 card --note PCI, not AGP
Please attach your X config file, log file, and the output of the following: lspci -vn cat /proc/version
Created attachment 82464 [details] Original XF86Config file, machine deadlocks when using this config
Created attachment 82465 [details] Diff showing changes to original config file (disabling DRI) --X starts ok with this config
Created attachment 82466 [details] `lspci -vn` output on machine exhibiting deadlock
Created attachment 82467 [details] Info from /proc/version
Cannot post X log file because machine deadlocks before any data gets written to the log. If you have a suggestion on how to work around this, I'll give it a shot...
Please upgrade to Fedora Core 2 or later, and if this issue turns out to still be reproduceable, please file a bug report in the X.Org bugzilla located at http://bugs.freedesktop.org in the "xorg" component. Once you've filed your bug report to X.Org, if you paste the new bug URL here, Red Hat will continue to track the issue in the centralized X.Org bug tracker, and will review any bug fixes that become available for consideration in future updates.