With the current intel driver (xorg-x11-drv-i810-2.4.2-8.fc10.i386), Xorg seems to "hang" occasionally, until it gets input from the mouse or keyboard. Then it starts drawing again. Once the input stops the display draws for a bit, then hangs again.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 316762 [details] Xorg.0.log from stalled graphics system I'm seeing identical behavior. Clean rawhide install from this past weekend on an Acer Aspire One. No xorg.conf whatsoever, here's the resulting log.
Some further info: Intel 945GME integrated graphics in this case. BIOS lists 8MB allocated for graphics (can't be altered).
Booting with pci=nomsi seems to help here.
Created attachment 316770 [details] Xorg.0.log Xorg.0.log from a Dell Insprion 1420 with a "Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)" that exhibits this problem with the same driver as the OP. This system does not use an xorg.conf file. pci=nomsi helps somewhat, but the display still hangs for me.
please try -329 when it builds in koji.
Seems I was just lucky that one boot w/pci=nomsi, it doesn't seem to have made a difference on subsequent boots (nor did nohz=off). Trying 329 w/the updated intel irq handling patches momentarily... Okay, booted, and so far, looks like that did the trick. Noticeable improvement in graphics responsiveness across the board, and I have yet to encounter any stall-outs. Will keep an eye on it the next boot or three to be sure it isn't a fluke like nomsi. ;)
(In reply to comment #6) > please try -329 when it builds in koji. That one fixes the issue for me.
Will? Does -329 help for you?
This seems fixed with kernel -329.
I don't get this any more with 329 either.
329 is in the beta/rawhide, closing this bug.