Red Hat Bugzilla – Bug 144867
Xwindows locks with radeon DRI enabled
Last modified: 2015-01-04 17:15:20 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 Description of problem: When starting Xorg (Xwindows) the computer screen will lock, and can not be brought down (ctrl-alt-backspace does nothing, can't switch screens either). In the 2.6.10 kernel, the screen comes up all funky looking, with a X windows mouse cursor that responds to the touchpad movement. The system stops at this point and though the mouse continues to move fine, there is no response to the keyboard (cannot ctrl-alt-backspace or reboot via keyboard). It is still possible to ssh into the machine and poweroff the system, but kill commands to the xserver seem to fail to return the screen to the console. In the 2.6.9 kernel, the screen stays blank and the entire system locks. Removing the "load DRI" line clears the problem and normal Xwindows functionality returns. Version-Release number of selected component (if applicable): kernel-2.6.9-1.667, kernel-2.6.10-1.737_FC3, xorg-x11-6.8.1-12.FC3.21 How reproducible: Always Steps to Reproduce: 1. run startx with radeon driver and dri enabled Additional info: ATI Radeon Mobility M6 LY
Alright I tried re-installing and doing all updates except the xorg related ones. Using kernel-2.6.10-1.741_FC3 and the older xorg-x11 that comes with FC3 initialy I still get the same screen lock. BUT the 2.6.9-1.667 does not lock the screen and it works normally. So something in both the kernel-2.6.10-1.741_FC3 package and the xorg-x11-6.8.1-12.FC3.21 independently cause this lock up (system can still be rebooted, vie alt-ctl-del, but that's about it). I'll experiement further, but it's a slow process.
Confirmed the following: kernel-2.6.10-1.741_FC3 + xorg-x11-6.8.1-12.FC3.21 + DRI = Locks kernel-2.6.10-1.741_FC3 + xorg-x11-6.8.1-12.FC3.21 - DRI = Works kernel-2.6.10-1.741_FC3 + xorg-x11-6.8.1-12 + DRI = Locks kernel-2.6.10-1.741_FC3 + xorg-x11-6.8.1-12 - DRI = Works kernel-2.6.9-1.667 + xorg-x11-6.8.1-12.FC3.21 = Works kernel-2.6.9-1.667 + xorg-x11-6.8.1-12 = Works Not sure why the 2.6.9 kernel is working now, and not before. The 2.6.10 now seems to be the only common factor in the lock ups. Will experiment more.
Created attachment 112845 [details] Photo of locked display
This problem still occurs in the 2.6.11-1.7_FC3.i686.rpm from FC3 test. At this point any kernel after 2.6.9 with DRI enabled causes the xserver to fail to load correctly and to lock out keyboard actions. The image displayed is a distored image of the systems boot graphic (ie during bios startup). The mouse still responds and the Xwindows X cursor is present (though not the window mangers normal arrow cursor). So you can move the mouse, see it move, but no clicks do anything, and you can't switch consoles, or force the xserver to shutdown. The system fails to respond to the keyboard. I can ssh in from a remote system and cleanly shutdown the system. There are no error messages in the xorg log files. The last messages are the mouse/touchpad being initialized and that's it (as expected). I've included a camera shot of the laptops screen after the xserver has failed (posted above). I'm currently trying to compile a stock 2.6.11-6 kernel to test with and see if this is an upstream issue.
Also forgot to add this is on a Sharp MM20 Laptop (based on a Transmeta Efficeon processor). I also found the following bug which seems to have the same issue: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152312
I have confirmed that this is repeatable with a stock 2.6.11.6 kernel downloaded from kernel.org. All other systems seem to start up fine, but the same messed up image, moving mouse pointer and unresponsive keyboard as above is present.
Just confirmed, it's still broken with kernel 2.6.11-1.14_FC3. Just tried the update, and it locks the same way. Can still ssh in remotely and cleanly shutdown.
Ok, I tried something new, and narrowed the issue down to something with the AGP driver used. By using Option "BusType" "PCI" and forcing the xorg to use the AGP card as a PCI card, everything works as expected. The only issue being that it is slower than Using AGP mode. I also filed a bug upstream with kernel.org since I found the same issue with a 2.6.11.6 kernel I compiled from them. That bug can be found here: http://bugzilla.kernel.org/show_bug.cgi?id=4513
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you.
Unfortunately, the problem persists with the latest kernel. Currently running kernel-2.6.12-1.1372_FC3 with xorg-x11-6.8.2-1.FC3.13 on Fedora Core 3. Same issue as before, still get the moving mouse on a black screen with screwed up images at the very top. No keyboard response, but the system isn't locked, can ssh in and cleanly shutdown the system. With Option "BusType" "PCI" set the system will boot into xwindows with DRI enabled. With out setting it to "PCI" then the screen locks as described above. I have not tried FC4 on this system yet.
*** Bug 152312 has been marked as a duplicate of this bug. ***
This is a mass-update to all currently open Fedora Core 3 kernel bugs. Fedora Core 3 support has transitioned to the Fedora Legacy project. Due to the limited resources of this project, typically only updates for new security issues are released. As this bug isn't security related, it has been migrated to a Fedora Core 4 bug. Please upgrade to this newer release, and test if this bug is still present there. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. Thank you.
This problem is still happening in FC4. I just installed FC4 on this laptop again and have found that DRI does not work in AGP or PCI mode. Current packages: 2.6.14-1.1656_FC4 and xorg 6.8.2-37.FC4.49.2 I have yet to try using a stock 2.6.15 kernel from kernel.org yet.
This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you.
Ok, the solution to this has been tracked down, please see this kernel bug report for the solutions. http://bugzilla.kernel.org/show_bug.cgi?id=4513 Quick summary: Narrowed down to a missing function in the efficeon-agp driver. Patch has been developed and tested succesfully. Glad to have it working again, and a big thanks to all that narrowed this down and fixed it! Look forward to seeing this patch in future kernels.
This bug does also exist in FC5.
Should be fixed in the latest errata for both FC4 & FC5.