Intrepid: compiz fails on Intel McCreary [8086:2e02]

[Yingying Zhao]

Platform: McCreary (Eaglelake gfx & ICH10)
OS: Intrepid Alpha4 x86_64

When I tried to login X system when compiz is enabled, the screen is dead while the mouse can move.

[update]
Compiz has been blacklisted for this chip 8086:2e02, which resolves the booting issue, but leaves the question of why compiz is not working on this hardware.

[Yingying Zhao (yingying-zhao)]

Created an attachment (id=18609)
Xorg.0.log

HW: Eaglelake gfx & ICH10
OS: Intrepid Alpha4 x86_64 with kernel 2.6.27-rc5

When I tried to login X system, the screen hang up without any response. "Ctrl+Alt+Fx" doesn't work and networking(ssh) doesn't work neither.

If comment the "dri" section in Xorg.conf, X can boot well.

I'll attach the Xorg.0.log and Xorg.conf.
Please let me know what else I can do for this bug.

[Yingying Zhao (yingying-zhao)]

Created an attachment (id=18610)
Xorg.conf which comments out "Load dri"

[Gordon Jin (gordon-jin)]

Does this problem only happens on Eaglelake?

[Haihao-xiang (haihao-xiang)]

Obviously the driver you are using is improper.

See "(EE) AIGLX error: i965 exports no extensions (/usr/lib/dri/i965_dri.so: undefined symbol: __driDriverExtensions)" in your Xorg.0.log.

[Yingying Zhao (yingying-zhao)]

I made(In reply to comment #3)
> Obviously the driver you are using is improper.
I made a mistake. I just submitted the log files for system which we downgraded Mesa to 7.0 for bug analysis purpose.

I'll attach the log file for a fresh Intrepid Alpha4 w/ 2.6.27-rc3 kernel.

[Yingying Zhao (yingying-zhao)]

Created an attachment (id=18633)
Xorg.0.log for fresh Intrepid Alpha4 with upgraded 2.6.27-rc4 kernel

[Yingying Zhao (yingying-zhao)]

(In reply to comment #5)
> Created an attachment (id=18633) [details]
> Xorg.0.log for fresh Intrepid Alpha4 with upgraded 2.6.27-rc4 kernel

Sorry. It's 2.6.27-rc3 kernel.
#uname -a
Linux ubuntu-MC 2.6.27-1-generic #2 SMP Wed Aug 13 19:41:04 UTC 2008 i686 GNU/Linux

[Haihao-xiang (haihao-xiang)]

How do you start up X? Could you run X from a console by hand?

[Yingying Zhao (yingying-zhao)]

Created an attachment (id=18646)
default xorg.conf of Intrepid

Default xorg.conf of Intrepid. X always fails to boot in this configuration.

[Yingying Zhao (yingying-zhao)]

I tried the 2.6.27-rc3 kernel and this bug is still there.

[Yingying Zhao (yingying-zhao)]

X can start with dri disabled.

I added the following to the default xorg.conf and then I can boot into X:
Section "Module"
# Load "dri"
EndSection

[Yingying Zhao (yingying-zhao)]

I tried to boot into console mode, run "X" with different xorg.conf. I got same result: a gray screen. Mouse can move, but no gnome desktop. The different xorg.conf are:
- with default xorg.conf
- with defalt xorg.conf plus "Load dri" in "Module" section
- with defalt xorg.conf plus "Option AccelMethod EXA" and "Option DRI false" in "Device" section and "Load dri" in "Module" section
- with defalt xorg.conf plus "Option AccelMethod EXA" and "Option DRI true" in "Device" section and "Load dri" in "Module" section
- with defalt xorg.conf plus "Option AccelMethod EXA" and "Option DRI true" in "Device" section and "Load dri" in "Module" section

[Yingying Zhao (yingying-zhao)]

In console mode with Intrepid default xorg.conf, I just tried to start xterm and run glxgears and it can well display the gears.

The steps I used:
> xinit /usr/bin/xterm -> I get a xterm window
> glxinfo | grep rendering -> the output is:
Failed to initialize TTM buffer manager. Falling back to classic.
direct rendering: Yes
> glxgears -> gears display well.

[Haihao-xiang (haihao-xiang)]

So X can startup well and basically direct rendering works well too. The issue you encountered should be caused by a client program, not X itself.

[Yingying Zhao (yingying-zhao)]

Hi Haihao,
I just checked this issue with Intrepid Alpha5 release and glad to see this issue disappears:-)
Thanks for your help!

[Haihao-xiang (haihao-xiang)]

Marked as fixed according to comment #12

[Yingying Zhao (yingying-zhao)]

More detailed discussion about this bug is in freedesktop bugzilla http://bugs.freedesktop.org/show_bug.cgi?id=17384.
X can startup well and basically direct rendering works well. Some application of gnome may caused this problem.
I tested Intrepid Alpha 5 x86_64 and x86 releases. The result is gnome desktop can start with "none" Visual Effect, but always hang up with "normal" Visual Effect.

[Yingying Zhao (yingying-zhao)]

In the latest testing of Intrepid Alpha5 (kernel 2.6.27-rc5), I found that if we turn on the virtual effect of gnome, X will still hang up and only reboot can make system come back.

And another issue is after the gfx hangs up, e1000e cards will stop working. seems that a system crash writes some wrong data to EEPROM of LAN cards. A very similar discussion is also there in the e1000e mailling list which shows that after some gfx crash, his e1000e card also got corruption. http://<email address hidden>/msg00399.html
Now we can't say it's gfx crash that causes this e1000e issue, but the fix for gfx crash can help us for the e1000e issue.

Can you reopen this bug or do I create another bug?

[Haihao-xiang (haihao-xiang)]

Could you provide the PCI id of your machine?

[Bryce Harrington (bryce)]

Created an attachment (id=19156)
lspci output

I can reproduce the issue with similar hardware. lspci attached.

[Bryce Harrington (bryce)]

Yes, I can confirm the failure. It seems to be a recent regression - I had a functional compiz on this hardware as of a couple weeks ago (prior to the latest mesa and I think maybe prior to the .27 kernel).

[Yingying Zhao (yingying-zhao)]

Created an attachment (id=19177)
lspci output of my test machine

[Gordon Jin (gordon-jin)]

Yingying, as I understand, turning on virtual effect of gnome just means running compiz, right?
So I test compiz with mesa-7.2 + xf86-video-intel-2.5-branch + 2.6.27-rc6 on 2e02 (rev 03) (the same pci id as yours) and it works fine.
Can you try mesa-7.2 to see if this issue has gone?

[Haihao-xiang (haihao-xiang)]

I tested Intrepid with virtual effect enabled on 2e02 (rev 03), and it works fine for me.

[Yingying Zhao (yingying-zhao)]

(In reply to comment #19)
> I tested Intrepid with virtual effect enabled on 2e02 (rev 03), and it works
> fine for me.

I just want to make sure the "visual effect" is set to "normal" (it's "none" in default installation), right?
And after you login gnome desktop, can you run some application, like firefox.etc. Sometimes, gfx can't crash until we run some GUI applications.

[Haihao-xiang (haihao-xiang)]

(In reply to comment #20)
> (In reply to comment #19)
> > I tested Intrepid with virtual effect enabled on 2e02 (rev 03), and it works
> > fine for me.
> I just want to make sure the "visual effect" is set to "normal" (it's "none" in
> default installation), right?

normal or extra.

> And after you login gnome desktop, can you run some application, like
> firefox.etc. Sometimes, gfx can't crash until we run some GUI applications.
>
Normal operations such as open, maximize/minimize, drag a window all work fine.
If only a special application cause X hung up, I think you should open a new bug to track it (You said you failed to login into X in your bug description) and detail how to reproduce this issue.

[Yingying Zhao (yingying-zhao)]

> If only a special application cause X hung up, I think you should open a new
> bug to track it (You said you failed to login into X in your bug description)
> and detail how to reproduce this issue.

Before we upgraded mesa to 7.2 (in Intrepid Alpha6, the mesa is 7.1-RCx), X always hangs right after we input the username/password and login the system without running any applications.

Yesterday we upgraded mesa to 7.2 and tried these operations:
- First time, Run one application caused X hang, steps:
1. After default installation (compix is disable by default), login system and upgraded the mesa packages and then turn on "visual effect" to "normal" and then reboot system
2. After login system, there's no X crash. But when I run "Synaptic Package Manager", screen became black and we could only see the mouse moving.
3. Press "Ctrl+Alt+Fx" can't show any console, but we also tried to press "Ctrl+Alt+F2" and input "username", "password", "sudo reboot", "password"
4. After several minutes, system didn't perform "reboot", but shut down.

- Second time, we powered on the machine and system failed to boot.
After press the "power on" button, we can see the boot progress bar. But we didn't see the login window after the progress bar reached 100% as expected, instead, system shut down again.

- Third time, we powered on the machine and X hang right after I login the system.

The mesa-7.2 packages I updated for Intrepid Alpha6 are:
ii libgl1-mesa-dri 7.2-1ubuntu1 A free implementation of the OpenGL API -- D
ii libgl1-mesa-glx 7.2-1ubuntu1 A free implementation of the OpenGL API -- G
ii libglu1-mesa 7.2-1ubuntu1 The OpenGL utility library (GLU)
ii mesa-utils 7.2-1ubuntu1 Miscellaneous Mesa GL utilities

I don't think is caused by some specific application, we also meet this issue when we run firefox.

[Eric Anholt (eric-anholt)]

This needs to be retested against current drm-intel-next kernel and master xf86-video-intel.

[Michael Fu (michael-fu-intel)]

this one should be fixed now. please reopen if it doesn't. thanks.

[Bryce Harrington (bryce)]

I've tested compiz with jaunty on McCreary and it's working splendidly now. The compiz blacklist should be removed.

I did notice another issue that occurs when shutting down X, but will report that separately.

[Bryce Harrington (bryce)]

Fix uploaded and committed to bzr

[Michael Vogt (mvo)]

The compiz blacklist is removed now.

[Bryce Harrington (bryce)]

Thanks mvo, closing bug.

Feel free to reopen if there are still any problems.