Created attachment 22588 [details]
Xorg log from 1st run
Acer Aspire 3690
Celeron Yonah 1.6
Intel 945GM w/ integrated graphics
Source Mage GNU/Linux
Linux 2.6.29-rc3-git5 (also 2.6.29-rc3), only with enabled KMS
xorg-server 1.5.3 (also 220.127.116.112)
The first time I run Xorg, it works with following glitches:
1. Xorg sets screen to 1280x800 (native resolution of my LCD), but for some reason it changes LVDS mode to 1024x768, displaying only upper-left part of the desktop. Xrandr knows about this mismatch and it is possible to switch LVDS back to 1280x800. VT switching works in both modes and in 1280x800 it is much faster than it used to be, so I assume that KMS works fine.
2. 3D rendering performs very poorly. glxgears gives ~0.928 fps and prints this message:
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try adjusting the vblank_mode configuration parameter.
When I exit X and try to start it again, I get a black screen and an oops in dmesg.
Created attachment 22589 [details]
Xorg log from 2nd run
Created attachment 22590 [details]
dmesg after 2nd run
Created attachment 22591 [details]
Created attachment 22592 [details]
I can confirm this, with Linux kernel 2.6.29-rc4-git (HEAD is 4c098bcd55fad34dcf224bf8343db6a9ac58fc68).
I'm attaching my dmesg output with the Oops.
945GM (X60s Thinkpad) chipset
Created attachment 22757 [details]
this still happens with 2.6.29-rc5 and latest drm-fixes (commit:eaaffe54249d4444bb4de3631b9d968456bb0458)
I have the same issue on my acer extensa 5620 with an Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03).
Last kernel tried is 2.6.29-rc5 which im using right now, libdrm 2.4.4, mesa 7.3 and xorg server 1.5.3.
Just ask if you need more info.
Can you try again with -rc7 and 2D driver 2.6.3? We've fixed a ton of bugs between when this was reported and today. Also it looks like you're only getting DRI1 for some reason; we mainly test KMS with DRI2 so you should probably figure out why you're not getting that.
Doesn't happen for me with kernel 2.6.29-rc7, xf86-video-intel-2.6.3 and xorg-server 1.6.0, using KMS.
There are other problems (on which I couldn't gather data-points) but this exact bug seems to be solved.
Great, thanks for testing.
I've just checked it on my box. With rc7 and driver 1.6.3 the oops is gone.