Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Starting up X locks up my machine|
|Product:||[Fedora] Fedora||Reporter:||Lennart Poettering <lpoetter>|
|Component:||xorg-x11-drv-i810||Assignee:||Adam Jackson <ajax>|
|Status:||CLOSED DUPLICATE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||notting, peter.hutterer, tcallawa, xgl-maint|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-11-04 13:38:47 EST||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Lennart Poettering 2008-10-05 16:22:10 EDT
Created attachment 319501 [details] xorg.0.log When I start up X on my machine the machine locks up entirely. If this happens with gdm all you see is a gray frame where the login window should be and then things are frozen. The animated cursors before that is shown properly however. If you start X from the console by typing "X" it freezes right-away. This is "Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)". xorg-x11-drv-i810-2.4.2-9.fc10.i386
Comment 1 Bill Nottingham 2008-10-27 16:30:12 EDT
Any improvements with new rawhide kernel/intel 2.5.0 driver?
Comment 2 Lennart Poettering 2008-10-30 21:50:23 EDT
The problem is still unchanged even with current rawhide. But, I now get a differnt Xorg.0.log output. Will attach. It seems to suggest that this is not actually a problem of the intel driver, but of evdev instead. Also, the machine is not completely locked up. Logging in via ssh still works. When I switch to the "vesa" driver the problem goes away. I'll also attache my xorg.conf.
Comment 3 Lennart Poettering 2008-10-30 21:51:23 EDT
Created attachment 322011 [details] New xorg.0.log
Comment 5 Lennart Poettering 2008-10-30 21:54:29 EDT
/me wonders if that has anything to do with the "Video Bus" devices showing up as input devices in /proc/bus/input/devices. I'll attach a dump.
Comment 6 Lennart Poettering 2008-10-30 21:55:16 EDT
Created attachment 322013 [details] /proc/bus/input/devices
Comment 7 Bill Nottingham 2008-10-31 12:23:51 EDT
CC'ing evdev guru.
Comment 8 Peter Hutterer 2008-11-02 18:41:45 EST
nope, this isn't evdev. what happens is that the graphics driver hogs the server, so all input events that are processed during SIGIO are appended to the event queue but never removed. After a while, the EQ starts overflowing - causing all these warnings and the backtrace (for debugging). So these warnings mean that the evdev driver still works happily, but the graphics driver doesn't.