Bug 17384

Created attachment 18610 [details]
Xorg.conf which comments out "Load dri"

Does this problem only happens on Eaglelake?

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.

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.

Created attachment 18633 [details]
Xorg.0.log for fresh Intrepid Alpha4 with upgraded 2.6.27-rc4 kernel

(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

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

Created attachment 18646 [details]
default xorg.conf of Intrepid

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

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

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.

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.

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

Marked as fixed according to comment #12

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://www.mail-archive.com/e1000-devel@lists.sourceforge.net/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?

Could you provide the PCI id of your machine?

Created attachment 19156 [details]
lspci output

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

Created attachment 19177 [details]
lspci output of my test machine

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?

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

(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.

(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.

> 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.

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

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