Created attachment 23001 [details] Xorg log xorg-x11-drv-i810-2.5.0-4.fc10.i386 xorg-x11-server-Xorg-1.5.3-13.fc10.i386 libdrm-2.4.0-0.21.fc10.i386 mesa-libGL-7.2-0.15.fc10.i386 On startup X begins to takes 100% cpu and is unresponsive except that the X cursor moves with the mouse. [root@machias X11]# grep -E 'EE|WW' /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (EE) Unable to locate/open config file (II) Loading extension MIT-SCREEN-SAVER (WW) Falling back to old probe method for fbdev (EE) open /dev/fb0: No such file or directory (WW) Falling back to old probe method for vesa (WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB (WW) intel(0): Failed to allocate texture space. (WW) intel(0): Failed to allocate texture space. (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled (WW) intel(0): Existing errors found in hardware state. (EE) AIGLX error: drmMap of framebuffer failed (Invalid argument)(EE) AIGLX: reverting to software rendering This is with an empty xorg.conf. Same result with AccellMethod set to XAA. strace shows infinite loop: --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now [])
Also, previously used the i810 driver on this machine because it allowed the use of 1600x1200 resolution with this monitor: (II) I810(0): Attempting to use 75.00Hz refresh for mode "1600x1200" (85a) (--) I810(0): Virtual size is 1600x1200 (pitch 2048) (**) I810(0): *Built-in mode "1600x1200"
Better with: xorg-x11-drv-i810-2.6.0-5.fc11.i386 xorg-x11-server-Xorg-1.5.99.902-12.fc11.i386 libdrm-2.4.4-4.fc11.i386 mesa-libGL-7.3-2.fc11.i386 Only error/warning messages now are: (WW) Falling back to old probe method for vesa (WW) Falling back to old probe method for fbdev (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. Although I am seeing 5.6-5.9% CPU for the X server just sitting at the log it screen.
Created attachment 23031 [details] X strace This seems to be the loop X is in as shown by strace.
Hmm, no cpu usage after today's fedora rawhide updates and a reboot. As for the initial issue, would it be possible for whatever fixed that issue to get backported to the 2.5 branch for possible inclusion into Fedora 10?
Looks fixed. Close.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.