[i965] X freezes starting on April 3rd

[Jithin Emmanuel]

[Problem]
Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 users started noticing X freeze after several hours of use, triggered by application usage especially noticeable with (but not unique to) compiz enabled.

[Impact]
The freeze bug affects a subset of i965 based systems, most particularly those using compiz. Exact numbers cannot be determined, but may be as high as 25-50% based on rough estimates.

The problem is severe: An unpredictable lockup of the system that requires a power cycle to recover from. For some users it comes on within minutes, while for others it comes after a few hours of use.

[How Addressed in Development Version]
For now, the patch being proposed for Jaunty has been uploaded to Karmic.

Longer term, we plan to move from EXA to UXA once the latter is stable enough. It has been found that while UXA exhibits other kinds of freezes, we've not yet been able to reproduce this particular freeze there.

[Patch for Jaunty]
A low-risk workaround that has proven effective at eliminating freezes, or at least greatly reducing their frequency, is to increase the Virtual framebuffer size. Some users do this locally as a matter of course to gain dual-head support, so this setting has received extremely widespread testing already.

The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it is not otherwise specified. Users can still override this with their own settings, larger or smaller, as desired.

A side effect of this patch is that it also mitigates bug 158415 to a degree, which will make projector usage somewhat easier for this hardware because it will enable X to recognize higher resolutions available from the external monitor than were available on initial boot.

[Test Case]
The best method found to reproduce the bug is:
  a. Enable compiz
  b. Set your desktop to a 6x1 workspace layout
  c. Run http://launchpadlibrarian.net/25683477/repro.sh
  d. System will freeze anywhere from 1-20 min typically
  e. Power-button shutdown is required to reset the system

[Regression Potential]
In general, Virtual has been widely and extensively tested, so we do not expect this patch to trigger regressions.

The patch is coded to only take effect on i965 systems, so the scope of any regression that might conceivably be triggered will be limited to just that hardware.

[Suspects]
Omitting obviously trivial, unrelated changes, here are what changed in several suspect packages in the timeframe in question:

* intel driver:
  4/01: 118_drop_legacy3d.patch: Removed Legacy3D
  4/03: 114_fix_xv_with_non_gem.patch: Dropped since it caused regression
  4/06: 119_drm_bo_unreference_needs_null.patch: Fixes various nullptr derefs
  4/08: 120_fix_vt_switch.patch: Fix nullptr deref in video playback

* xserver:
  4/08: 177_animated_cursor_change_master.patch: fixes animated cursors
  4/06: 174_set_bg_pixmap_of_cow_to_none.patch: Sets bg pixmap of
         composite overlay window to None
  3/30: 172_cwgetbackingpicture_nullptr_check.patch: fix race condition
         when minimzing/maximizing firefox with flash video playing.

* mesa:
  4/03: 7.4 released
    * Added MESA_GLX_FORCE_DIRECT env var for Xlib/software driver
    * GLSL version 1.20 is returnd by the GL_SHADING_LANGUAGE_VERSION query
    * glGetActiveUniform() returned wrong size for some array types
    * Fixed some error checking in glUniform()
    * Fixed a potential glTexImage('proxy target') segfault
    * Fixed bad reference counting for 1D/2D texture arrays
    * Fixed VBO + glPush/PopClientAttrib() bug #19835
   * Assorted i965 driver bug fixes
    * Fixed a Windows compilation failure in s_triangle.c
    * Fixed a GLSL array indexing bug
    * Fixes for building on Haiku

* linux:
  4/04: 2.6.28-11.41: Revert MCHBAR patch
  4/02: 2.6.28-11.40: Add MCHBAR patch

* libdrm:
  4/04: 02_libdrm_nouveau_update.patch: Only affects nouveau code
  3/29: libdrm-nouveau1.symbols: Probably innocuous

[Workarounds]
Various people have found one or more of the following have helped to reduce the frequency or eliminate the freezes:

  * Turn off compiz
  * AccelMethod UXA
  * Set NoAccel true
  * Set Virtual to something high
  * MigrationHeuristic greedy
  * Revert to 2.4 -intel driver

[Current Theory]
A 3D memory buffer accumulates data until something gets in there incorrectly and leads to a freeze. This can happen either slowly over a long period of light use, or fairly soon if using the system heavily. It is not simply a matter of filling the memory up, so the trigger often seems to be random, but usually follows some sort of graphics transition (such as the 3D effect from alt-tab, or closing a firefox window).

It is fairly certain that there are multiple freeze bugs present in X.org with the -intel driver. This causes significant confusion when people having different bugs think they might have the same one, and find the symptoms and workarounds don't match. It is also suspected that the same root bug may have multiple different ways of triggering it.

Increasing the Virtual settings seems to either eliminate or greatly reduce the frequency of these freezes. Presumably this allocates larger memory buffers so the chances of something hitting a wrong thing are greatly lessened. However, none of this is well understood.

[Original Report]
I am using kubuntu jaunty beta. My system is freezing randomly. I have the latest updates.
After freezing the mouse pointer still works. And sometimes the power off button works. On powering off , when the stage for kubuntu logo comes its showing a distorted image.

This happens with or without desktop effects. These freezes are very randomly, but mostly when I run some new applications.
I am using intel graphics.

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c)
     Subsystem: Hewlett-Packard Company Device [103c:30be]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
     Subsystem: Hewlett-Packard Company Device [103c:30be]

[Jithin Emmanuel (jithin1987)]

Sorry the first attachment is lscpci , typo

[Bryce Harrington (bryce)]

What you have described is a generic freeze. It could be caused by any number of things, and you need to take some additional steps to provide a complete report. "randomly" is not specific enough to be able to analyze the problem.

When did you upgrade to Jaunty? When did you first notice the freezes occurring?

How frequently do the freezes occur? How many per day would you say you experience?

List the applications you typically have open at the time of the freeze.

Describe example activities you were performing for a few of the recent freezes. You mentioned it occurs when you run new applications, which applications were these? In what way were they "new"?

For more tips on troubleshooting freeze bugs, please refer to these links:

  https://wiki.ubuntu.com/X/Troubleshooting/Freeze
  https://wiki.ubuntu.com/X/Bugs/IntelDriver

[Jithin Emmanuel (jithin1987)]

I did not have the freezes on jaunty alpha6. I remember it started occurring on last friday april 3rd . I am sure because it was that day kde 4.2.2 updates hit the jaunty repos. Prior to that date, when I was using kde 4.2.1 I didn't have any freezes.
The application I have running are firefox, kmail , kopete, eclipse, konsole.

Some times freeze occurs after I start kmail , but not always. Mostly when freezing I will be using konsole or kmail or firefox.
New in the sense after I start some new applications. Though I never noticed this occurring on idle state. Some times freeze occurs after login, but only after applications start and I get desktop.

[Jithin Emmanuel (jithin1987)]

And I am using a laptop hp compaq 6910p

[Matthew Woerly (nattgew)]

I'm having random freezes too, with Gnome and Compiz. They seemed to just start recently, maybe around April 3rd like you said.
I thought it was related to Gnome-Do at first, because it always froze when trying to bring up Gnome-Do. I removed that and still had the problem. So then I thought it was the UXA acceleration, but I changed back to EXA and still had it freeze. Now the freezes seem random, I'll see if I can find some kind of trend in when they occur.

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

[Bryce Harrington (bryce)]

On Sat, Apr 11, 2009 at 08:44:00AM -0000, Jithin Emmanuel wrote:
> I did not have the freezes on jaunty alpha6. I remember it started occurring on last friday april 3rd . I am sure because it was that day kde 4.2.2 updates hit the jaunty repos. Prior to that date, when I was using kde 4.2.1 I didn't have any freezes.
> The application I have running are firefox, kmail , kopete, eclipse, konsole.
>
> Some times freeze occurs after I start kmail , but not always. Mostly when freezing I will be using konsole or kmail or firefox.
> New in the sense after I start some new applications. Though I never noticed this occurring on idle state. Some times freeze occurs after login, but only after applications start and I get desktop.
>

Thanks for narrowing it to date 4/3, that's probably a very good clue.
Please attach your /var/log/dpkg.log so I can see what versions of
things you had installed that date.

Bryce

[Andres Mujica (andres.mujica)]

in fact i was about to point as probably guilty the xorg updates for that day. In fact i remember i've updated late at night and the other day i had about 5 freezes during the day.

However i didn't see anything deeply related with a freeze in the changelog.

I'm waiting for another freeze, so i can downgrade to a previous version and check again.

the thing is that this bug is hard to reproduce...

[Andres Mujica (andres.mujica)]

Would it be possible to the affected users to downgrade the mesa packages to version 7.3?

libglu1-mesa_7.3-1ubuntu4_i386.deb
libgl1-mesa-dri_7.3-1ubuntu4_i386.deb
libgl1-mesa-glx_7.3-1ubuntu4_i386.deb
mesa-utils_7.3-1ubuntu4_i386.deb

these ones are probably at /var/cache/apt/archives on your machines, if not go to packages.ubuntu.com and download those versions.

Thanks

[Bryce Harrington (bryce)]

2009-04-03 23:32:25 upgrade libgl1-mesa-dri 7.3-1ubuntu4 7.4-0ubuntu1
2009-04-03 23:32:25 status half-configured libgl1-mesa-dri 7.3-1ubuntu4
2009-04-03 23:32:25 status unpacked libgl1-mesa-dri 7.3-1ubuntu4
2009-04-03 23:32:25 status half-installed libgl1-mesa-dri 7.3-1ubuntu4
2009-04-03 23:32:26 status half-installed libgl1-mesa-dri 7.3-1ubuntu4
2009-04-03 23:32:27 status unpacked libgl1-mesa-dri 7.4-0ubuntu1
2009-04-03 23:32:27 status unpacked libgl1-mesa-dri 7.4-0ubuntu1
2009-04-03 23:32:27 upgrade libgl1-mesa-glx 7.3-1ubuntu4 7.4-0ubuntu1
2009-04-03 23:32:27 status half-configured libgl1-mesa-glx 7.3-1ubuntu4
2009-04-03 23:32:27 status unpacked libgl1-mesa-glx 7.3-1ubuntu4
2009-04-03 23:32:27 status half-installed libgl1-mesa-glx 7.3-1ubuntu4
2009-04-03 23:32:27 status half-installed libgl1-mesa-glx 7.3-1ubuntu4
2009-04-03 23:32:27 status unpacked libgl1-mesa-glx 7.4-0ubuntu1
2009-04-03 23:32:27 status unpacked libgl1-mesa-glx 7.4-0ubuntu1

Bingo.

On my i965 system, after reproducing the freezes yesterday, I downgraded to mesa 7.3 (and nothing else), left it running overnight, and have seen no freezes since.

To confirm, please downgrade these packages; you may still have them in your /var/cache/apt/archives/, else you can get them off packages.ubuntu.com.

If my theory is correct, you'll have no further freezes after installing these packages.

[Andres Mujica (andres.mujica)]

For those without the packages at /var/cache/apt/archives

https://edge.launchpad.net/ubuntu/jaunty/i386/mesa-utils/7.3-1ubuntu4
https://edge.launchpad.net/ubuntu/jaunty/i386/libgl1-mesa-dri/7.3-1ubuntu4
https://edge.launchpad.net/ubuntu/jaunty/i386/libgl1-mesa-glx/7.3-1ubuntu4
https://edge.launchpad.net/ubuntu/jaunty/i386/libglu1-mesa/7.3-1ubuntu4

download, install with sudo dpkg -i filename and restart your session. Don't apply new updates until it's confirmed or discard that the problem is with mesa.

thanks

[Andres Mujica (andres.mujica)]

i've downgraded, waiting for the freeze to happen (about 24 hours ago i had 2 freezes, just a few hours i had another one, so at least tomorrow night will report back)

however check this comment

https://bugs.edge.launchpad.net/ubuntu/+bug/358033/comments/15

unless is not related... :(

[wirechief (wirechief)]

I need the packages listed by Andres Mujica however i need the amd64 versions, can they be gotten ? I tried to find
them at the link listed without success.

[wirechief (wirechief)]

I hope that those who find they need to reboot because of the freeze have at least tried RSEIUB , if used correctly
it can prevent filesystem damage here is a link to how its used.. http://techpatterns.com/forums/about911.html
I have noticed that `intel_reg_dumper`, which is available as part of the xserver-xorg-video-intel-dbg package
reveals the register that is being changed when the freeze occurs, running it before and after the crash and using
sudo intel_reg_dumper > reg_good.txt before the crash and sudo intel_reg_dumper > reg_bad.txt after the crash
from a ssh session to the sick machine and then doing sudo diff reg_good.txt reg_reg_bad.txt will show the register
that is changing .
 diff reg_good.txt reg_bad.txt
140c140
< (II): MI_MODE: 0x00000200
---
> (II): MI_MODE: 0x00000000
and then
wirechief@wirechief-laptop:~$ cat reg_bad.txt |grep MI_MODE
(II): MI_MODE: 0x00000000
wirechief@wirechief-laptop:~$ cat reg_good.txt |grep MI_MODE
(II): MI_MODE: 0x00000200
I am reading in other bug reports this is the common indication that the freeze issue has occurred.

[Andres Mujica (andres.mujica)]

change i386 for amd64 in the path.

[wirechief (wirechief)]

Sun Apr 12 12:28pm
my mesa downgraded .
sudo dpkg -l |grep mesa
ii libgl1-mesa-dri 7.3-1ubuntu4 A free implementation of the OpenGL API -- D
ii libgl1-mesa-glx 7.3-1ubuntu4 A free implementation of the OpenGL API -- G
ii libglu1-mesa 7.3-1ubuntu4 The OpenGL utility library (GLU)
ii mesa-utils 7.3-1ubuntu4 Miscellaneous Mesa GL utilities

I will have to research how to put these on hold so they are not updated on my next du
i got this when i tried.
sudo echo mesa-utils hold |dpkg --set-selections
dpkg: operation requires read/write access to dpkg status area

[Andres Mujica (andres.mujica)]

wirechief you've missed a sudo before dpkg

[crashsystems (crashsystems)]

As Bryce Harrington suggested, I downgraded my mesa packages to the previous version. I did this almost 24 hours ago, and 15 minutes ago I had another freeze. So I think ether the bug was introduced in an earlier version, or is in another package entirely.

[Steve Langasek (vorlon)]

crashsystems,

to confirm: you restarted X after downgrading the mesa packages?

[crashsystems (crashsystems)]

Yes, X was restarted. Since I took my laptop several places, it got rebooted
several times.

[VangelistX (vangelistx)]

Maybe newly released Mesa 7.5 will solve the problem?

http://www.phoronix.com/scan.php?page=news_item&px=NzE4OQ

What about including Mesa 7.5 in Jaunty?

[Jithin Emmanuel (jithin1987)]

After I downgraded to mesa 7.3 I am not facing any freezes so far. But the thing is, I am on vacation and is not under thesame conditions I got the bug, ie I am not using my laptop frequently and nor running applications I used to run and I am not using wifi. Anyway I will report back if I notice any freezes, I have been using with out any dektop effects, now I will enable them and use.

[Jithin Emmanuel (jithin1987)]

OK. I got my freeze after I enabled desktop effects with mesa 7.3. It seems like I asked for it the moment I switched desktop effects ON in my kubuntu. :( So mesa 7.3 is not the solution it seems.

[Julian Edwards (julian-edwards)]

It's definitely related to desktop effects, I am totally lockup-free without them, but will reliably freeze the instant I turn them on (alt-shift-f12).

However, I am also plagued by bug 342923 which makes performance pretty awful and with screen corruption. I wonder if these two bugs are related somehow.

I was running KDE4.2 from the PPA packages on intrepid before jaunty, and there were no problems at all. The intel Xorg driver has my finger pointing at it.

[Jithin Emmanuel (jithin1987)]

Same story here. I wish I was using intrepid with kde from PPA.

[wirechief (wirechief)]

Yes i have rebooted a number of times now and a no lockup as of yet.
I made a seperate bug on the pinning.. 359392

On Sun, Apr 12, 2009 at 9:55 PM, Andres Mujica
<email address hidden> wrote:
> wirechief you've missed a sudo before dpkg
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[wirechief (wirechief)]

I am not using Desktop effects. I disabled compiz. perhaps after
another 24hr i will give
them a try although for me I wasn't using them unless they are enabled
by default.
I did notice a drop in my screen performance but not significantly.

On Mon, Apr 13, 2009 at 8:35 AM, Jithin Emmanuel <email address hidden> wrote:
> Same story here. I wish I was using intrepid with kde from PPA.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Fernando Miguel (fernandomiguel)]

Is bug 359231 related to this bug, even if I have a different GPU (nvidia in my case)?

https://bugs.launchpad.net/bugs/359231

[Julian Edwards (julian-edwards)]

It's worth mentioning that I made the change mentioned in bug 342923:

        Option "AccelMethod" "EXA"
        Option "MigrationHeuristic" "greedy"

And I no longer get any freezes, even with effects turned on, and the desktop is a lot quicker now.

(I have a GMA965)

[Matt Zimmerman (mdz)]

Bug 358574 may be a duplicate of this one, please evaluate.

[Jithin Emmanuel (jithin1987)]

Today I am back to work and the moment I started my laptop in my office. I had 2 freezes in a row on login and after that it went away, one with desktop effects and one with out desktop effects. I guess mesa 7.3 has nothing to do with the freezes. Shall I updates back to mesa 7.4

The 3rd time before I logged in I ssh'ed to my box and has Xorg.0.log tail'ed

[Jithin Emmanuel (jithin1987)]

Ok It froze again gor the 3rd time but this time it closed the ssh connection I had and I was not able to connect again until I restarted.

Can any one confirm on
        Option "AccelMethod" "EXA"
        Option "MigrationHeuristic" "greedy"
change?

[Christophe Olinger (olingerc)]

Hey guys,

Just wanted to say that I'm experiencing the same problem on my hp2510p tablet PC which also got an intel graphics card. Am using kubuntu jaunty fully updated with kde 4.2.2 and the freezes started around the date mentioned here although I can't remember the exact date. The only applications I had freezes in were dolphin and firefox but those are the only ones I used. Desktop effects are enabled. I'll be on holiday for some days now so I can unfortunately not participate :-(

Good luck guys.

[Alex57185 (alexandre-demasi)]

I had the same problem on my Dell XPS M1330 with the intel cart. I updated this packages :

ibglu1-mesa
libgl1-mesa
libgl1-mesa-glx
mesa-utils

I use the debian packages in Sid (version 7.4-2 ) , and I updated the intel driver in the Sid repository.

I don't have any freeze after that (and I use the Desktop effect)

[Zack Evans (zevans23)]

@Jithin Emmanuel: I have multiple freeze bugs I think, including the one that appeared after the update to kernel 11.41. I have other freeze bugs that go back some time and therefore aren't related to recent updates.

Anyway - I can confirm that
        Option "AccelMethod" "EXA"
        Option "MigrationHeuristic" "greedy"
is rock-stable for me, so I'm now running that in day and experimenting with tracking my bugs down in the evening.

Note that my lockups are not specific to UXA, and happen with EXA if I omit the MigrationHeuristic option.

Mobile 945GME Express.

[Jithin Emmanuel (jithin1987)]

I upgraded back to mesa 7.4 and also added
        Option "AccelMethod" "EXA"
        Option "MigrationHeuristic" "greedy"
So far I am not having any freezes, but now my opera has a blank icon in system tray. Which will be taken over by the icon in its left if some new system tray icon is going to come on its right.
Have you faced this problem Zack Evans.

[Jithin Emmanuel (jithin1987)]

On more diggint it seems that
        Optio.n "AccelMethod" "EXA"
        Option "MigrationHeuristic" "greedy"
affects system tray icon on non kde applications in kubuntu. Do not know how its affects gnomes system tray.
Can any one using this option on a gnome desktop comment on this?

[Julian Edwards (julian-edwards)]

On Wednesday 15 April 2009 10:05:42 Jithin Emmanuel wrote:
> I upgraded back to mesa 7.4 and also added
> Option "AccelMethod" "EXA"
> Option "MigrationHeuristic" "greedy"
> So far I am not having any freezes, but now my opera has a blank icon in
> system tray. Which will be taken over by the icon in its left if some new
> system tray icon is going to come on its right. Have you faced this problem
> Zack Evans.

I get the same issue but with Konversation.

[Jithin Emmanuel (jithin1987)]

Konversarion is a kde 3 application . May be that's why Julian is having the issue.
Though it seems that
Option "AccelMethod" "EXA"
Option "MigrationHeuristic" "greedy" seems to fix the freeze issue, it brings its own trouble. CAN any one please tell what
Option "MigrationHeuristic" "greedy" does ?

[Zack Evans (zevans23)]

My system tray is OK, although most things I have in there are KDE4. Skype seems OK though and that's obviously not part of KDE4 build!

Do you have the same corruption as in https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/298475

Either way that's a new bug to do with "MigrationHeuristic" "greedy" causing corruption, so either find a similar bug or post a new one specific to the corruption problem - this bug is about freezes (I probably shouldn't have replied, because I am on 945 not 965 :-) )

[Laurent Claessens (moky-math)]

I'm also impacted by freezes since (more or less) the same datum.
My hardware is :
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

By the way, the workaround proposed here (for other reasons) seems to fix the situation about freezes on my computer :
https://wiki.ubuntu.com/ReinhardTartler/X/RevertingIntelDriverTo2.4

That is reverting the driver to the version in Intrepid.

I let you know if I experience new freezes although using the old driver.

[Bryce Harrington (bryce)]

Update from some of my testing and research...

Since downgrading mesa to 7.3, I had 2 freezes over a period of about 5 days or so. I then went back to 7.4 and in the space of 12 hours had 3 freezes.

It makes me wonder if there are two freeze issues - one low frequency one in 7.3, and a higher frequency one in 7.4. Certainly there were already a number of reports of freezes prior to 4/3, just that we had a spurt of i965-specific ones after 4/3.

[Bryce Harrington (bryce)]

For register dumps on this bug, MI_MODE 0x00000200 just means "Looks like the GPU is frozen", which we already know. :-)

However, if you get anything *different*, that could be evidence you may have an unrelated freeze.

[Bryce Harrington (bryce)]

"What about including Mesa 7.5 in Jaunty?"

No, it is way too late into release freeze to pull in new versions. Also, odd numbered mesa's are unstable versions, and the reason we wanted to be on 7.4 in the first place is so Jaunty would have a "stable release" version of mesa.

However, cherrypicking well-tested fixes from mesa 7.5 is certainly in the cards, if they can be shown to solve key issues in jaunty. If you find such a situation, open a new bug, link the patch, and state the case for inclusion in jaunty, and we can take a look.

[Bryce Harrington (bryce)]

The working theory we have at the moment is that this bug is being caused by the patch 103_bump_965_texture_limit.diff. This patch increases the texture size for i965 cards. This patch was proposed for mesa 7.4 but declined with the following comment:

"Each time we bump up the max texture size it means we also increase the max drawing surface size (render to texture and all that). One consequence of this is the fixed point arithmetic in the swrast triangle code may start failing. There's comments in the code about it. It also means various internal buffers will double in size.

It's not a huge deal, but some testing needs to be done. I really need to write a glean test that exercises max-sized textures/FBOs..."

Based on upstream's review that this could cause instabilities, I consider it our leading suspect at this time.

I've prepared a PPA with this change reverted. I've installed it and been running it on my test box without problems for a couple hours. Can others please give this a try and see if it helps?

https://edge.launchpad.net/~bryceharrington/+archive/purple

[Jithin Emmanuel (jithin1987)]

I heared in some comments that after X freeze system is still ssh'able . But what I experienced is that my ssh connection was closed and I was no longer able to access host till I rebooted. Although sysreq keys combinations RSEIUB worked.
I was using
Option "AccelMethod" "EXA"
Option "MigrationHeuristic" "greedy"
Now I am going to remove it and try Byrce's repository ( though I am not facing any freezes with this options it brings some graphical corruption)

[wirechief (wirechief)]

I am planning on giving this a try myself, although i have to admit to
being a complete novice on compiling
source files (but this is a good reason to learn) I have to wait until
my free download time, because of FAP
constraints. I havent tried the EXA or greedy option in my Xorg,
perhaps i should leave that alone until after
i get through these patches being tested.

On Wed, Apr 15, 2009 at 8:33 PM, Jithin Emmanuel <email address hidden> wrote:
> I heared in some comments that after X freeze system is still ssh'able . But what I experienced is that my ssh connection was closed and I was no longer able to access host till I rebooted. Although sysreq keys combinations RSEIUB worked.
> I was using
> Option "AccelMethod" "EXA"
> Option "MigrationHeuristic" "greedy"
> Now I am going to remove it and try Byrce's repository ( though I am not facing any freezes with this options it brings some graphical corruption)
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Bryce Harrington (bryce)]

On Thu, Apr 16, 2009 at 12:33:47AM -0000, Jithin Emmanuel wrote:
> I heared in some comments that after X freeze system is still ssh'able . But what I experienced is that my ssh connection was closed and I was no longer able to access host till I rebooted. Although sysreq keys combinations RSEIUB worked.

If you can't ssh or ping the system, that suggests a kernel freeze
rather than X.

However, if your system uses wireless, if your wireless is managed in
your user session, then if X freezes it is possible for the network to
go down. In such cases, plug in an ethernet cable and ssh through that.

Bryce

[Jithin Emmanuel (jithin1987)]

@Bryce Yes. I was using wireless next time if that happens I will try Ethernet connection. ( Hoping that there will not be a next time as I am using mesa packages from your PPA)

[Jithin Emmanuel (jithin1987)]

@Bryce. I had my first freeze using your PPA packages. It worked for a long time until I stared amarok and it froze during playback, though sound continued to come.

[Jithin Emmanuel (jithin1987)]

Its started freezing here and there. Now I am sticking with the xorg.conf options
Option "AccelMethod" "EXA"
Option "MigrationHeuristic" "greedy" even though its causing display corruptions around certain windows and system tray. Atleast it works.

[wirechief (wirechief)]

I have just installed the packages...will continue to monitor...

On Thu, Apr 16, 2009 at 12:10 AM, Jithin Emmanuel <email address hidden> wrote:
> @Bryce. I had my first freeze using your PPA packages. It worked for a
> long time until I stared amarok and it froze during playback, though
> sound continued to come.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Bryce Harrington (bryce)]

Yeah I have found I'm still getting frequent freezes with these
packages, after 30-60 min of use and always when doing alt+tab.
Seems to not make a difference whether greedy is enabled or not.

[Jithin Emmanuel (jithin1987)]

@Bryce. I am now using with Option "MigrationHeuristic" "greedy" and your mesa packages. So far there is nor freezes. I am planning to give UXA a try.

[Soeren Sonnenburg (bugreports-nn7)]

On Thu, 2009-04-16 at 09:30 +0000, Bryce Harrington wrote:
> Yeah I have found I'm still getting frequent freezes with these
> packages, after 30-60 min of use and always when doing alt+tab.
> Seems to not make a difference whether greedy is enabled or not.

Indeed, same here (on debian since about 1-2 days). Greedy does not
help, same freezes. It did not help to upgrade to the intel packages
from experimental either. Could it be related to general changes in
Xorg, like the hal stuff - e.g. would disabling it via
Option "AutoAddDevices" "off" make a difference?

So does anyone see this on non-intel?

Soeren

[Jithin Emmanuel (jithin1987)]

What do you guys mean by greedy? I thought it is Option "MigrationHeuristic" "greedy" . And I am using with that option with no freezes.

[wirechief (wirechief)]

I just added the following to my xorg.conf
Section "Device"
 Identifier "Onboard Intel Video"
  Option "EXAOptimizeMigration" "true"
 #Option "AccelMethod" "exa"
 #Option "MigrationHeuristic" "greedy"
 Option "monitor-VGA" "ExternalVGA"
 Option "monitor-LVDS" "OnboardLVDS"
 #Option "AccelMethod" "uxa"
EndSection
I think this enables EXA and I will try the greedy in a little while,
will see how this works.

On Thu, Apr 16, 2009 at 5:57 AM, Jithin Emmanuel <email address hidden> wrote:
> What do you guys mean by greedy? I thought it is Option
> "MigrationHeuristic" "greedy" . And I am using with that option with no
> freezes.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[fedsotto (fedsotto)]

Hi all,

I have been using the experimental fix for about two hours (I have an
intel) and I just faced the first freeze. I was writting an email in
thunderbird, in my case, it was totally unrelated with alt+tab.

Federico

Soeren Sonnenburg wrote:
> On Thu, 2009-04-16 at 09:30 +0000, Bryce Harrington wrote:
>
>> Yeah I have found I'm still getting frequent freezes with these
>> packages, after 30-60 min of use and always when doing alt+tab.
>> Seems to not make a difference whether greedy is enabled or not.
>>
>
> Indeed, same here (on debian since about 1-2 days). Greedy does not
> help, same freezes. It did not help to upgrade to the intel packages
> from experimental either. Could it be related to general changes in
> Xorg, like the hal stuff - e.g. would disabling it via
> Option "AutoAddDevices" "off" make a difference?
>
> So does anyone see this on non-intel?
>
> Soeren
>
>

[Jithin Emmanuel (jithin1987)]

@wirechief. Were you using uxa? Did you have freezes with it?

 I just enabled UXA and so far I have no freezes on my i965 graphics and performance seems to be a bit faster before UXA for sure.

[Soeren Sonnenburg (bugreports-nn7)]

On Thu, 2009-04-16 at 09:57 +0000, Jithin Emmanuel wrote:
> What do you guys mean by greedy? I thought it is Option
> "MigrationHeuristic" "greedy" . And I am using with that option with no
> freezes.

I meant that too. I just recognized that as I am using kms xorg refuses
to switch to using EXA, so 'greedy' was definitely not turned on.

[wirechief (wirechief)]

@Jithin Emmanuel, i was not using uxa. at the present time i have the Option "EXAOptimizeMigration" "true"
along with these, provided by Bryce, additionally i reinstalled compiz this am and so far everything is working
fine, I have tried using alt tab and no freeze's noted, I have tried Amarok and have a error message with it
but that is a seperate issue and not related to freezes.

dpkg -l |grep mesa
rc libgl1-mesa-glx 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- G
ii libgl1-mesa-swx11 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- r
ii libgl1-mesa-swx11-dbg 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- d
ii libgl1-mesa-swx11-dev 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- d
hi libglu1-mesa 7.4-0ubuntu2~bug359392~1 The OpenGL utility library (GLU)
ii libglu1-mesa-dev 7.4-0ubuntu2~bug359392~1 The OpenGL utility library -- development fi
ii libosmesa6 7.4-0ubuntu2~bug359392~1 Mesa Off-screen rendering extension
ii libosmesa6-dev 7.4-0ubuntu2~bug359392~1 Mesa Off-screen rendering extension -- devel
ii mesa-common-dev 7.4-0ubuntu2~bug359392~1 Developer documentation for Mesa
ii mesa-utils 7.4-0ubuntu2~bug359392~1 Miscellaneous Mesa GL utilities

[Jithin Emmanuel (jithin1987)]

I have been using UXA last day. and with that I am having no freezes. Also there was an update on mesa packages from repository and I applied it.
Does this mean switching to UXA is the solution to freezes?
But it has its own problem with switch user and some minor issues with hibernation ( though works). I have opened a separate bug for that.

[Martin Pitt (pitti)]

Should get fixed in an SRU.

[Jithin Emmanuel (jithin1987)]

What is an SRU? Does that means it won't be fixed when jaunty releases. Won't that create some badmouth?

[wirechief (wirechief)]

I have not had a freeze however i am noticing the "(EE)" error
cat /var/log/Xorg.0.log |grep "(EE)"
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) AIGLX error: dlopen of /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
(EE) AIGLX: reverting to software rendering
(EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
(EE) GLX: could not load software renderer

Is this a concern ? did i miss doing a patch from Bryce's PPA ?
I had Option "AccelMethod" "exa"
 Option "monitor-VGA" "ExternalVGA"
 Option "monitor-LVDS" "OnboardLVDS"
however # them and still have the same error, but again no freezes...

[Zack Evans (zevans23)]

usr/lib/dri/i965_dri.so is provided by the package libgl1-mesa-dri.

So indeed these errors suggest you are now missing that package, or you have a permissions problem with it, so I agree you have some installation problem with Bryce's package.

Meanwhile this means your system is not even trying to use DRI, so clearly you aren't going to trigger any bugs. :-) But I also imagine this means you've had a slowdown?

[Timo Jyrinki (timo-jyrinki)]

Dropping 103_bump_965_texture_limit.diff has kept mine and tjaalton's i965 machines from crashing for multiple days now. Before dropping it, I simply couldn't enable compiz.

I would suggest to drop 103 anyway as it looks like it already helps many i965 users, even if it would not be everyone.

[Timo Jyrinki (timo-jyrinki)]

Just an idea: dropping the patch helps only amd64 i965 users?

[wirechief (wirechief)]

Well thats where this gets very confusing to me.
with this check. sudo dpkg -l |grep libgl1-mesa-dri
iU libgl1-mesa-dri 7.4-0ubuntu2~bug359392~1
but i don't know what the iU stands for ;)
I don't seem to have a slowdown but i think that is relative if i dont
know what
fast is. ;)

On Fri, Apr 17, 2009 at 10:49 AM, Zack Evans <email address hidden> wrote:
> usr/lib/dri/i965_dri.so is provided by the package libgl1-mesa-dri.
>
> So indeed these errors suggest you are now missing that package, or you
> have a permissions problem with it, so I agree you have some
> installation problem with Bryce's package.
>
> Meanwhile this means your system is not even trying to use DRI, so
> clearly you aren't going to trigger any bugs. :-) But I also imagine
> this means you've had a slowdown?
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Matt Zimmerman (mdz)]

On Fri, Apr 17, 2009 at 03:41:03PM -0000, wirechief wrote:
> Well thats where this gets very confusing to me.
> with this check. sudo dpkg -l |grep libgl1-mesa-dri
> iU libgl1-mesa-dri 7.4-0ubuntu2~bug359392~1
> but i don't know what the iU stands for ;)
> I don't seem to have a slowdown but i think that is relative if i dont
> know what
> fast is. ;)

U stands for Unpacked, i.e. the package is not properly installed. Run
"sudo apt-get -f install"

--
 - mdz

[Soeren Sonnenburg (bugreports-nn7)]

On Fri, 2009-04-17 at 14:49 +0000, Timo Jyrinki wrote:
> Dropping 103_bump_965_texture_limit.diff has kept mine and tjaalton's
> i965 machines from crashing for multiple days now. Before dropping it, I
> simply couldn't enable compiz.
>
> I would suggest to drop 103 anyway as it looks like it already helps
> many i965 users, even if it would not be everyone.

Well I am seeing this very same bug in debian too. Debian got mesa 7.4
recently but only includes these patches

02_use-ieee-fp-on-s390-and-m68k.patch
03_optional-progs-and-install.patch
04_osmesa_version.diff.

I've tried various things to nail down the problem.

a) disable compiz / run metacity instead
b) disable aiglx/compositing
c) revert to a known to work self compiled xserver-xorg-video-intel
version 2.6.3

Nothing helped.

I wonder how if the bug is really in mesa and not some other part of
xorg / libdrm ...

[Ronald McCollam (fader)]

Attached is a script that will switch desktops, sleep for a couple of seconds, switch desktops, sleep... etc. forever. (A quick ugly hack of Shang-Feng Yang's script here: http://sfyang-en.blogspot.com/2008/02/rotate-cube-in-compiz-with-wmctrl.html)

You will need wmctrl installed for this to work (sudo apt-get install wmctrl).

This may be useful in attempting to reproduce this bug.

[wirechief (wirechief)]

Well I got myself wrapped around a tree with this thing. I tried to
install iU libgl1-mesa-dri
but have a depends issue. gonna have to try and start all over with
it. I must of missed the correct
order of install on the first attempt (being inexperienced at this
sort of thing) but thats how you
get experienced (hits the wall and slides down)................

On Fri, Apr 17, 2009 at 12:03 PM, Matt Zimmerman <email address hidden> wrote:
> On Fri, Apr 17, 2009 at 03:41:03PM -0000, wirechief wrote:
>> Well thats where this gets very confusing to me.
>> with this check. sudo dpkg -l |grep libgl1-mesa-dri
>> iU  libgl1-mesa-dri                            7.4-0ubuntu2~bug359392~1
>> but i don't know what the iU stands for ;)
>> I don't seem to have a slowdown but i think that is relative if i dont
>> know what
>> fast is. ;)
>
> U stands for Unpacked, i.e. the package is not properly installed.  Run
> "sudo apt-get -f install"
>
> --
>  - mdz
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[wirechief (wirechief)]

this has apt totally confused.
 cannot access libgl1-mesa-dev_7.40ubuntu2_all.deb: No such file or directory
wirechief@wirechief-laptop:/var/cache/apt/archives$ ls libgl1-mesa*.*
libgl1-mesa-dev_7.4-0ubuntu2_all.deb

On Fri, Apr 17, 2009 at 1:09 PM, wirechief <email address hidden> wrote:
> Well I got myself wrapped around a tree with this thing. I tried to
> install  iU  libgl1-mesa-dri
> but have a depends issue. gonna have to try and start all over with
> it. I must of missed the correct
> order of install on the first attempt (being inexperienced at this
> sort of thing)  but thats how you
> get experienced (hits the wall and slides down)................
>
> On Fri, Apr 17, 2009 at 12:03 PM, Matt Zimmerman <email address hidden> wrote:
>> On Fri, Apr 17, 2009 at 03:41:03PM -0000, wirechief wrote:
>>> Well thats where this gets very confusing to me.
>>> with this check. sudo dpkg -l |grep libgl1-mesa-dri
>>> iU  libgl1-mesa-dri                            7.4-0ubuntu2~bug359392~1
>>> but i don't know what the iU stands for ;)
>>> I don't seem to have a slowdown but i think that is relative if i dont
>>> know what
>>> fast is. ;)
>>
>> U stands for Unpacked, i.e. the package is not properly installed.  Run
>> "sudo apt-get -f install"
>>
>> --
>>  - mdz
>>
>> --
>> [i965] X freezes starting on April 3rd
>> https://bugs.launchpad.net/bugs/359392
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Reach out and share life, care for others,
>

--
Reach out and share life, care for others,

[Martin Pitt (pitti)]

Slightly improved version of rotate-forever, thanks Ronald for the original version! This one

  - Uses positive arithmetic, since % doesn't turn negative numbers into positive numbers and thus rotation wouldn't work at all for me (It tried to scroll to -1280).
  - add date output every two seconds to the screen (to see when it started freezeing); note that if you are unlucky, it freezes at the wrong desktop and you can't see it
  - add date output to ~/rotate-forever.log, so that after a reboot you can check whether it was the screen freezing, or X.org crashing completely

[Michael Vogt (mvo)]

I looked over the reports and it seems like the people reporting the problem all have a 8086:2a02 pci id for the primary card.

[Sebastien Bacher (seb128)]

I've a "8086:2a02 (rev 0c)" and no issue

[Nicolas Valcarcel (nvalcarcel)]

I've this issue, i've tried to solve it several times sshing into the machine and restarting gdm, but it doesn't work either. Machine needs to be rebooted.

[Dustin Kirkland  (kirkland)]

I have a Thinkpad x61, with an Intel Mobile GM965/GL960 Integrated Graphics Controller, and can confirm this issue, and the work around.

If I have compiz on, I will eventually, and inevitably have a hung system (flashing caps-lock). It is almost always an alt-tab or a ctrl-alt-left/right that triggers this.

At first I thought it was my compiz settings, so I played a little with the various different effects associated with switching applications and switching desktops. All of them seemed to trigger it, but it seemed like the "fancier" (more intensive?) triggered it sooner.

Alas, compiz generally just keeps me from getting work done, so I usually disable it. I have had none of these problems with compiz off.

Please let me know what else I can do to help.

:-Dustin

[Jesse Barnes (jbarnes-virtuousgeek)]

Here's a patch to dump error info (if we're actually getting an error) from the i915 interrupt handler. The dump albert provided should also help (looking at it now).

[Matt Zimmerman (mdz)]

Attaching a reproducer script I'm working on. It's not reliable yet, but seems to make the problem happen more frequently. Sometimes it seems to help to suspend and resume before running it.

Please let us know if this triggers the problem for you.

[Matt Zimmerman (mdz)]

Please note that when the freeze occurs, most of the system is alive and well, only the X server is wedged. It is possible to ssh into the system for debugging purposes.

When I attach to the X server when it is frozen, I see one of the following stack traces:

#0 0x00007fa8715e4cd7 in ioctl () from /lib/libc.so.6
#1 0x00007fa86f5523bd in drm_intel_gem_bo_start_gtt_access () from /usr/lib/libdrm_intel.so.1
#2 0x00007fa85e943241 in intelFinish () from /usr/lib/dri/i965_dri.so
#3 0x00007fa870251ac6 in __glXDisp_SwapBuffers (cl=0x503ff00, pc=<value optimized out>) at ../../glx/glxcmds.c:1425
#4 0x00007fa870254de2 in __glXDispatch (client=0x2065b00) at ../../glx/glxext.c:523
#5 0x000000000044e304 in Dispatch () at ../../dix/dispatch.c:437
#6 0x0000000000433d8d in main (argc=10, argv=0x7fff7ba0b9e8, envp=<value optimized out>) at ../../dix/main.c:397

or

#0 0x00007f8ff1befcd7 in ioctl () from /lib/libc.so.6
#1 0x00007f8ff020d343 in drmIoctl () from /usr/lib/libdrm.so.2
#2 0x00007f8ff020d5cb in drmCommandWrite () from /usr/lib/libdrm.so.2
#3 0x00007f8fefd7f528 in I830Sync (pScrn=0x9950a0) at ../../src/i830_accel.c:214
#4 0x00007f8fef522e6c in exaWaitSync (pScreen=0x9ca4e0) at ../../exa/exa.c:1065
#5 0x00007f8fef5240a1 in ExaDoPrepareAccess (pDrawable=0x5f89630, index=0) at ../../exa/exa.c:509
#6 0x00007f8fef528d99 in exaCopyDirty (migrate=0x7ffffc015458, pValidDst=0x168853d0, pValidSrc=<value optimized out>,
    transfer=0,
    fallback_src=0x5f89670 "��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������"...,
    fallback_dst=0x7f8fed628880 "", fallback_srcpitch=32, fallback_dstpitch=64, fallback_index=0,
    sync=0x7f8fef522e80 <exaMarkSync>) at ../../exa/exa_migration.c:218
#7 0x00007f8fef52927d in exaDoMoveInPixmap (migrate=0x7ffffc015458) at ../../exa/exa_migration.c:274
#8 0x00007f8fef529a6f in exaDoMigration (pixmaps=0x7ffffc015440, npixmaps=2, can_accel=1) at ../../exa/exa_migration.c:683
#9 0x00007f8fef52af3c in exaTryDriverComposite (op=3 '\003', pSrc=0x5f89930, pMask=0x0, pDst=0x61bffc0, xSrc=0, ySrc=0,
    xMask=<value optimized out>, yMask=<value optimized out>, xDst=<value optimized out>, yDst=<value optimized out>,
    width=<value optimized out>, height=<value optimized out>) at ../../exa/exa_render.c:642
#10 0x00007f8fef52b665 in exaComposite (op=3 '\003', pSrc=0x5f89930, pMask=0x0, pDst=0x61bffc0, xSrc=0, ySrc=0, xMask=0,
    yMask=0, xDst=0, yDst=0, width=17, height=17) at ../../exa/exa_render.c:935
#11 0x0000000000539f78 in damageComposite (op=11 '\v', pSrc=0x5f89930, pMask=0x0, pDst=0x61bffc0, xSrc=0, ySrc=0, xMask=-4,
    yMask=<value optimized out>, xDst=<value optimized out>, yDst=<value optimized out>, width=<value optimized out>,
    height=<value optimized out>) at ../../../miext/damage/damage.c:643
#12 0x00000000005325da in ProcRenderComposite (client=0x71dbe50) at ../../render/render.c:720
#13 0x000000000044e304 in Dispatch () at ../../dix/dispatch.c:437
#14 0x0000000000433d8d in main (argc=10, argv=0x7ffffc015958, envp=<value optimized out>) at ../...

[Matt Zimmerman (mdz)]

Note that repro.sh expects a 1x6 workspace layout (having lots of workspaces and applications open seems to help trigger the bug).

[Albert Damen (albrt)]

I was able to reproduce the freeze with kernel 2.6.30-rc2 and capture
intel_gpu_dump data.

[Rick Spencer (rick-rickspencer3)]

Matt Zimmerman's patch caused my computer to freeze. I was previously not experiencing this bug. I ran it once during a session where I had suspended. I hard rebooted, ran the script again, and got the freeze. So in this case, suspend/resume was not directly involved.

[Rick Spencer (rick-rickspencer3)]

For clarity, in comment 88, I meant to say Matt Zimmerman's script, not his patch.

[Michael Vogt (mvo)]

I just got confirmation from Dustin and Nicolas that they have a 8086:2a02 as well. Its a additional datapoint (but it may also mean that this is just the most widespread of the 965 family of chips).

[Bryce Harrington (bryce)]

Hi guys,

Upstream has developed a tool to collect useful data on X freezes. Unfortunately it requires the 2.6.30-rc2 kernel (and a slightly newer libdrm), so we can't put it in jaunty directly. However I've created a PPA for testers:

  https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test

You also have to install the 2.6.30-rc2 kernel, which you can get debs for here:

  http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30-rc2/

[Jesse Barnes (jbarnes-virtuousgeek)]

Here's an updated one that will dump more info.

[Bryce Harrington (bryce)]

Using the above packages and debug steps with mdz's handy script, I reproduced the freeze and grabbed this dump.

[Bryce Harrington (bryce)]

And here's the contents of my /sys/kernel/debug/dri/0

[Bryce Harrington (bryce)]

Try that again...

[Jesse Barnes (jbarnes-virtuousgeek)]

FWIW, on my T61 stock Jaunty Beta worked fine. I couldn't reproduce a hang until I did a suspend/resume, which would usually die shortly after resuming (nothing special needed). Even after updating things seem ok.

However with a 2.6.30ish kernel (from the drm-intel-next branch) things hang very quickly, before login even completes. Using my debug patch I see a bunch of instruction parse errors that don't make much sense...

[Rick Spencer (rick-rickspencer3)]

I took the latest mesa update. The repro script still hangs my machine, but I'm not seeing any regressions in compiz or metacity.

[Dustin Kirkland  (kirkland)]

FYI...

Upgraded my mesa to 7.4-0ubuntu3, rebooted, reran mdz's repro.sh script... Same issue, hung X.

:-Dustin

[Bryce Harrington (bryce)]

Crashy stuff in dmesg...

[Dustin Kirkland  (kirkland)]

Followed the instructions at:
 * https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test

Attaching the crash information here...

:-Dustin

[Dustin Kirkland  (kirkland)]

Also attaching some more diagnostics out of /sys/kernel/debug/dri/0/i915*...

:-Dustin

[Leann Ogasawara (leannogasawara)]

I've rebuilt i915.ko against the latest Jaunty git HEAD with jbranes' patch from http://launchpadlibrarian.net/25685701/i915-error-info-2.patch . Unfortunately my system with the Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) is locking up hard before I'm even able to run mdz's test script. I can't even ssh into the machine to see if any additional debug messages were logged. If anyone else could give it a try that would be great.

[Jithin Emmanuel (jithin1987)]

I am using UXA in my i965 system with no freezes for the past 2 days.

[Matthew Woerly (nattgew)]

My 8086:2a02 froze about every day for a little while, but for about a week now I haven't had any problems.

[Andres Mujica (andres.mujica)]

i was able to get a bt from a tipical freeze for this bug. *without kernel panic, nor caps lock tiling*

hope the backtrace includes interesting information.

[Bryce Harrington (bryce)]

Jithin, it would be useful if you could try running with EXA and no modifications to your xorg.conf, using the mesa 7.4-0ubuntu3, with compiz forced on (see http://ubuntuforums.org/showthread.php?t=582112). This would help us identify if reverting patch 103 solves the problem for this case, so we can know whether this bug report can be closed.

(We know there are other freeze bugs that this update does not fix, so those will have to be addressed separately.)

[Daniel Holbach (dholbach)]

No crash for me.
 - 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
 - on a Lenovo X61s
 - No exciting xorg.conf
 - Created new user (uses compiz)
 - let pitti's rotate-forever script running for 6+ hours with glxgears, googleearth, crack-attack and other stuff on the workpsaces.
 - mesa 7.4-0ubuntu2.

No crash.

[Daniel Holbach (dholbach)]

compiz 1:0.8.2-0ubuntu7.

[Soeren Sonnenburg (bugreports-nn7)]

On Fri, 2009-04-17 at 22:35 +0000, Michael Vogt wrote:
> I just got confirmation from Dustin and Nicolas that they have a
> 8086:2a02 as well. Its a additional datapoint (but it may also mean that
> this is just the most widespread of the 965 family of chips).

Yeah, but 8086:27ae here and same problem.

[Jithin Emmanuel (jithin1987)]

@Bryce. I will try with UXA off. I was using UXA because it seems to fix for me this annoying KDE bug

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/338669

Also I am using kde with kwin desktop effects so the compiz part won't apply to me.

[Rick Spencer (rick-rickspencer3)]

@Daniel, @Seb: Could you please try Matt's script to see if that can repro the freeze on your hardware?

[Soeren Sonnenburg (bugreports-nn7)]

On Sat, 2009-04-18 at 04:56 +0000, Jithin Emmanuel wrote:
> @Bryce. I will try with UXA off. I was using UXA because it seems to fix
> for me this annoying KDE bug
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
> ati/+bug/338669
>
> Also I am using kde with kwin desktop effects so the compiz part won't
> apply to me.

This bug is not related to compiz anyway as it happens with plain
metacity too.

[Jithin Emmanuel (jithin1987)]

I just had a freeze on the very first login after I turned UXA off. Seems that I have to go back to UXA ( though it breaks switch user)

[Bryce Harrington (bryce)]

Thanks Jithin.

[Jithin Emmanuel (jithin1987)]

@Bryce. I tried the repro.sh script. System froze *without UXA*. and I ran the script after turning *UXA on*. It worked smoothly.

[Bryce Harrington (bryce)]

Jithin, do you wish to pursue getting the underlying EXA fix resolved or do you consider UXA the ultimate fix for you?

If the former, then we have some additional steps for you to follow to collect necessary information to properly debug it. If the latter, I guess we can utilize other people's reports and leave this report until the UXA switch is made.

[Rick Spencer (rick-rickspencer3)]

While this is not definitive, I ran 10 instances on glx gear on various desktops, two full screen movies, one in totem and one in mplayer on two different desktops, and opened about 15 or 20 terminal windows. Matt Zimmerman's script does not work in metacity, so I manually switched desktops for 10 minutes while these apps were running, and I was not able to reproduce the freeze, which repros easily under compiz with Matt Zimmerman's script.

[Daniel Holbach (dholbach)]

Rick: no crash with 1.5h of repro.sh on
 - 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
 - on a Lenovo X61s
 - No exciting xorg.conf
 - Created new user (uses compiz)
 - mesa 7.4-0ubuntu3.
 - compiz 1:0.8.2-0ubuntu8.

[Timo Jyrinki (timo-jyrinki)]

Here's lspci -vnn of 2a02 rev 0c for which disabling the 103 max texture size patch (now in ubuntu3) helped and zero crashes now even with compiz and heavy rotate-forever usage etc.

My previous thought about disabling 103 helping only amd64 proved false, and also screen resolutions vary (machines with 1024x768, 1400x900 and no crashes, other machines with same resolutions with crashes). Also memory size seems not to matter, I (and tjaalton) used mem=1G and we couldn't get our machine to crash either.

There is probably nothing (?) people not getting the crashes with the help of latest mesa ubuntu3 can currently do to help. Note that 2a02 was now blacklisted in compiz, so if you don't have crashes you can edit /usr/bin/compiz and comment out the line with 2a02.

[Bryce Harrington (bryce)]

After updating to the official mesa-7.4-0ubuntu3 I got the freeze after about 4 hrs continuous use. Again, it happened during an alt-tab and was associated with a period of sluggish performance.

I pretty much already knew from prior testing that the fix wouldn't solve it for me, although I was surprised it lasted 4 hrs, usually it hit within 1 hour.

One thing that is quite interesting to note is that the intel_gpu_dump output is completely different from both these two cases.

[wirechief (wirechief)]

Linux wirechief-laptop 2.6.30-020630rc2-generic #020630rc2 SMP Wed Apr 15 13:20:18 UTC 2009 x86_64 GNU/Linux
sudo dpkg -l |grep mesa
ii libgl1-mesa-dev 7.4-0ubuntu3 A free implementation of the OpenGL API -- G
ii libgl1-mesa-dri 7.4-0ubuntu3 A free implementation of the OpenGL API -- D
ii libgl1-mesa-dri-dbg 7.4-0ubuntu3 Debugging symbols for the Mesa DRI modules
ii libgl1-mesa-glx 7.4-0ubuntu3 A free implementation of the OpenGL API -- G
ii libgl1-mesa-glx-dbg 7.4-0ubuntu3 Debugging symbols for the Mesa GLX runtime
ic libgl1-mesa-swx11 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- r
ii libglu1-mesa 7.4-0ubuntu3 The OpenGL utility library (GLU)
ii libglu1-mesa-dev 7.4-0ubuntu3 The OpenGL utility library -- development fi
ii libosmesa6 7.4-0ubuntu3 Mesa Off-screen rendering extension
ii mesa-common-dev 7.4-0ubuntu3 Developer documentation for Mesa
ii mesa-utils 7.4-0ubuntu3 Miscellaneous Mesa GL utilities

I am not getting freezes but am wondering why I get this with the repro.sh script
 sh repro.sh
repro.sh: 3: wmctrl: not found
repro.sh: 20: arithmetic expression: expecting primary: " * 0"

my xorg.conf is here
Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Device"
 Identifier "Onboard Intel Video"
 Option "AccelMethod" "exa"
 #Option "monitor-VGA" "ExternalVGA"
 #Option "monitor-LVDS" "OnboardLVDS"
 #Option "EXAOptimizeMigration" "true"
 #Option "MigrationHeuristic" "greedy"
 #Option "AccelMethod" "uxa"
EndSection

Section "ServerFlags"
 Option "DontZap" "False"
EndSection

cat /var/log/Xorg.0.log |grep "(EE)"
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
wirechief@wirechief-laptop:~$

[Daniel Holbach (dholbach)]

wirechief: install the wmctrl package.

[Jithin Emmanuel (jithin1987)]

@bryce although I am happy with UXA I am willing to help out with EXA, if you can tell me what to do.

[Bryce Harrington (bryce)]

On Sat, Apr 18, 2009 at 08:59:31AM -0000, Jithin Emmanuel wrote:
> @bryce although I am happy with UXA I am willing to help out with EXA,
> if you can tell me what to do.

Sure, directions are here:

  https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test/

Collect the dump and also tar up the contents of /sys/kernel/debug/dri/

[Nicolas Valcarcel (nvalcarcel)]

The script crashes my machine within a < 5 minutes window, tested 2 times already.

[Jithin Emmanuel (jithin1987)]

OMG. I had my first freeze with UXA, in 3 days. I just opened Kdevelop an tried to open a project. This is the first time I am using this app. And X froze. Though after that I could not reproduce the freeze.

[Jithin Emmanuel (jithin1987)]

After installing this new kernel will I be able to revert back to original jaunty packages?

[Jithin Emmanuel (jithin1987)]

@Bryce I cannot reproduce freeze in 2.6.30-020630rc2-generic kernel. but with 2.6.28 kernel I can.

[Dave Conniff (chronniff)]

I just installed the compiz update that blacklisted my intel gm965 video card, and so i booted into metacity, (where I realized how used to the desktop effects I have gotten), but guess what, X freezes again, this bug is seriously a pain in the ass, I mean it doesn't even seem as though anything in particular sets it off.....sometimes it will happen when you are switching between many apps and in doing so overtaxing xorg somehow, but then other times, it will happen when I am merely scrolling through some text ( although I have noticed that firefox is often involved in the freezes). Its absolutely frustrating me

[wirechief (wirechief)]

@daniel Holbrook I installed the wmctrl package. it gets further than before ...
sh repro.sh
[sudo] password for wirechief:
repro.sh: 20: arithmetic expression: expecting EOF: "1280
1280 * 0"

hmm chws 0 not sure what that is, is it line 20 that the script is blowing out ?

[wirechief (wirechief)]

looking again it appears to be a label but something with the aritmetic.

[Rick Spencer (rick-rickspencer3)]

@wirecheif

The symptom that you are seeing in Matt Zimmerman's script occurs when it is running under metacity. For folks who have updated since April 17th, they will see this because i965 are for the time being blacklisted for Jaunty so that users do not run into this freeze until the underlying problem is solved.

In the meantime, you can override the blacklist by starting compiz at the command line by issuing this command:

SKIP_CHECKS=yes compiz

[wirechief (wirechief)]

ok, that did it. the script ran and now the r61e laptop is locked up
with for terminal screens across
the screen, am going to update the bug report.

On Sat, Apr 18, 2009 at 10:40 AM, Rick Spencer
<email address hidden> wrote:
> @wirecheif
>
> The symptom that you are seeing in Matt Zimmerman's script occurs when
> it is running under metacity. For folks who have updated since April
> 17th, they will see this because i965 are for the time being blacklisted
> for Jaunty so that users do not run into this freeze until the
> underlying problem is solved.
>
> In the meantime, you can override the blacklist by starting compiz at
> the command line by issuing this command:
>
> SKIP_CHECKS=yes compiz
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[wirechief (wirechief)]

here is the bug report...

[Jesse Barnes (jbarnes-virtuousgeek)]

Leann, I was seeing the same thing (hard lockup at login) with 2.6.30-rc2 from the drm-intel-next branch with my patch applied. It could be due to my patch or some other interaction with more recent kernels. I'm trying to reproduce the problem with 2.6.28 now (first the Ubuntu kernel then one with my patch applied), still waiting for the test script to crash my machine though.

[Timo Jyrinki (timo-jyrinki)]

Could someone who is easily getting the crash (with eg. repro.sh) try albert's tip?

14:40 < albert23> With Virtual 2048 2048 in display subsection in xorg.conf I could run the test script without freezing for more then an hour
14:40 < albert23> After removing that etting X froze again in less then 2 minutes
14:41 < albert23> I originally used it to solve the slow cube rotation. Effect is that you get more EXA offscreen memory
14:43 < albert23> For me EXA offscreen memory goes up from 19 to 49 MB

[wirechief (wirechief)]

can you give a example for this setting (make sure its inserted
correctly) i dont have a display
subsection.

On Sat, Apr 18, 2009 at 12:49 PM, Timo Jyrinki <email address hidden> wrote:
> Could someone who is easily getting the crash (with eg. repro.sh) try
> albert's tip?
>
> 14:40 < albert23> With Virtual 2048 2048 in display subsection in xorg.conf I could run the test script without freezing for more then an hour
> 14:40 < albert23> After removing that etting X froze again in less then 2 minutes
> 14:41 < albert23> I originally used it to solve the slow cube rotation. Effect is that you get more EXA offscreen memory
> 14:43 < albert23> For me EXA offscreen memory goes up from 19 to 49 MB
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Jithin Emmanuel (jithin1987)]

I am not able to reproduce freeze with 30 rc2 kernel but with 28 I can. I used the repro.sh script.

[Rick Spencer (rick-rickspencer3)]

I crudely hacked Matt Zimmerman's script to try to stress metacity in an effort to confirm that falling back to metacity will, in fact, stop the freeze from occurring. As far as I can tell wmcntrl -o does not work under metacity, so the modified script uses wmcntrl -s, which simply switches to the designated workspace. Note that shell scripting is far from my forte, so any adjustments to the script are most welcome. Also, note that you have to:
1. Install wmcntrl
2. Install mplayer
3. Edit the script to specify your screen height and width.

Under compiz, Matt Zimmerman's script freezes my computer in a few minutes. Under metacity, my script did not freeze my computer in 35 minutes. I also did a suspend/resume, and ran the script for another 45 minutes without freezing.

[Alexey Osipov (lion-simba)]

Confirm that bug but with NVIDIA 7600 GT. Proprietary driver version 180.
So I think that's not only intel issue.

[Bryce Harrington (bryce)]

On Sat, Apr 18, 2009 at 05:58:31PM -0000, Alexey Osipov wrote:
> Confirm that bug but with NVIDIA 7600 GT. Proprietary driver version 180.
> So I think that's not only intel issue.

No, let's not let the focus of this bug drift. We even already are
pretty sure that we are seeing multiple different bugs with the GPU
lockups on -intel, and that's with the same hw and driver.

You have the same *symptom* (a frozen X) but it has to be a separate
bug. This bug is ONLY going to focus on freezes with -intel on i965.

Indeed, the troubleshooting tools and approach we're using is only
applicable to -intel anyway.

Furthermore, since you're using the proprietary driver, your problem
probably can't be fixed by Ubuntu anyway.

[Sebastien Bacher (seb128)]

interesting new comments, as written before on IRC I'm using stock jaunty I've no speed or hang issue, the only revelant change I've in the xorg configuration is:

" SubSection "Display"
  Virtual 2840 1050
 EndSubSection""

I've just commented it and tried mdz repro code and workspace is immediatly slugish, I didn't get a freeze yet but that seems to make a real difference

[wirechief (wirechief)]

I tried adding this to my xorg.conf
SubSection "Display"
               Virtual 2048 2048
EndSubSection
when i run the script like this:
 sh repro.sh
[sudo] password for wirechief:
repro.sh: 20: arithmetic expression: expecting EOF: "1280
1280 * 0"
it just stopped, I don't know if its the adding of this or not, I will comment it out to see if the script works.

[Jesse Barnes (jbarnes-virtuousgeek)]

I still haven't been able to reproduce this. I did notice that Albert, Dustin and Bryce's intel_gpu_dump output was identical though (all had what looked like i965 render commands in them). Some people have reported that using EXA greedy migration made the bug go away, I wonder if disabling render accel altogether would as well (ExaNoComposite true in xorg.conf)? Can someone who's seeing this frequently give that a try?

So far the closest I've come to seeing this with Jaunty is by starting 50 instances of glxgears. That makes X pretty much unusable (all my windows grey out and no other rendering seems possible). That's pretty pathological though, so probably isn't the problem, though it does indicate some issues with our GPU scheduler under high load.

[Zack Evans (zevans23)]

@Sebastien: The Intel driver doesn't do acceleration with Virtual over 2048 - known limitation

[Henning Eggers (henninge)]

My current situation:
After upgrading to jaunty I first experienced a heavy drop in video performance. Later I experienced the first freeze, related to maximizing an application window, I think. A few days later the screen froze again, twice within about two hours. I was given the hint to disable compiz which I did. No more freezes since then.

[Tom Jaeger (thjaeger)]

I still see freezes with render acceleration turned off, although I'm
not quite sure if it's the same issue that everyone else is experiencing
(I've had these freezes for at least half a year). I can reliable
reproduce the freeze by opening ~10 fullscreen windows, minimizing some
of them and then pressing Alt+Tab. I've attached a backtrace and a gpu
dump.

JesseBarnes wrote:
> I still haven't been able to reproduce this. I did notice that Albert,
> Dustin and Bryce's intel_gpu_dump output was identical though (all had
> what looked like i965 render commands in them). Some people have
> reported that using EXA greedy migration made the bug go away, I wonder
> if disabling render accel altogether would as well (ExaNoComposite true
> in xorg.conf)? Can someone who's seeing this frequently give that a
> try?
>
> So far the closest I've come to seeing this with Jaunty is by starting
> 50 instances of glxgears. That makes X pretty much unusable (all my
> windows grey out and no other rendering seems possible). That's pretty
> pathological though, so probably isn't the problem, though it does
> indicate some issues with our GPU scheduler under high load.
>

[Matt Zimmerman (mdz)]

On Sat, Apr 18, 2009 at 09:17:10PM -0000, Zack Evans wrote:
> @Sebastien: The Intel driver doesn't do acceleration with Virtual over
> 2048 - known limitation

Sebastien said he was running fine with the large Virtual setting, but that
he got sluggish performance after *removing* it.

I think that makes two independent reports of setting Virtual avoiding the
problem somehow.

--
 - mdz

[Tom Jaeger (thjaeger)]

> I think that makes two independent reports of setting Virtual avoiding the
> problem somehow.

I still get freezes even with offscreen pixmap memory increased. But
the setting is a keeper anyway, since it improves compiz performance
noticeably. Is there any reason that the intel driver is so stingy with
  pixmap memory (at 2048x2048 there's only room for 3 fullscreen
pixmaps, for example)?

[Rick Spencer (rick-rickspencer3)]

@Jesse:
I ran repro.sh with this:

Section "Device"
 Identifier "Configured Video Device"
 Option "AccelMethod" "EXA"
        Option "ExaNoComposite" "true"
EndSection

and then this

Section "Device"
 Identifier "Configured Video Device"
 #Option "AccelMethod" "EXA"
        Option "ExaNoComposite" "true"
EndSection

My computer froze as per usual. Please let me know if I didn't set it correctly so I can try again.

[Jithin Emmanuel (jithin1987)]

Finally I was able to reproduce the freeze on 2.6.30-020630rc2 kernel, though the repro.sh script did not help. It just happened pure randomly.

Attaching my freeze_dump.txt. I could not find any files at /sys/kernel/debug/dri/

[Timo Jyrinki (timo-jyrinki)]

wirechief: Regarding your problems in running repro.sh, it's not posix compatible script so you'll want to run it eg. "bash repro.sh", not "sh repro.sh". Also, do not forget to set 6 workspaces (by right clicking on the workspace switcher) instead of the default 2 or 4.

[Vincenzo Ciancia (vincenzo-ml)]

I have a 8086:27a2 card and it froze in jaunty, likely for the same problem.

[Bryce Harrington (bryce)]

On Sun, Apr 19, 2009 at 12:21:50AM -0000, Jithin Emmanuel wrote:
> Attaching my freeze_dump.txt. I could not find any files at
> /sys/kernel/debug/dri/

Probably because you have to explicitly mount /sys/kernel/debug

[Jithin Emmanuel (jithin1987)]

I did mount.

On Sun, Apr 19, 2009 at 3:18 PM, Bryce Harrington <<email address hidden>
> wrote:

> On Sun, Apr 19, 2009 at 12:21:50AM -0000, Jithin Emmanuel wrote:
> > Attaching my freeze_dump.txt. I could not find any files at
> > /sys/kernel/debug/dri/
>
> Probably because you have to explicitly mount /sys/kernel/debug
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
W. C. Fields <http://www.brainyquote.com/quotes/authors/w/w_c_fields.html>
- "A rich man is nothing but a poor man with money."

[Albert Damen (albrt)]

On Sat, 2009-04-18 at 21:17 +0000, Zack Evans wrote:
> @Sebastien: The Intel driver doesn't do acceleration with Virtual over
> 2048 - known limitation
>

That limitation does not apply to GM965.

[Jerone Young (jerone)]

Wikipedia has a table of all the Intel cards here (along with pci ids):
http://en.wikipedia.org/wiki/Intel_GMA

 The GM965 is questions is the x3100 mobile part.

@Vincenzo
   Your card is a GMA 950 card.

[Albert Damen (albrt)]

On Sat, 2009-04-18 at 21:02 +0000, JesseBarnes wrote:
> I wonder if disabling render accel altogether would as well (ExaNoComposite true
> in xorg.conf)? Can someone who's seeing this frequently give that a try?

With ExaNoComposite true X still froze. Actually, it even seems to
freeze faster. First attempt the freeze happened when repro.sh was
opening terminal windows. Second time the freeze happened in some 30
seconds. Normally it takes me about 2 to 3 minutes to get the freeze.
Attached are the dump and logs of the second test.

[Jerone Young (jerone)]

- ran rotate-forever for 45 min with no crash
      * even launched 5 instances of glxgears

Then I ran repo.sh
 - ran fine for about 10 minutes, then I started to interact with the machine to close it out, and as I was about to close the huge glxgears window it crashed the system.

I have a Thinkpad T61 with i965 chipset & x3100 (GM965), 4 gigs of RAM, & a Intel Core 2 Dou T7300 2.00GHZ

[Jesse Barnes (jbarnes-virtuousgeek)]

@Albert
Assuming you're seeing the same root problem that vindicates the 965 render acceleration code.

[Matt Zimmerman (mdz)]

On Sun, Apr 19, 2009 at 03:23:44PM -0000, Jerone Young wrote:
> Then I ran repo.sh
> - ran fine for about 10 minutes, then I started to interact with the machine to close it out, and as I was about to close the huge glxgears window it crashed the system.

When you say "crashed the system" are you speaking literally? The normal
symptom for this bug is that the X server gets wedged, but the system does
NOT crash (it's possible to ssh in and debug). However, at least Dustin has
reported kernel panics (flashing caps lock), which may or may not be a
different bug.

--
 - mdz

[Bryce Harrington (bryce)]

dumps from my latest freeze on my laptop.

[Oliver Grawert (ogra)]

using a 8086:2a02 (rev 03) card as reported by lspci -n i could run the script for about 20h without hitting a lockup ...
i *do* see lockups though in normal operation as well as the massive slowdown with alt-tab and during workspace switching (which might be another bug)

[Ken VanDine (ken-vandine)]

I tested repro.sh on my G965 (8086:29a3), no lockups. Tested with both default X conf and with UXA.

[Andres Monroy-Hernandez (andresmh)]

After updating my Jaunty box I could not use Compiz anymore. Someone pointed out that this bug was the cause. I am running:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

[Rick Spencer (rick-rickspencer3)]

@Andres -

Correect. compiz is (for the time being) blacklisting this particular chip so that users do not lose data to encountering a freeze. The blacklisting will be removed when this bug is fixed.

[Soeren Sonnenburg (bugreports-nn7)]

On Mon, 2009-04-20 at 14:25 +0000, Rick Spencer wrote:
> @Andres -
>
> Correect. compiz is (for the time being) blacklisting this particular
> chip so that users do not lose data to encountering a freeze. The
> blacklisting will be removed when this bug is fixed.

At least for me disabling compiz is of no use as I get freezes with
plain metacity too.

[Martin Pitt (pitti)]

Soeren Sonnenburg [2009-04-20 15:03 -0000]:
> At least for me disabling compiz is of no use as I get freezes with
> plain metacity too.

Are you using any 3D application, 3D screensaver, or anything like
that?

[Jithin Emmanuel (jithin1987)]

Well you are not alone. I have freezes with plain kwin with out any desktop
effects. I believe disabling effects just reduces slightly the frequency of
freezes not completely remove them.

For kubuntu will the desktop effects be turned off by default for this chip?

On Mon, Apr 20, 2009 at 8:33 PM, Soeren Sonnenburg <email address hidden>wrote:

> On Mon, 2009-04-20 at 14:25 +0000, Rick Spencer wrote:
> > @Andres -
> >
> > Correect. compiz is (for the time being) blacklisting this particular
> > chip so that users do not lose data to encountering a freeze. The
> > blacklisting will be removed when this bug is fixed.
>
> At least for me disabling compiz is of no use as I get freezes with
> plain metacity too.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Jonathan Swift<http://www.brainyquote.com/quotes/authors/j/jonathan_swift.html>
- "May you live every day of your life."

[Zack Evans (zevans23)]

I've been thinking about the tangle of package versions we've got now and it prompted a couple of thoughts.

1. What happens when you have libgl1-mesa-glx AND lib-gl1-mesa-swx11 installed?

AIUI -glx is the hw-acceleration version of OpenGL and will therefore trigger any DRI bugs we have and generally sweat the graphics hardware fully, whereas -swx11 is a software rendering engine for OpenGL and unlikely to use the full capabilities of the chipset.

Could it be we have some people here with swx11 accidentally installed therefore putting them into software render mode, and therefore going -around- any bugs in the hw?

I notice wirechief has ended up with both installed... glx "official" 7.4-0ubuntu3 but swx11 from Bryce's purple version.

2. What libosmesa6 do - "Mesa Off-screen rendering extension"

I don't have it installed, I guess because no other package has ever pulled it in. If I ask to install -swx11 then I need to install this library too... so I haven't, yet, but might be interesting to see if it changes my symptoms.

I've gone to 7.4-0ubuntu3 and I CAN now boot with EXA + greedy under 2.6.30RC2 - I had a freeze straightaway in X with 7.4.0ubuntu2. So something's fixed in EXA mode at least...

[Soeren Sonnenburg (bugreports-nn7)]

On Mon, 2009-04-20 at 15:12 +0000, Martin Pitt wrote:
> Soeren Sonnenburg [2009-04-20 15:03 -0000]:
> > At least for me disabling compiz is of no use as I get freezes with
> > plain metacity too.
>
> Are you using any 3D application, 3D screensaver, or anything like
> that?

No nothing. But please note that I am on debian-sid but do have the very
same symptons described here all over the place (freeze of screen, mouse
cursor still working). As I stated before debian does not have all the
ubuntu patches but unfortunately everything upgraded, xorg, mesa, intel
drivers (drm and display driver) at the same time. However, I still get
the crash when downgrading the intel driver to 2.6.3 (which was known to
work reliably). Unfortunately I had to stop there, the bug seems to
complex for proper bisecting (under my time constraints).

[Mingming Ren (portis25)]

I also experience this kind of freeze. It appears quite often when I'm using compiz. It freezes, but the mouse can move.
Then I turned off compiz, and upgraded mesa, xserver, intel driver, and kernel to the very up-to-date git version.

It worked for two days without freeze, until this afternoon. It freezed, but the mouse can still move.

[wirechief (wirechief)]

So far I have not had any freezes. and you are right this is installed.
ic libgl1-mesa-swx11 7.4-0ubuntu2~bug359392~1
I thought about removing it and just updating, but have not done so.
perhaps I should and see if freezes start.
however I am also unable to run the repro.sh perhaps i need to re-run
SKIP_CHECKS=yes compiz and that will allow the script to run but at this
point I know the script will freeze my system and freeze it right away.
(not fun)

On Mon, Apr 20, 2009 at 11:21 AM, Zack Evans <email address hidden> wrote:
> I've been thinking about the tangle of package versions we've got now
> and it prompted a couple of thoughts.
>
> 1. What happens when you have libgl1-mesa-glx AND lib-gl1-mesa-swx11
> installed?
>
> AIUI -glx is the hw-acceleration version of OpenGL and will therefore
> trigger any DRI bugs we have and generally sweat the graphics hardware
> fully, whereas -swx11 is a software rendering engine for OpenGL and
> unlikely to use the full capabilities of the chipset.
>
> Could it be we have some people here with swx11 accidentally installed
> therefore putting them into software render mode, and therefore going
> -around- any bugs in the hw?
>
> I notice wirechief has ended up with both installed... glx "official"
> 7.4-0ubuntu3 but swx11 from Bryce's purple version.
>
> 2. What libosmesa6 do - "Mesa Off-screen rendering extension"
>
> I don't have it installed, I guess because no other package has ever
> pulled it in. If I ask to install -swx11 then I need to install this
> library too... so I haven't, yet, but might be interesting to see if it
> changes my symptoms.
>
> I've gone to 7.4-0ubuntu3 and I CAN now boot with EXA + greedy under
> 2.6.30RC2 - I had a freeze straightaway in X with 7.4.0ubuntu2. So
> something's fixed in EXA mode at least...
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[wirechief (wirechief)]

nope i needed to use bash in front of the script. its currently running....

On Mon, Apr 20, 2009 at 12:28 PM, wirechief <email address hidden> wrote:
> So far I have not had any freezes. and you are right this is installed.
> ic  libgl1-mesa-swx11                          7.4-0ubuntu2~bug359392~1
> I thought about removing it and just updating, but have not done so.
> perhaps I should and see if freezes start.
> however I am also unable to run the repro.sh perhaps i need to re-run
> SKIP_CHECKS=yes compiz and that will allow the script to run but at this
> point I know the script will freeze my system and freeze it right away.
> (not fun)
>
> On Mon, Apr 20, 2009 at 11:21 AM, Zack Evans <email address hidden> wrote:
>> I've been thinking about the tangle of package versions we've got now
>> and it prompted a couple of thoughts.
>>
>> 1. What happens when you have libgl1-mesa-glx AND lib-gl1-mesa-swx11
>> installed?
>>
>> AIUI -glx is the hw-acceleration version of OpenGL and will therefore
>> trigger any DRI bugs we have and generally sweat the graphics hardware
>> fully, whereas -swx11 is a software rendering engine for OpenGL and
>> unlikely to use the full capabilities of the chipset.
>>
>> Could it be we have some people here with swx11 accidentally installed
>> therefore putting them into software render mode, and therefore going
>> -around- any bugs in the hw?
>>
>> I notice wirechief has ended up with both installed... glx "official"
>> 7.4-0ubuntu3 but swx11 from Bryce's purple version.
>>
>> 2. What libosmesa6 do - "Mesa Off-screen rendering extension"
>>
>> I don't have it installed, I guess because no other package has ever
>> pulled it in. If I ask to install -swx11 then I need to install this
>> library too... so I haven't, yet, but might be interesting to see if it
>> changes my symptoms.
>>
>> I've gone to 7.4-0ubuntu3 and I CAN now boot with EXA + greedy under
>> 2.6.30RC2 - I had a freeze straightaway in X with 7.4.0ubuntu2. So
>> something's fixed in EXA mode at least...
>>
>> --
>> [i965] X freezes starting on April 3rd
>> https://bugs.launchpad.net/bugs/359392
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Reach out and share life, care for others,
>

--
Reach out and share life, care for others,

[Jesse Barnes (jbarnes-virtuousgeek)]

@Bryce
Your last hang is right after a render accel request again (the GPU dump indicates that), but the interrupt state and such look ok:
Interrupt enable: 00020053 <- user interrupts are on, which is good since we use those to wait for requests to complete
Interrupt identity: 00000000 <- no interrupts pending atm, which should be ok
Interrupt mask: fffcdfac
Pipe A stat: 00040000 <- pipe stats shouldn't matter here, but fwiw vblank interrupts are on
Pipe B stat: 00000206 <- and one has occurred on pipe B
Interrupts received: 308241 <- interrupt count seems reasonable (you'll get lots of them)
Current sequence: 553893 <- hw finished with request # 553893
Waiter sequence: 553897 <- most recent request #
IRQ sequence: 553890 <- most recently signalled request completion (should be <= current sequence, so it's ok)

The active request list looks ok too, the seqnos are all in the future though, which means software is still waiting for rendering to complete... Just to confirm, if you repeatedly cat i915_gem_interrupt you don't see the interrupts received or any of the sequence numbers change?

[wirechief (wirechief)]

it has been running now for over 40 minutes, simply amazing from my
first experience with it.
im gonna close all those windows now and terminate the test.

On Mon, Apr 20, 2009 at 12:29 PM, wirechief <email address hidden> wrote:
> nope i needed to use bash in front of the script. its currently running....
>
> On Mon, Apr 20, 2009 at 12:28 PM, wirechief <email address hidden> wrote:
>> So far I have not had any freezes. and you are right this is installed.
>> ic  libgl1-mesa-swx11                          7.4-0ubuntu2~bug359392~1
>> I thought about removing it and just updating, but have not done so.
>> perhaps I should and see if freezes start.
>> however I am also unable to run the repro.sh perhaps i need to re-run
>> SKIP_CHECKS=yes compiz and that will allow the script to run but at this
>> point I know the script will freeze my system and freeze it right away.
>> (not fun)
>>
>> On Mon, Apr 20, 2009 at 11:21 AM, Zack Evans <email address hidden> wrote:
>>> I've been thinking about the tangle of package versions we've got now
>>> and it prompted a couple of thoughts.
>>>
>>> 1. What happens when you have libgl1-mesa-glx AND lib-gl1-mesa-swx11
>>> installed?
>>>
>>> AIUI -glx is the hw-acceleration version of OpenGL and will therefore
>>> trigger any DRI bugs we have and generally sweat the graphics hardware
>>> fully, whereas -swx11 is a software rendering engine for OpenGL and
>>> unlikely to use the full capabilities of the chipset.
>>>
>>> Could it be we have some people here with swx11 accidentally installed
>>> therefore putting them into software render mode, and therefore going
>>> -around- any bugs in the hw?
>>>
>>> I notice wirechief has ended up with both installed... glx "official"
>>> 7.4-0ubuntu3 but swx11 from Bryce's purple version.
>>>
>>> 2. What libosmesa6 do - "Mesa Off-screen rendering extension"
>>>
>>> I don't have it installed, I guess because no other package has ever
>>> pulled it in. If I ask to install -swx11 then I need to install this
>>> library too... so I haven't, yet, but might be interesting to see if it
>>> changes my symptoms.
>>>
>>> I've gone to 7.4-0ubuntu3 and I CAN now boot with EXA + greedy under
>>> 2.6.30RC2 - I had a freeze straightaway in X with 7.4.0ubuntu2. So
>>> something's fixed in EXA mode at least...
>>>
>>> --
>>> [i965] X freezes starting on April 3rd
>>> https://bugs.launchpad.net/bugs/359392
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>
>>
>>
>> --
>> Reach out and share life, care for others,
>>
>
>
>
> --
> Reach out and share life, care for others,
>

--
Reach out and share life, care for others,

[Jesse Barnes (jbarnes-virtuousgeek)]

Here's an alternate error state patch (the interrupt one I sent earlier still needs work). It should add an i915_error_state file to debugfs, which can be capture at hang time along with the rest of the files in that directory.

[Albert Damen (albrt)]

Attached are the results with Jesse's error state patch.
After the freeze i915_gem_interrupt did not change.

[Jesse Barnes (jbarnes-virtuousgeek)]

> Attached are the results with Jesse's error state patch.
> After the freeze i915_gem_interrupt did not change.
>
> ** Attachment added: "gpudump-errorstate.tar.gz"
> http://launchpadlibrarian.net/25802051/gpudump-errorstate.tar.gz

Ok, so you got an instruction parser error, which indicates we've
probably executed junk or a corrupted batch buffer. Can you try
running your environment under INTEL_DEBUG=batch to see batchbuffers as
they're executed?

[Joachim Nilsson (troglobit)]

Just upgraded and noticed my chipset being blacklisted due to this buglet. For the record:

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

No freezes seen before. Actually this (before the upgrade) has been the first time I've been able to run Compiz on my extended desktop (1920x1200 + 1280x800) with the ThinkPad T61 in my dock. That was cool, so I'm quite interested in this bug.

My xorg.conf:
Section "Screen"
 Identifier "Configured Screen Device"
 Device "Configured Video Device"
 SubSection "Display"
  Virtual 3200 1200
 EndSubSection
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Option "AccelMethod" "uxa"
EndSection

[seldon7 (ubuntu-pengo)]

in case its of any use - I think I'm getting the same error on both the final beta and also the RC of Jaunty. NVidia6800GS card on a Pentium 4 3GHz chip. I get a black unresponsive screen after several hours use. HDD seems to be active.

I seemed to get more of these black screens when I was overclocking the CPU, so dropped it back to default and now only about once every 6-12 hours. Doesn't seem to be a temperature issue (I monitor temp closely). Just my impression - nothing concrete.

Resolves itself / doesn't occur when I'm running Intrepid.

[Martin Pitt (pitti)]

Joachim Nilsson [2009-04-21 2:18 -0000]:
> SubSection "Display"
> Virtual 3200 1200
> EndSubSection

That's the second person who reports no freezes with a larger
VirtualSize. Jesse, do you know why this could happen? Maybe if the
VirtualSize is big enough you can fit all of the viewports into the
backbuffer without the need of copying them in and out on viewport
switches?

[Joachim Nilsson (troglobit)]

So my running with UXA is not relevant? Good thing I pasted in my whole xorg.conf then. :)

[Matt Zimmerman (mdz)]

On Tue, Apr 21, 2009 at 03:59:57AM -0000, seldon7 wrote:
> in case its of any use - I think I'm getting the same error on both the
> final beta and also the RC of Jaunty. NVidia6800GS card on a Pentium 4
> 3GHz chip. I get a black unresponsive screen after several hours use.
> HDD seems to be active.

You have a different problem, please look for a bug which matches your
symptoms, and if you don't find one, file a new one. Neither your hardware
nor your symptoms match those in this bug.

--
 - mdz

[Soeren Sonnenburg (bugreports-nn7)]

On Tue, 2009-04-21 at 07:45 +0000, Matt Zimmerman wrote:
> On Tue, Apr 21, 2009 at 03:59:57AM -0000, seldon7 wrote:
> > in case its of any use - I think I'm getting the same error on both the
> > final beta and also the RC of Jaunty. NVidia6800GS card on a Pentium 4
> > 3GHz chip. I get a black unresponsive screen after several hours use.
> > HDD seems to be active.
>
> You have a different problem, please look for a bug which matches your
> symptoms, and if you don't find one, file a new one. Neither your hardware
> nor your symptoms match those in this bug.

Just to second that, I haven't seen the problem to occur on ATI hardware
either (on same setup). So it really seems to be some intel specific
problem.

[Matt Zimmerman (mdz)]

On Tue, Apr 21, 2009 at 06:24:53AM -0000, Martin Pitt wrote:
> Joachim Nilsson [2009-04-21 2:18 -0000]:
> > SubSection "Display"
> > Virtual 3200 1200
> > EndSubSection
>
> That's the second person who reports no freezes with a larger
> VirtualSize. Jesse, do you know why this could happen? Maybe if the
> VirtualSize is big enough you can fit all of the viewports into the
> backbuffer without the need of copying them in and out on viewport
> switches?

That's three: albert23, Sebastien Bacher and Joachim Nilsson.

I wonder if it avoids the problem completely or just makes it harder to
trigger.

--
 - mdz

[Dave Conniff (chronniff)]

I thought it might be worth mentioning that I installed the xorg crack pushers ppa repo a few days ago, (latest intel develoment snapshots), and it has reduced the frequency of the X lockups, I have only had one or two in the entire time that I have had them isntalled.....Also, there is no reason that you should lose data during these lockups since most of the system is infact running fine, just not the part that you can see with your own eyes......I have been successful in not losing any data that I know if through the careful use of the linux magic SysRq commands, which have no problem syncing the filesystem and rebooting it since the rest of the hardware is not locking up

[Chris Broekema (broekema)]

I'm using a larger VirtualSize (3200 1280) with the previous version of Mesa (so including 103_bump_965_texture_limit.diff). I do experience occasional freezes, so I don't think it completely solves the problem. Reading back I don't think the above patch is a suspect anymore, but I'll upgrade Mesa to the current version and see if it freezes again.

[vervelover (alessiopangos)]

No frezees for me with "UXA" and "migration heuristic greedy" enabled in my xorg.conf, not even with the repro.sh script running togheter with skype rhytmbox and mozilla and compiz. I have freezes as soon as I disable the migration heuristic option. Everything seems just ok with UXA, I have no reasons to try EXA now. Glxgears is faster with EXA but games run better with UXA so what's the point?

Anyway, even with UXA and migration heuristic greedy enabled, I can reproduced a system freeze anytime I enable windows reflection in the compiz reflection plugin. If it doesn't happen immediatly, it happens after a few minutes anyway.

[Jithin Emmanuel (jithin1987)]

UXA with 2.6.28 kernel has a lot of side effects like switch user fails. I installed kernel 2.6.29.1 and xserver-xorg-video-intel from xorg-edgers .
This seems to have fixed all of the UXA issues I faced and I am not having any freezes.

[vervelover (alessiopangos)]

just experienced a freeze, now switching to xorg-edgers driver, but with jaunty standard kernel. No freezes since now.

[Albert Damen (albrt)]

> Can you try running your environment under INTEL_DEBUG=batch to see batchbuffers as
> they're executed?

I started gdm with sudo INTEL_DEBUG=batch /etc.init.d/gdm start and took
the last 5.000 lines from the gdm log (gdm-tail.log).

[Jesse Barnes (jbarnes-virtuousgeek)]

On Tue, 21 Apr 2009 14:45:09 -0000
Albert Damen <email address hidden> wrote:

> > Can you try running your environment under INTEL_DEBUG=batch to see
> > batchbuffers as they're executed?
>
> I started gdm with sudo INTEL_DEBUG=batch /etc.init.d/gdm start and
> took the last 5.000 lines from the gdm log (gdm-tail.log).
>
>
> ** Attachment added: "intel_debug.tar.gz"
> http://launchpadlibrarian.net/25826804/intel_debug.tar.gz

Ah excellent, but can you include the whole log?

Thanks,
--
Jesse Barnes, Intel Open Source Technology Center

[Jesse Barnes (jbarnes-virtuousgeek)]

On Tue, 21 Apr 2009 14:45:09 -0000
Albert Damen <email address hidden> wrote:

> > Can you try running your environment under INTEL_DEBUG=batch to see
> > batchbuffers as they're executed?
>
> I started gdm with sudo INTEL_DEBUG=batch /etc.init.d/gdm start and
> took the last 5.000 lines from the gdm log (gdm-tail.log).
>
>
> ** Attachment added: "intel_debug.tar.gz"
> http://launchpadlibrarian.net/25826804/intel_debug.tar.gz

And one more thing... while removing a bunch of old code from the
driver yesterday, Eric noticed a pretty bad bug in GEM/DRI1 interaction
that would cause the ring buffer to get stomped if the kernel ever had
to perform an eviction during an operation (which can happen when the
GPU is busy and lots of objects are mapped).

Disabling render accel (ExaNoComposite true) and not using video should
avoid that particular issue though. Can anyone reproduce the issue
with both of those features disabled?

[Francois Lesueur (f-lesueur)]

Hello,

Not verified if this is the same bug, but looks very similar. Using Elisa Media Center (OpenGL), I encountered system crashes. Elisa in idle mode or navigating in menus is ok, but when I launch a movie it freezes after a few minutes. When freezed, the computer responds to ping requests but AFAIK I was not able to ssh into it. Of course, no ALT+F1 and no Ctrl-Alt-Delete responding...

Freevo with mplayer using xv output is ok. MPlayer with gl/gl2 output is ok too.

My xorg.conf is empty (only the self-generated part, no option for the vga device).

VGA card is :
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10)
        Subsystem: Micro-Star International Co., Ltd. Device [1462:7529]

Tonight, I upgraded the intel driver to 2.7 using Stefan Glasenhardt PPA. After a few tens of minutes, there is still no crash, which is very different from previously...

[VladNistor (vladnistor)]

This bug usually appeared within 5 minutes of logging into kde with compiz on. After I moved to UXA I no longer get X hangs. I have not tried the repro.sh yet, but it hasn't appeared within 5 minutes after several restarts.
I'm using kernel 2.6.29-02062901-generic and heuristics "greedy".

[Botond Szász (boteeka)]

With standard Jaunty kernel, uxa acceleration, and greedy migrationheuristics, if reflections plugin is enabled in compiz, Gnome wouldn't even start. It will freeze after a couple of seconds of the startup sound playing. After I managed to disable the reflections plugin, it is working, at least as of yet.

[Albert Damen (albrt)]

On Tue, 2009-04-21 at 11:31 -0700, Jesse Barnes wrote:
> but can you include the whole log?

Sure, this is the full log of the same freeze of
http://launchpadlibrarian.net/25826804/intel_debug.tar.gz

[Jesse Barnes (jbarnes-virtuousgeek)]

Ok so the bug I mentioned in 196 doesn't actually exist, so ignore that request.

However Eric is now worried about the buffer reuse we're seeing in the dumps. If caching is at all wrong or we're not taking care to reset the buffer contents correctly between reuse it could easily cause problems.

Buffer object reuse can be disabled in the 3D driver by setting the bo_reuse DRI variable to 0 (it defaults to 1). The 2D driver needs to be patched to avoid re-use though:

diff --git a/src/i830_driver.c b/src/i830_driver.c
index 6ec2cdd..c43a7be 100644
--- a/src/i830_driver.c
+++ b/src/i830_driver.c
@@ -2835,7 +2835,7 @@ i830_init_bufmgr(ScrnInfoPtr pScrn)
         batch_size = 4096;

       pI830->bufmgr = intel_bufmgr_gem_init(pI830->drmSubFD, batch_size);
- intel_bufmgr_gem_enable_reuse(pI830->bufmgr);
+// intel_bufmgr_gem_enable_reuse(pI830->bufmgr);
    } else {
       assert(pI830->FbBase != NULL);

[Flavio Capobianco (norkov)]

I don't know if I'm contributing anything new but this is my experience.

I've got the GM965/GL960 [8086:2a02] (rev 0c) on my laptop.

I've been experiencing frequent freezes, always while using compiz.

Loose binding seemed to make things better, but there were terrible wrong renderings, such as no menu highlighting.

When turning on reflection plug-in the freeze was almost instantaneous.

I tried many things such as rolling back to the latest Intrepid Ibex display drivers and trying UXA with greedy. It didn't help.

Following compiz troubleshooting wiki I then tried

LIBGL_ALWAYS_INDIRECT=1 INTEL_BATCH=1 compiz --replace --indirect-rendering --sm-disable ccp &

and option "XAANoOffscreenPixmaps" "true" in my xorg.conf and nothing else.

This made things better. I tested it with reflection plugin on and it took a long time to freeze. I opened lots of nautilus windows, alt tabed, faded to desktop for several minutes and nothing happened. Only after I thought it wouldn't be freezing after all, I opened a terminal and typed a command and it freezed.

[Bryce Harrington (bryce)]

I've added an -intel 2.6.3-0ubuntu10~bug359392~1 package with Jesse's patch to this ppa for testing purposes:

  https://edge.launchpad.net/~bryceharrington/+archive/purple/

[Bryce Harrington (bryce)]

After booting the aforementioned patch and re-running mdz's script, it froze after a few minutes with this gpu state.

[Jithin Emmanuel (jithin1987)]

I am now facing a new problem, my gnome-terminal or konsole is not taking
Escape key. So in vim if I go to insert mode I cannot come back. I am not
having this problem with pure console login.
Could this be related to x server?

On Wed, Apr 22, 2009 at 6:44 AM, Bryce Harrington <<email address hidden>
> wrote:

> After booting the aforementioned patch and re-running mdz's script, it
> froze after a few minutes with this gpu state.
>
> ** Attachment added: "i915_debugfs_bwh4.tgz"
> http://launchpadlibrarian.net/25840981/i915_debugfs_bwh4.tgz
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Dan Quayle <http://www.brainyquote.com/quotes/authors/d/dan_quayle.html> -
"I love California, I practically grew up in Phoenix."

[Flavio Capobianco (norkov)]

I installed the ppa patch, turned reflection effect on and it froze after two minutes.

[Bryce Harrington (bryce)]

On Wed, Apr 22, 2009 at 01:29:24AM -0000, Jithin Emmanuel wrote:
> I am now facing a new problem, my gnome-terminal or konsole is not taking
> Escape key. So in vim if I go to insert mode I cannot come back. I am not
> having this problem with pure console login.
> Could this be related to x server?

Doubtful, but even if it was you should not double up problem reports
onto an unrelated bug... which is already hugely too long as it is. ;-)

Have you tested the patch Jesse provided (and that I put into the PPA)
to see if it makes the issue go away?

Bryce

[Bryce Harrington (bryce)]

Here is a freeze running a normal user session with 2 gnome-terminal's and firefox, using Jesse's patch with the above debs.

This happened within about 15 minutes of freshly booting during regular usage (not mdz's script), which is sort of a record since usually it takes several hours. I noticed some slowdown in performance when task switching prior to the freeze, however I was not doing alt-tab at the instant it froze as typical; I was just closing down firefox tabs.

[Flavio Capobianco (norkov)]

This is my first debugging.

I installed the 2.6.30-020630rc2_i386 kernel and followed all the instructions for Intel X freeze testing.

I got X frozen in two minutes without using any scripts, just by turning on Compiz reflection effect, opening several windows and some heavy alt tabbing.

The first time I sshed into the frozen computer, it hanged right after I mounted /sys/kernel/debug. I tried sshing into it again but I got no response.

The second time, I froze X the same way but this time nothing hanged, so I could created all log files, which I attach here.

[Jithin Emmanuel (jithin1987)]

I had freeze with the new intel driver from Bryce's repository.
What surprised me was I got a freeze with UXA ON on 2.6.29 kernel. I could
not collect the debug info coz I was not on 30 kernel at that time.
I could not find any files on /sys/kernel/debug/dri/ and I did mount debugfs

/dev/sda5 on / type ext4 (rw,relatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)

On Wed, Apr 22, 2009 at 8:08 AM, Bryce Harrington <<email address hidden>
> wrote:

> Here is a freeze running a normal user session with 2 gnome-terminal's
> and firefox, using Jesse's patch with the above debs.
>
> This happened within about 15 minutes of freshly booting during regular
> usage (not mdz's script), which is sort of a record since usually it
> takes several hours. I noticed some slowdown in performance when task
> switching prior to the freeze, however I was not doing alt-tab at the
> instant it froze as typical; I was just closing down firefox tabs.
>
>
> ** Attachment added: "i915_debugfs_bwh5.tgz"
> http://launchpadlibrarian.net/25842399/i915_debugfs_bwh5.tgz
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Dan Quayle <http://www.brainyquote.com/quotes/authors/d/dan_quayle.html> -
"I love California, I practically grew up in Phoenix."

[Jithin Emmanuel (jithin1987)]

I had freeze with the new intel driver from Bryce's repository.
What surprised me was I got a freeze with UXA ON on 2.6.29 kernel. I could not collect the debug info coz I was not on 30 kernel at that time.
I could not find any files on /sys/kernel/debug/dri/ and I did mount debugfs

/dev/sda5 on / type ext4 (rw,relatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
securityfs on /sys/kernel/security type securityfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)

[Jithin Emmanuel (jithin1987)]

oops sorry for the reposting. First I sent from gmail And I didnt see it getting posted here so I decided to post directly again.

[Jithin Emmanuel (jithin1987)]

Is the packages xserver-xorg-driver-all and xserver-xorg-video-all required ? It installs drivers for all nvidia, ati ... Only intel specific ones are required right?

[AZC (albazc)]

I forgot to mention I experienced the freeze with Virtual 3200 1200 in my xorg.conf.

This is my whole xorg.conf:

Section "Device"
 Identifier "Configured Video Device"
  Option "XAANoOffscreenPixmaps" "true"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"

#to prevent compiz freeze flavs

 SubSection "Display"
  Virtual 3200 1200
 EndSubSection

EndSection

[Flavio Capobianco (norkov)]

Comment 214 belongs to me, sorry.

I now tried Jesse Barnes' suggestion to add Option "ExaNoComposite" "true" to xorg.conf (I also added INTEL_BATCH="1" to /etc/environment).

When I rebooted performance seemed to be as good as it was with Intrepid. No more sluggishness. I opened many windows, alt tabbed between them and minimized in quick succession. All of it with reflection effect on but nothing happened. I started playing with other effects, turning them on and off and it froze after ten minutes while I was turning off some effect. I could not ssh from another computer. I was on a wifi link, that must have been the cause since it didn't hang. I was able to reboot doing alt sysrq R S E I U B.

[Jithin Emmanuel (jithin1987)]

I thought UXA was the perfect solution for me and it was for past week. But now I am having frequent freezes even with UXA ON, though repro.sh won't trigger it. It seems that moving back to intrepid is a viable option.

[Bryce Harrington (bryce)]

Another gpu dump including gdm.log after reproducing freeze with jesse's patch and disabling dri buffer reuse:

http://www2.bryceharrington.org:8080/files/i915_debugfs_bwh6.tgz (74mb)

[Marius Gedminas (mgedmin)]

Another data point from another user:

  * Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
  * no freezes ever encountered in Intrepid nor Jaunty (upgraded on Apr 05)
  * I used EXA for a couple of days then switched to UXA
  * the only other change in my xorg.conf is "Virtual 2960 1880" and this one has been there since Intrepid
  * I used dual-head (1280x800 + 1024x1280) with both EXA and UXA, so large textures got some exercise (this was before the last mesa upload disabled the large texture patch)
  * I haven't tried running repro.sh (yet)

I used to get occasional crashes (but not freezes) after suspend & resume when I switched to UXA, but they seem to have stopped lately.

[wirechief (wirechief)]

Amazingly i have now been able to run repro.sh without any noticable
problems, I decided to start compiz
from a terminal was was told that my graphics id 00:02.0 VGA
compatible controller: Intel Corporation Mobile GM965/GL960 Integrated
Graphics Controller (rev 0c) was blacklisted and I thought well i knew
this.
but then as I tried to reply to a ubuntu-mail list I noticed my
keyboard was not working. I could pulldown menus, my caps lock would
toggle on /off but i could not type, i was able to open a terminal
with ctrl alt f2
so i ssh into this sick machine and did the
https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test
instructions. i will have to visit launchpad to paste the files.

On Wed, Apr 22, 2009 at 3:48 PM, Marius Gedminas <email address hidden> wrote:
> Another data point from another user:
>
>  * Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
>  * no freezes ever encountered in Intrepid nor Jaunty (upgraded on Apr 05)
>  * I used EXA for a couple of days then switched to UXA
>  * the only other change in my xorg.conf is "Virtual 2960 1880" and this one has been there since Intrepid
>  * I used dual-head (1280x800 + 1024x1280) with both EXA and UXA, so large textures got some exercise (this was before the last mesa upload disabled the large texture patch)
>  * I haven't tried running repro.sh (yet)
>
> I used to get occasional crashes (but not freezes) after suspend &
> resume when I switched to UXA, but they seem to have stopped lately.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[wirechief (wirechief)]

attachments from the recent keyboard freeze. I am not sure this is the same freeze i had days ago. but sypmtoms
were similar enough

[wirechief (wirechief)]

there are several more files, if they are needed please advise.

[Flavio Capobianco (norkov)]

@wirechief : You can pack them all in a zip file and upload them.

[wirechief (wirechief)]

unfortunately my HD crashed, i had to reinstall .. they are gone.

On Thu, Apr 23, 2009 at 2:46 AM, Flavio Cabobianco <email address hidden> wrote:
> @wirechief : You can pack them all in a zip file and upload them.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Bryce Harrington (bryce)]

This time it happened even when Desktop Effects was shut off (first time freeze with only metacity for me).

Also, I've been noticing that with these freezes I often have some zombie processes. This time I took a looksee:

root@salisbury:~# ps -el | grep 'Z'
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD
0 Z 1000 4664 4644 0 80 0 - 0 exit ? 00:00:00 gnome-terminal <defunct>
0 Z 1000 4665 4644 0 80 0 - 0 exit ? 00:00:00 gnome-terminal <defunct>
0 Z 1000 4666 4644 0 80 0 - 0 exit ? 00:00:00 gnome-terminal <defunct>

[jbond00747 (jeff-cowart)]

I have a Dell D830 laptop with the Intel GM965 card that's been blacklisted. I haven't had any problems with X freezing. My screen runs at 1920x1200 resolution. I don't have a lot of compiz effects enabled, but I have a few enabled.

Here is the relevant output of `lspci -nn`
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

My Xorg.conf file is pretty generic. Here are the relevant sections:

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 SubSection "Display"
  Virtual 2944 1200
 EndSubSection
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

[Bryce Harrington (bryce)]

Killing the parent of the gnome-terminal processes destroyed the zombies but did not bring back the screen.

@jbond, we do not need people to confirm that they are not having the X freeze. I understand you're probably frustrated to have lost compiz, but trust me you're lucky you have only lost desktop effects and are not suffering the freeze problem. ;-) You can comment on 363821 if you wish.

[Björn Ruberg (bjoern-ruberg-wegener)]

Hello!

I welcome all ubuntu users in the world of freezing desktop on intel chipsets. As I switched to Fedora10 on my main machine some month ago, I had the problem a little earlier.
I tried to collect all data in my bug report in the freedesktop bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=20893#c0

Short story: This bug has been probably introduced after xorg-video-intel-2.5.1 . As this driver and earlier drivers are reported working, it is quite sure a bug in the driver.
The ONLY always working reported workaround is to put "Option" "NoAccel" "true" in your xorg.conf. Turning off composite alone does reduce the number of freezes, but they are still there.

So, take this upstream to the intel developers. I already predicted them that many ubuntu users will have this problem now.

Please post your intel_gpu_dumps there!

[Jithin Emmanuel (jithin1987)]

I was planning to switch to fedora 11 when rc is released. Now dropped that plan. So now the only option for a good desktop for intel users is to switch back to intrepid. Considering this is in upstream for some time, I think by the time this is fixed it will be time for ubuntu 9.10 .

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno ven, 24/04/2009 alle 08.54 +0000, Björn Ruberg ha scritto:
>
> So, take this upstream to the intel developers. I already predicted
> them
> that many ubuntu users will have this problem now.

I know it would take time and patience, but is it possible to do a
forward port of the new drivers? Or the entire Xorg? The new one gives
troubles, what are the advantages for an end user?

[Joseph Wakeling (webdrake)]

Björn Ruberg wrote:
> The ONLY always working reported workaround is to put "Option" "NoAccel" "true" in your xorg.conf. Turning off composite alone does reduce the number of freezes, but they are still there.

For the benefit of those of us who are not too familiar with xorg.conf
editing, can you specify _exactly_ where in the file to enter this
option? :-)

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno ven, 24/04/2009 alle 12.11 +0000, Vincenzo Ciancia ha scritto:
> I know it would take time and patience, but is it possible to do a
> forward port of the new drivers?

Indeed I meant a forward port of the old drivers.

[Bernhard (b.a.koenig)]

Btw, this must have been said before in this thread but I will say it again if people missed it:

you can enable compositing in metacity (type "gconf-editor" and then go to apps/metacity/general and enable "compositing"). Then you can have your docks and everything and you are only missing a small eye-candy part of compiz. I'm doing that right now and it works OK for me.

[wirechief (wirechief)]

Well i just ran a quick and dirty test on my kanotix install, ive been
using it for over 1.5 yrss
never had a freeze and never installed compiz (i dont like wiggley
windows) but as a test I
installed it and when i tried to run it was given the same error
message that compiz detected
my intel card and was not going to run, evidently compiz blacklists
the intel card now.
but i chose to run overide it with SKIP_CHECKS=yes compiz my screen
blinked and changed
and then every window i opened froze, the terminal froze, i was unable
to move anything, i
had what i thought was the same freeze that i reported with jaunty but
i only think the effects
were similar. i am using this:
ii xserver-xorg-video-intel 2:2.3.2-2+lenny6
        X.Org X server -- Intel i8xx, i9xx display d

I imagine there are lots of people burning lots of midnight oil on this bug....

2009/4/24 Björn Ruberg <email address hidden>:
> Hello!
>
> I welcome all ubuntu users in the world of freezing desktop on intel chipsets. As I switched to Fedora10 on my main machine some month ago, I had the problem a little earlier.
> I tried to collect all data in my bug report in the freedesktop bugzilla:
> https://bugs.freedesktop.org/show_bug.cgi?id=20893#c0
>
> Short story: This bug has been probably introduced after xorg-video-intel-2.5.1 . As this driver and earlier drivers are reported working, it is quite sure a bug in the driver.
> The ONLY always working reported workaround is to put "Option" "NoAccel" "true" in  your xorg.conf. Turning off composite alone does reduce the number of freezes, but they are still there.
>
> So, take this upstream to the intel developers. I already predicted them
> that many ubuntu users will have this problem now.
>
> Please post your intel_gpu_dumps there!
>
> ** Bug watch added: freedesktop.org Bugzilla #20893
>   https://bugs.freedesktop.org/show_bug.cgi?id=20893
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno ven, 24/04/2009 alle 13.04 +0000, Bernhard ha scritto:
>
> you can enable compositing in metacity (type "gconf-editor" and then
> go
> to apps/metacity/general and enable "compositing"). Then you can have
> your docks and everything and you are only missing a small eye-candy
> part of compiz. I'm doing that right now and it works OK for me.

Does metacity have the ability to zoom the screen? And the
"scale" (compiz) or "expose" (mac) way to view all the windows at once?
These are extremely useful especially on small notebooks.

V.

--
It is also important to note that hedgehogs do not actually hurt each
other when they get close to one another. Actually, when living in
groups, hedgehogs often sleep close to each other.
http://en.wikipedia.org/wiki/Hedgehog%27s_dilemma

[Isa (ibaboo)]

I have the same Intel graphics card and I am also experiencing X freezing with Compiz. It worked fine in Intrepid. Just one big note I am using GNOME.

[Zachary Waldowski (zwaldowski)]

Adding my dri_debug files to the mix obtained from the ubuntu-x-swat instructions, hope it can help.

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

Why don't we all write to http://supportmail.intel.com/scripts-emf/prodspec.aspx to ask them for help with this bug (and possibly to complain about their closed drivers)?

[Andres Mujica (andres.mujica)]

Hi BJörn!!

Thanks for your info. I'm linking the FD bug here. Luckily for us the Intel devs are aware about this issue and are looking at the issue. However we're really missing the upstream official bug report and i believe your`s it`s the ideal one!.

About the Fedora one, i`ve been looking at Red Hat's bugzilla a lot searching for the same symptons without luck. In fact the one you`ve mentioned is under my radar, but i don't really think that is the same bug (the EQ error logs are not shown here), probably related but not the same, so i`m not really convinced to link this bug against it.

However, in order to benefit both communities it would be really great to find the right bug at Red Hat's bugzilla so we can share more info, do you know another one reported there?

[Matt Zimmerman (mdz)]

On Fri, Apr 24, 2009 at 05:42:50PM -0000, Fabio wrote:
> Why don't we all write to http://supportmail.intel.com/scripts-
> emf/prodspec.aspx to ask them for help with this bug (and possibly to
> complain about their closed drivers)?

Intel's developers are aware of the issue and working with Ubuntu developers
to identify the root cause.

--
 - mdz

[jippie (jph4dotcom)]

Same issue here.
- KDE4 locks up;
- Mouse pointer moves;
- Keyboard locked;
- System available via SSH;
- System hangs quickly with Desktop Effects, usually within minutes;
- System hangs without Desktop Effects, usually within a day;
- Running: Kubuntu amd64 9.04 with latest patches (24 apr. 2009);
- Checked 7.3 mesa => does not work for me;
- Platform:
  - Motherboard: DG35EC;
  - CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz
  - GPU: 82G35 Express Integrated Graphics Controller (i9x5 compatible)

Haven't had the time/energy yet to author an xorg.conf. Hints to ease this job are welcomed.

[jippie (jph4dotcom)]

Forgot to mention that, when Effects are enabled, the system starts with really smooth effects and after a little while those effects start to jump and hickup. At that moment it is just a matter of seconds before KDE freezes.

BTW: Although this is my first (k)ubuntu install, I come from several Gentoo stage 1 installs. Bear with me while learning the ubuntu way ;o)

[Björn Ruberg (bjoern-ruberg-wegener)]

WORKAROUND:

For getting rid of the freezes make do the following.
If you don't have a /etc/X11/xorg.conf , create one by runnig X -configure (and putting the resulting file to that place).
In the xorg.conf the is a section looking like this:

Section "Device"
        Driver "intel"
EndSection

Make sure to have this option in that section:
        Option "NoAccel" "yes"

As a result, you will have this:

Section "Device"
        Driver "intel"
        Option "NoAccel" "yes"
EndSection

After that, you won't have nice effects and not much fun playing videos. But your system does not freeze anymore.

Andres, the Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=464866 is indeed the right one. But there are different bugs put into one. So it's not very clean. I have the EQ overflowing message.

Good to hear that ubuntu and intel is working together. Sad that it is done this late. The bug is known longer. Probably it would be good to work more with Fedora. I don't flame about distros, I love each and every one. But Fedora is technically always ahead of ubuntu. Bugs not fixed there will hit the next ubuntu release. As it happened now.

[jippie (jph4dotcom)]

@Andres, Björn: This is a thread I spotted yesterday at FD, but can't find a related bug id
http://forums.fedoraforum.org/showthread.php?t=205950

[jippie (jph4dotcom)]

Great hint! Implemented it, hopefully my system will now be stable
enough to get my VirtualBoxes running some server processes :o) I'll
keep the thread updated in case of problems.

JP

Björn Ruberg wrote:
> WORKAROUND:
>
> For getting rid of the freezes make do the following.
> If you don't have a /etc/X11/xorg.conf , create one by runnig X -configure (and putting the resulting file to that place).
> In the xorg.conf the is a section looking like this:
>
> Section "Device"
> Driver "intel"
> EndSection
>
> Make sure to have this option in that section:
> Option "NoAccel" "yes"
>
> As a result, you will have this:
>
> Section "Device"
> Driver "intel"
> Option "NoAccel" "yes"
> EndSection
>
> After that, you won't have nice effects and not much fun playing videos.
> But your system does not freeze anymore.
>
>
> Andres, the Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=464866 is indeed the right one. But there are different bugs put into one. So it's not very clean. I have the EQ overflowing message.
>
> Good to hear that ubuntu and intel is working together. Sad that it is
> done this late. The bug is known longer. Probably it would be good to
> work more with Fedora. I don't flame about distros, I love each and
> every one. But Fedora is technically always ahead of ubuntu. Bugs not
> fixed there will hit the next ubuntu release. As it happened now.
>
> ** Bug watch added: Red Hat Bugzilla #464866
> https://bugzilla.redhat.com/show_bug.cgi?id=464866
>
>

[Bryce Harrington (bryce)]

Btw, unless your intel_gpu_dump output roughly matches what I've posted, you may be having an unrelated bug.

For me, the issue goes away when booting mesa 7.3 or turning off desktop effects or using AccelMethod UXA. The freeze I see is a memory issue that crops up after opening a lot of windows, either via use of mdz's script (which triggers the freeze in 5-10 min) or after a few hour's of "normal" use.

If your freeze does not match this sequence of steps, you probably are having an unrelated freeze bug.

[Soeren Sonnenburg (bugreports-nn7)]

On Sat, 2009-04-25 at 03:41 +0000, Bryce Harrington wrote:
> Btw, unless your intel_gpu_dump output roughly matches what I've posted,
> you may be having an unrelated bug.
>
> For me, the issue goes away when booting mesa 7.3 or turning off desktop
> effects or using AccelMethod UXA. The freeze I see is a memory issue
> that crops up after opening a lot of windows, either via use of mdz's
> script (which triggers the freeze in 5-10 min) or after a few hour's of
> "normal" use.
>
> If your freeze does not match this sequence of steps, you probably are
> having an unrelated freeze bug.

I guess you have a different bug then, because this one happens no
matter what AccelMethod you use nor does it help to disable compiz. It
just takes a little longer for it to occur.

[Luca Marra (luca-marra)]

I'm using intel video drivers 2.7.0 and UXA: no freezes in 24h of utilization with compiz enabled. repro.sh ran without freeze.

Hope this helps.

[telewizor (jakubch)]

How about some quick HOWTO on how to blend them into Jaunty?

[Sonny (aadityabhatia)]

Had the same problem in Intrepid. Display didn't freeze that often, but considerably slowed down - right after I updated my box on April 4th. System was unusable until I switched to EXA.

[Bassu Khan (bashukhan)]

Woaah...!
I was getting freaked by the naughty auto_eth0 NetworkManager bug in Interpid from last five months (though I already had that fixed by setting up my own startup scripts) and when Jaunty was released yesterday, I tried with a fresh install and guess what, the first thing I encountered, was this freeze.... !
I found that Inetl **Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)** was blacklisted in /usr/bin/compiz - I whitelisted it and started getting problems.

It was working perfect in Interpid so i thought I would be the same after the upgrade.. but upgrade brings more side effects than the resolutions.. lol... as Andres mentioned in comment# 167

I am now trying this https://wiki.ubuntu.com/X/UxaTesting and this https://wiki.ubuntu.com/X/Bugs/IntelDriver

I'll post back if something helps!

[wirechief (wirechief)]

i have not had crashes since at least the compiz blacklisted my intel graphics or when this got installed.
2009-04-23 02:22:15 status installed xserver-xorg-video-intel-dbg 2:2.6.3-0ubuntu10~bug359392~1

[Bassu Khan (bashukhan)]

Thanks Wirechief.
I already reverted back to Interpid's Intel 2.4's package on Jaunty, it didn't freeze but it was so slow~
I just installed xserver-xorg-video-intel-dbg 2:2.6.3-0ubuntu10~bug359392~1, I got the performance back and I'll report again if this works fine for me as well.

Thanks again.

>i have not had crashes since at least the compiz blacklisted my intel graphics or when this got installed.
>2009-04-23 02:22:15 status installed xserver-xorg-video-intel-dbg 2:2.6.3-0ubuntu10~bug359392~1

[floyd0815 (floriankre)]

Is it possible, that evtouch is causing this problem?

My X only (or mostly, don't know it exactly because of the number of freezes) crashes, when I used my touchscreen.(after +/- 1 or 2 minutes)

I had the same freezes after I installed evtouch into kuki (Aspire One distro) where no other one experienced freezes and evtouch is included in UNR 9.04 anyway. (don't know about ubuntu and kubuntu)

And when I only use my touchpad, there are no freezes.

Acer Aspire One
UNR Jaunty
2.6.29-1 Sickboy's Kernel

PS: In my case, I can restart X after a freeze with <alt>+<print>+<k>. RSEIUB is a bit too aggresive.

Floyd

[Sushant (sushant-indiankanoon)]

I tried "UAX" the fix and compiz is working great for last 5 hours without any freezes. I followed the instructions from here
http://www.ubuntugeek.com/intel-graphics-performance-guide-for-ubuntu-904-jaunty-users.html

and I am running Dell Inspiron 13 with Intel GM965 graphics card.

[Martin Beukman (digibeuk)]

I have the some problems as described, numerous freezes. But have an amd64 processor and nvidia graphics card

[Shwan (shwan-ciyako)]

I have 8086 2a00 and have the problem.

[Martin Pitt (pitti)]

Since the pattern here is still pretty inconclusive, we started collecting more structured feedback on a wiki page:

  https://wiki.ubuntu.com/DesktopTeam/i965Users

Please add your data here. Please also test from a live system, to make sure that the tests are all done on a fixed software platform.

I also uploaded a test -intel package to my PPA which drops a patch which was meant to mitigate a problem on the i945, but never quite worked very well. It's a complete shot in the dark, but worth ruling out. Thank you!

[Zachary Waldowski (zwaldowski)]

Okay, Martin, I installed your package and filled out my respective entry on the Wiki. I've still been victim to the freeze on every possible Jaunty combination: default, your package, Bryce's "purple" packages, Ubuntu X Swat's bug test packages, Xorg crack pushers PPA, Ubuntu X Swat Update PPA. All the same freeze. It's even happened multiple times on the LiveCD. Only time I didn't get the freeze was in Intrepid. Does anybody know where I could get absolute bleeding-edge Xorg everything?

[Bassu Khan (bashukhan)]

Oops, the intel's fixed pkg is still not working.. caused freeze for three more times!
Bump.. another major bug in the new release ~!

--
>i have not had crashes since at least the compiz blacklisted my intel graphics or when this got installed.
>2009-04-23 02:22:15 status installed xserver-xorg-video-intel-dbg 2:2.6.3-0ubuntu10~bug359392~1

[Bryce Harrington (bryce)]

After running Martin's PPA for 1 hr with mdz's repro.sh script there has been no freeze.

However, I've been testing a whole bunch of different ideas over the weekend, so my test box isn't pristine. So I'll back out those changes and re-verify.

Meanwhile, would be helpful to get additional confirmations that this ppa solves it. Here's a more direct link for people:

i386:
https://edge.launchpad.net/~pitti/+archive/ppa/+files/xserver-xorg-video-intel_2.6.3-0ubuntu9pitti4_i386.deb

amd64:
https://edge.launchpad.net/~pitti/+archive/ppa/+files/xserver-xorg-video-intel_2.6.3-0ubuntu9pitti4_amd64.deb

[Bryce Harrington (bryce)]

@zwaldowski, do you still see the freeze if you set AccelMethod to "UXA"?

[Eugenio Cano-Manuel (eugeniocano11)]

I've installed the i386 package you uploaded but i had a crash again while playing Stepmania, i know its funny but in my case, X ALWAYS crashes while playing that game since Jaunty, maybe because of heavy drawing?. Im using default settings except for compiz blacklisting which i skiped checks.

By the way, im using this. 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

[Zachary Waldowski (zwaldowski)]

Yes. I have Martin's Intel package you link to above with UXA enabled and I continue to freeze. Hell, I don't even have to run repro.sh, it happens anyway.

[Bryce Harrington (bryce)]

On Mon, Apr 27, 2009 at 06:52:38PM -0000, Eugenio Cano-Manuel wrote:
> I've installed the i386 package you uploaded but i had a crash again
> while playing Stepmania, i know its funny but in my case, X ALWAYS
> crashes while playing that game since Jaunty, maybe because of heavy
> drawing?. Im using default settings except for compiz blacklisting which
> i skiped checks.

This is about a freeze bug, not a crash bug. For crashes, please
collect a backtrace and report it as a separate issue.

[Matthew Woerly (nattgew)]

I first noticed this bug really badly because of Gnome-Do. It got to where it would freeze every time I brought it up. I removed Gnome-Do, because I thought that was the problem, but it still freezes sometimes, especially with dual monitors.
Does anyone else find that Gnome-Do makes X freeze a lot?

[Don Owen (donald.e.owen)]

Quote:
"
I first noticed this bug really badly because of Gnome-Do. It got to where it would freeze every time I brought it up. I removed Gnome-Do, because I thought that was the problem, but it still freezes sometimes, especially with dual monitors.
Does anyone else find that Gnome-Do makes X freeze a lot?
"

I also have Gnome-do installed and was experiencing frequent freezes (~ 15 minutes sometimes ).

But, this is just a circumstantial note, I don't have hard evidence, just mentioning in response to Nattgew.

[tdashroy (tdashroy)]

I too am getting these freezes. I have GM965 [8086:2a02] (rev 0c) like many mentioned above. I just recently disabled compiz to see if I still get the freezes. I would be willing to help out in any way possible. Could someone fill me in one which tests I should run?

[jippie (jph4dotcom)]

My (jippie) entry is up there too. My system is stable for over two days
now, since I changed the xorg.conf with
  Option "NoAccel" "yes"
Not sure what is meant though with the columns
  - has in situ freezes
  - happens on live system

Hope this helps.

JP

Martin Pitt wrote:
> Since the pattern here is still pretty inconclusive, we started
> collecting more structured feedback on a wiki page:
>
> https://wiki.ubuntu.com/DesktopTeam/i965Users
>
> Please add your data here. Please also test from a live system, to make
> sure that the tests are all done on a fixed software platform.
>
> I also uploaded a test -intel package to my PPA which drops a patch
> which was meant to mitigate a problem on the i945, but never quite
> worked very well. It's a complete shot in the dark, but worth ruling
> out. Thank you!
>
>

[Kevin Hausmann (salema)]

I can confirm running the patched driver and repro.sh for roughly an hour without any problems.

I have
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
UXA enabled
Compiz enabled (including patches from http://ppa.launchpad.net/cavedon for my dual head > 2048px setup)
[I do use Gnome-Do a lot without a hassle, I don't think it is an issue here]
[I do have VideoRam set in xorg.conf]

Please note that freezes were very infrequent for me anyway.

[Bryce Harrington (bryce)]

After backing out the changes I was testing over the weekend, to get closer to a stock system, the freeze returned.

[Alwin Garside (yogarine)]

Kevin, please test in EXA mode. On the [8086:2a02] (rev 0c) setting
AccelMethod to "UXA" acually fixes things, at the cost of a 25%
performance penalty.
Like Martin said, you should ideally test from a LiveCD or a fresh
untouched install. If you can't be bothered to reinstall Ubuntu or run
a LiveCD, at least test in EXA mode with Greedy Migration disabled.

On Mon, Apr 27, 2009 at 9:57 PM, kevin <email address hidden> wrote:
> I can confirm running the patched driver and repro.sh for roughly an
> hour without any problems.
>
> I have
> 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
> UXA enabled
> Compiz enabled (including patches from http://ppa.launchpad.net/cavedon for my dual head > 2048px setup)
> [I do use Gnome-Do a lot without a hassle, I don't think it is an issue here]
> [I do have VideoRam set in xorg.conf]
>
> Please note that freezes were very infrequent for me anyway.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Alwin Garside
Email: <email address hidden>
Blog: http://www.yogarine.net
Twitter: http://twitter.com/yogarine
MSN: <email address hidden>
Skype: yogarine
Phone: [phone]
Mobile: [phone]

[nwadams (nwnadams)]

i have an untouched install on my dell xps m1330 that I will begin testing with.

i have this card :00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

I will read the rest of this thread later tonight but I am first going to see if i get any freezes under normal usage before i try the scripts to reproduce the freezes on purpose.

[Matthew Woerly (nattgew)]

"On the [8086:2a02] (rev 0c) setting AccelMethod to "UXA" acually fixes things, at the cost of a 25%
performance penalty."
Is this with some patch installed? I've used UXA all along while having X freeze.

[wirechief (wirechief)]

I just got my first freeze in a long time, i had taken a nap, went to the lappy and was reading Bryce's entry at
2:04pm est, my shock to find it frozen, i had earlier changed my session to kde, i performed the X Freeze Tests
and will upload the results. (once i recover)

[wirechief (wirechief)]

if anyone wants to see more of the files i can upload as needed. (we seem to have lots of evidence already)
i am going to get the latest xserver from bryces ppa to see if that prevents the freeze.

[Bryce Harrington (bryce)]

On Mon, Apr 27, 2009 at 08:22:29PM -0000, Nattgew wrote:
> "On the [8086:2a02] (rev 0c) setting AccelMethod to "UXA" acually fixes things, at the cost of a 25%
> performance penalty."
> Is this with some patch installed? I've used UXA all along while having X freeze.

No; there are known freeze bugs with UXA which are probably unrelated to
this.

Bryce

[wirechief (wirechief)]

ii xserver-xorg-video-intel 2:2.6.3-0ubuntu9pitti4 X.Org X server -- Intel i8xx, i9xx display d
ii xserver-xorg-video-intel-dbg 2:2.6.3-0ubuntu10~bug359392~1 X.Org X server -- Intel i8xx, i9xx display d
ii xserver-xorg-video-mach64 6.8.0-3
pkg -l |grep mesa
ii libgl1-mesa-dev 7.4-0ubuntu3 A free implementation of the OpenGL API -- G
ii libgl1-mesa-dri 7.4-0ubuntu3 A free implementation of the OpenGL API -- D
ii libgl1-mesa-dri-dbg 7.4-0ubuntu3 Debugging symbols for the Mesa DRI modules
ii libgl1-mesa-glx 7.4-0ubuntu3 A free implementation of the OpenGL API -- G
ii libgl1-mesa-glx-dbg 7.4-0ubuntu3 Debugging symbols for the Mesa GLX runtime
ic libgl1-mesa-swx11 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- r
ii libglu1-mesa 7.4-0ubuntu3 The OpenGL utility library (GLU)
ii libglu1-mesa-dev 7.4-0ubuntu3 The OpenGL utility library -- development fi
ii libosmesa6 7.4-0ubuntu3 Mesa Off-screen rendering extension
ii mesa-common-dev 7.4-0ubuntu3 Developer documentation for Mesa
ii mesa-utils 7.4-0ubuntu3
It is interesting that i have not had to report a freeze in a very long time, i have not been in a kde environment about the same amount of time.

[Soeren Sonnenburg (bugreports-nn7)]

On Mon, 2009-04-27 at 21:24 +0000, Bryce Harrington wrote:
> On Mon, Apr 27, 2009 at 08:22:29PM -0000, Nattgew wrote:
> > "On the [8086:2a02] (rev 0c) setting AccelMethod to "UXA" acually fixes things, at the cost of a 25%
> > performance penalty."
> > Is this with some patch installed? I've used UXA all along while having X freeze.
>
> No; there are known freeze bugs with UXA which are probably unrelated to
> this.

I am having this bug with UXA enabled too. Mouse cursor is still there
and can be moved but display freezes.

[Alwin Garside (yogarine)]

> "On the [8086:2a02] (rev 0c) setting AccelMethod to "UXA" acually fixes things, at the cost of a 25%
> performance penalty."
> Is this with some patch installed? I've used UXA all along while having X freeze.

No, I'm using a fresh Ubuntu install with my [8086:2a02] (rev 0c)
(Sony VAIO VGN-NR230AE). Using default settings X will freeze, but
when I set AccelMethod to "UXA" everything runs fine.
If it still freezes with UXA then it's probably an unrelated issue.
I also did a bunch of benchmarks with OpenArena:

2.6 with EXA Normal:
840 frames 19.8 seconds 42.5 fps 10.0/23.6/89.0/7.0 ms
840 frames 19.9 seconds 42.3 fps 9.0/23.7/86.0/6.7 ms
840 frames 19.5 seconds 43.1 fps 9.0/23.2/66.0/6.2 ms
2.6 with EXA Greedy:
840 frames 19.9 seconds 42.2 fps 11.0/23.7/81.0/7.2 ms
840 frames 19.1 seconds 44.0 fps 10.0/22.7/44.0/5.4 ms
840 frames 19.6 seconds 42.8 fps 11.0/23.4/58.0/6.2 ms

2.6 with UXA Normal:
840 frames 25.5 seconds 32.9 fps 16.0/30.4/88.0/7.5 ms
840 frames 24.9 seconds 33.7 fps 14.0/29.7/78.0/6.5 ms
840 frames 25.0 seconds 33.6 fps 17.0/29.7/64.0/6.4 ms
2.6 with UXA Greedy:
840 frames 25.3 seconds 33.2 fps 16.0/30.1/101.0/7.6 ms
840 frames 24.9 seconds 33.7 fps 17.0/29.6/54.0/5.8 ms
840 frames 25.0 seconds 33.6 fps 18.0/29.8/98.0/6.6 ms

2.4 with EXA Normal:
840 frames 37.5 seconds 22.4 fps 21.0/44.7/104.0/12.5 ms
840 frames 38.7 seconds 21.7 fps 21.0/46.1/113.0/14.6 ms
840 frames 39.7 seconds 21.2 fps 22.0/47.3/108.0/14.6 ms
2.4 with EXA Greedy:
840 frames 40.7 seconds 20.6 fps 22.0/48.4/107.0/15.2 ms

2.4 with UXA Normal
840 frames 38.8 seconds 21.7 fps 21.0/46.1/208.0/16.2 ms

2.4 with UXA Greedy
840 frames 82.7 seconds 10.2 fps 53.0/98.4/223.0/23.0 ms

On Mon, Apr 27, 2009 at 10:22 PM, Nattgew <email address hidden> wrote:
> "On the [8086:2a02] (rev 0c) setting AccelMethod to "UXA" acually fixes things, at the cost of a 25%
> performance penalty."
> Is this with some patch installed?  I've used UXA all along while having X freeze.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Alwin Garside
Email: <email address hidden>
Blog: http://www.yogarine.net
Twitter: http://twitter.com/yogarine
MSN: <email address hidden>
Skype: yogarine
Phone: [phone]
Mobile: [phone]

[Zachary Waldowski (zwaldowski)]

Are you guys serious? I get the issue on both EXA and UXA; always have. I also get it on all combinations of drivers, so...

[Markus Kopp (mkopp)]

I have the Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c), 1400*900, 4GB Ram (Lenovo X300). Switched to jaunty amd64 during beta phase. All regular updates are installed, no special Patches. The freezes happen sporadic since the update from intrepid. Many days i have no freezes at all, but i also had 2 freezes during one hour. This happend with and without compiz. I'm not sure, but i believe when freezes happen they happen fast after boot. Maybe a problem with initialization? I have often seen corruption before the freeze. Corruption was corrupt characters but also whole paragraphs missing in Firefox.

[wirechief (wirechief)]

this might give more information on your freezes
https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test

On Mon, Apr 27, 2009 at 6:31 PM, Markus Kopp <email address hidden> wrote:
> I have the Intel Corporation Mobile GM965/GL960 Integrated Graphics
> Controller [8086:2a02] (rev 0c), 1400*900, 4GB Ram (Lenovo X300).
> Switched to jaunty amd64 during beta phase. All regular updates are
> installed, no special Patches. The freezes happen sporadic since the
> update from intrepid. Many days i have no freezes at all, but i also had
> 2 freezes during one hour. This happend with and without compiz. I'm not
> sure, but i believe when freezes happen they happen fast after boot.
> Maybe a problem with initialization? I have often seen corruption before
> the freeze. Corruption was corrupt characters but also whole paragraphs
> missing in Firefox.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Bryce Harrington (bryce)]

I've found that by increasing my Virtual setting to a higher number, the freezes go away. So far, at 1600x1600 and lower it freezes within about 10 min, but 1650x1650 and higher it seems to run repro.sh without freeze for >30 min. Still testing...

[Bryce Harrington (bryce)]

Virtual Freeze Test-Duration
2048 none 40 min
1800 no 30 min
1700 no 30 min
1650 no 30 min
1625 no 30 min
1612 no 30 min
1604 yes <15 min
1600 yes <10 min
1400 yes 1 min
1281 yes <1 min
1280 yes <1 min
none yes <1 min, many tests all froze

Diff between the 1612 and 1604 cases: http://pastebin.ubuntu.com/159748/

[Bryce Harrington (bryce)]

To finish off the table:

1608 no 30 min
1607 no 30 min
1606 yes <1 min

So it seems at least on my hardware, Virtual 1606 1606 and below freezes. Dunno what would be magical about that number, but it's pretty night and day. I'll run a few more tests to verify this dichotomy.

[Javier Jardón (jjardon)]

Perhaps of interest:

http://lists.freedesktop.org/archives/xorg/2009-April/045350.html

[Leon (leonbo)]

I've got the ppa package installed for a couple of hours now. So far I've had no freeze. While without the patched driver it would freeze within an hour of surfin' the internet.

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
 Subsystem: Dell Device [1028:0273]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+

The box had a complete clean install this weekend. I removed compize before trying the patched driver.

[Martin Pitt (pitti)]

jippie [2009-04-27 19:52 -0000]:
> My (jippie) entry is up there too. My system is stable for over two days
> now, since I changed the xorg.conf with
> Option "NoAccel" "yes"

That's one of the workarounds, but of course a pretty drastic one.

> Not sure what is meant though with the columns
> - has in situ freezes

"In some rather unpredictable situations, the screen freezes"

> - happens on live system

That's the live system which you get when you boot the computer with
the Ubuntu desktop CD and choose "try out Ubuntu".

[Martin Pitt (pitti)]

Bryce Harrington [2009-04-28 0:05 -0000]:
> I've found that by increasing my Virtual setting to a higher number, the
> freezes go away

That's what Sebastien reported as well. I think everyone else should
try this as well and check if it makes the freezes go away.

Bryce, do you think we could get out a test package which sets the
default VirtualSize to that number? (I wouldn't like to invent an
userspace hack to mess with xorg.conf for that).

[Kevin Hausmann (salema)]

This is just to confirm that my successful testing yesterday was with Virtual set to 2560 1024 in xorg.conf.

[wirechief (wirechief)]

it would be nice to see a snippet of the xorg.conf that is using this virtual setting, i am not sure i have mine correctly
set now. i am trying this uxa thing.
 cat /var/log/Xorg.0.log |grep "UXA"
(WW) intel(0): DRI2 requires UXA

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Device"
 Identifier "Onboard Intel Video"
 #Option "AccelMethod" "exa"
 #Option "monitor-VGA" "ExternalVGA"
 #Option "monitor-LVDS" "OnboardLVDS"
  Option "EXAOptimizeMigration" "true"
  Option "MigrationHeuristic" "greedy"
  Option "AccelMethod" "uxa"
         Option "Tiling" "false" # may break 3D rendering if enabled

EndSection

Section "ServerFlags"
 Option "DontZap" "False"
EndSection

[wirechief (wirechief)]

I just did a du and now this is my mesa
dpkg -l |grep mesa
ii libgl1-mesa-dev 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt A free implementation of the OpenGL API -- G
ii libgl1-mesa-dri 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt A free implementation of the OpenGL API -- D
ii libgl1-mesa-dri-dbg 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt Debugging symbols for the Mesa DRI modules
ii libgl1-mesa-glx 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt A free implementation of the OpenGL API -- G
ii libgl1-mesa-glx-dbg 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt Debugging symbols for the Mesa GLX runtime
ic libgl1-mesa-swx11 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- r
ii libglu1-mesa 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt The OpenGL utility library (GLU)
ii libglu1-mesa-dev 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt The OpenGL utility library -- development fi
ii libosmesa6 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt Mesa Off-screen rendering extension
ii mesa-common-dev 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt Developer documentation for Mesa
ii mesa-utils 7.4.1~git20090424+mesa-7-4-br

[Julian Edwards (julian-edwards)]

On Tuesday 28 April 2009 03:31:19 Bryce Harrington wrote:
> To finish off the table:
>
> 1608 no 30 min
> 1607 no 30 min
> 1606 yes <1 min
>
> So it seems at least on my hardware, Virtual 1606 1606 and below
> freezes. Dunno what would be magical about that number, but it's pretty
> night and day. I'll run a few more tests to verify this dichotomy.

Would your monitor's display size enter the equation at all?

I run 1920x1200 on an external monitor and it will freeze pretty quickly
unless I use Greedy.

[Matt Zimmerman (mdz)]

On Tue, Apr 28, 2009 at 08:28:13AM -0000, Julian Edwards wrote:
> Would your monitor's display size enter the equation at all?
>
> I run 1920x1200 on an external monitor and it will freeze pretty quickly
> unless I use Greedy.

We're trying to isolate that and other variables by collecting data at
https://wiki.ubuntu.com/DesktopTeam/i965Users. Please add your details
there.

--
 - mdz

[Kevin Hausmann (salema)]

@wirechief
my complete xorg.conf is just below (and works well)

Section "Monitor"
        Identifier "Configured Monitor"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
        SubSection "Display"
                Virtual 2560 1024
        EndSubSection
EndSection

Section "Device"
        Identifier "Configured Video Device"
        Option "AccelMethod" "UXA"
        # Option "MigrationHeuristic" "greedy"
        # VideoRam 786432
EndSection

[cbrmichi (cbrmichi)]

Same problem here.

What can I do?

[Zachary Waldowski (zwaldowski)]

I don't know what it is that did it, but something that I did to my Xorg.conf fixed it all.

[Alwin Garside (yogarine)]

Okay ladies and gentleman, I believe that, at least for [8086:2a02]
(rev 0c), increasing Virtual works as a workaround.

I've been using a fresh ubuntu installation, with no changes to
xorg.conf except Virtual 2560 1024, for the whole day now, with Compiz
enabled and no freezes.

Please try increasing the Virtual size to something high like 2560 x
1024, on a fresh installation where possible, and post your findings
here.

On Tue, Apr 28, 2009 at 3:46 PM, zwaldowski <email address hidden> wrote:
> I don't know what it is that did it, but something that I did to my
> Xorg.conf fixed it all.
>
> ** Attachment added: "FIXED XORG.CONF"
>   http://launchpadlibrarian.net/26070968/xorg.conf
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Alwin Garside
Email: <email address hidden>
Blog: http://www.yogarine.net
Twitter: http://twitter.com/yogarine
MSN: <email address hidden>
Skype: yogarine
Phone: [phone]
Mobile: [phone]

[Bryce Harrington (bryce)]

Rather, I'd recommend testing 2048 2048 for virtual

[Jithin Emmanuel (jithin1987)]

OK. Now that we have a working work around, is there any clean way to revert
back to jaunty packages, with out having to re install. Also is this virtual
size fix without UXA ?I ran into a lot of issues with UXA unrelated to
freezes.

On Tue, Apr 28, 2009 at 9:38 PM, Bryce Harrington <<email address hidden>
> wrote:

> Rather, I'd recommend testing 2048 2048 for virtual
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Mark Twain <http://www.brainyquote.com/quotes/authors/m/mark_twain.html> -
"Get your facts first, then you can distort them as you please."

[Martin Pitt (pitti)]

Jithin Emmanuel [2009-04-28 16:22 -0000]:
> OK. Now that we have a working work around,

It's at least promising.

> is there any clean way to revert back to jaunty packages, with out
> having to re install.

sudo apt-get install --reinstall xserver-xorg-video-intel/jaunty

> Also is this virtual size fix without UXA?

Yes.

Please NB that there'll be another -intel test package soon which
changes the default VirtualSize. We can't possibly change xorg.conf in
an update.

[Jithin Emmanuel (jithin1987)]

Does that mean that there will be one more test package before proper update
or there will be only this test package?

On Tue, Apr 28, 2009 at 10:13 PM, Martin Pitt <email address hidden>wrote:

> Jithin Emmanuel [2009-04-28 16:22 -0000]:
> > OK. Now that we have a working work around,
>
> It's at least promising.
>
> > is there any clean way to revert back to jaunty packages, with out
> > having to re install.
>
> sudo apt-get install --reinstall xserver-xorg-video-intel/jaunty
>
> > Also is this virtual size fix without UXA?
>
> Yes.
>
> Please NB that there'll be another -intel test package soon which
> changes the default VirtualSize. We can't possibly change xorg.conf in
> an update.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Winston Churchill<http://www.brainyquote.com/quotes/authors/w/winston_churchill.html>
- "The best argument against democracy is a five-minute conversation
with
the average voter."

[jippie (jph4dotcom)]

<Intermezzo>
I guess I found a Thunderbird bug or so, second time I notice I'm
sending out an empty message, luckily it does appear in my sent items
;o) Sorry for the confusion.
</Intermezzo>

OK, I've changed my "NoAccel" work around that was stable but very slow
for over three days now
with the Virtual 2048 2048 + Desktop effects enabled.
no other changes to the X -configure defaults.

I'll keep you informed.

jippie wrote:
>

[Zachary Waldowski (zwaldowski)]

Bah, I just got the freeze with Virtual 1600 1200. I'll try with 2048 2048 just to make sure, as everything seems to be working fine now otherwise.

[Marius Gedminas (mgedmin)]

Looks like I got my first freeze. The mouse cursor continues to move,
but nothing else is redrawn.

I can't recall if this is relevant for this bug, but the numbers are
strange:

$ cat /proc/dri/0/gem_objects
12222 objects
-1156268032 object bytes
4 pinned
4395008 pin bytes
134754304 gtt bytes
260575232 gtt total

Marius Gedminas
--
lg_PC.gigacharset (lg = little green men language, PC = proxima centauri)
 -- Markus Kuhn provides an example of a locale

[Zachary Waldowski (zwaldowski)]

Crap. Unfortunately, I can confirm that I still get the freeze on stock Jaunty packages with any Virtual number. My xorg.conf (currently, not the one I posted this morning) is just the stock one with the Virtual entries and UXA enabled. Maybe it's Compiz?

[Botond Szász (boteeka)]

Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xserver-xorg-video-intel 2:2.6.3-0ubuntu9
PackageArchitecture: i386
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev pulse pulse-access pulse-rt sambashare scanner tape vboxusers video

[wirechief (wirechief)]

mine test like this.
cat /proc/dri/0/gem_objects
4671 objects
78798848 object bytes
4 pinned
4395008 pin bytes
76488704 gtt bytes
260575232 gtt total

On Tue, Apr 28, 2009 at 3:53 PM, Marius Gedminas <email address hidden> wrote:
> Looks like I got my first freeze.  The mouse cursor continues to move,
> but nothing else is redrawn.
>
> I can't recall if this is relevant for this bug, but the numbers are
> strange:
>
> $ cat /proc/dri/0/gem_objects
> 12222 objects
> -1156268032 object bytes
> 4 pinned
> 4395008 pin bytes
> 134754304 gtt bytes
> 260575232 gtt total
>
> Marius Gedminas
> --
> lg_PC.gigacharset (lg = little green men language, PC = proxima centauri)
>        -- Markus Kuhn provides an example of a locale
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Martin Pitt (pitti)]

zwaldowski [2009-04-28 19:25 -0000]:
> Bah, I just got the freeze with Virtual 1600 1200.

Bryce confirmed that as well. He stopped getting freezes for >= 1606,
and recommended using 2048x2048.

[Martin Pitt (pitti)]

zwaldowski [2009-04-28 19:55 -0000]:
> Crap. Unfortunately, I can confirm that I still get the freeze on stock
> Jaunty packages with any Virtual number. My xorg.conf (currently, not
> the one I posted this morning) is just the stock one with the Virtual
> entries and UXA enabled.

Please note that this bug is specifically *not* about UXA, jaunty
defaults to EXA since UXA is still too unstable.

[Zachary Waldowski (zwaldowski)]

*Sigh*. It doesn't matter! I've been told a handful of times that the UXA doesn't matter, and for some people UXA *fixes* the problem. I've received the problem in both modes, and am only including it for clarification. EXA drops my framerates drastically and makes it - as it has all the way since Edgy - so I can't move a damn 3D/video windows around.

I also just got out of Jaunty again... 2048 2048 also gives the freeze after a little while.

[wirechief (wirechief)]

oops, it got away from me.

On Tue, Apr 28, 2009 at 6:30 PM, jippie <email address hidden> wrote:
>
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[jippie (jph4dotcom)]

thunderbird is wierd in replying here ...

Anyways I was saying:

My Virtual 2048x2o48 session including Desktop effects froze after
3h30m. The effects definately slow down just before the freeze.
Currently running the UXA option with virtual turned off.

Hope this helps,

JP

[Matthew D. Lukens (lukens)]

I have had no issues previously, besides a complete xorg crash/restart that I couldn't identify (and hasn't happened since), until today.

I was trying out the alarm-clock application (not installed by default, in the repos), and had an X lockup. I was able to CTRL-ALT-F1 and restart GDM and log back in. I tried the alarm-clock app again without launching anything else, and it locked up again.

This is a Thinkpad T61.

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

[wirechief (wirechief)]

http://ubuntuforums.org/showthread.php?p=7112258 this is interesting
with memory leaks
am wondering how this relates to cat /proc/dri/0/gem_objects they
seem to increase continually
i wonder how huge they are at the time of these freezes.

On Tue, Apr 28, 2009 at 7:55 PM, Matthew D. Lukens <email address hidden> wrote:
> I have had no issues previously, besides a complete xorg crash/restart
> that I couldn't identify (and hasn't happened since), until today.
>
> I was trying out the alarm-clock application (not installed by default,
> in the repos), and had an X lockup.  I was able to CTRL-ALT-F1 and
> restart GDM and log back in.  I tried the alarm-clock app again without
> launching anything else, and it locked up again.
>
> This is a Thinkpad T61.
>
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile
> GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Bryce Harrington (bryce)]

On Tue, Apr 28, 2009 at 11:55:29PM -0000, Matthew D. Lukens wrote:
> I was trying out the alarm-clock application (not installed by default,
> in the repos), and had an X lockup. I was able to CTRL-ALT-F1 and
> restart GDM and log back in. I tried the alarm-clock app again without
> launching anything else, and it locked up again.

The alarm-clock freeze is a completely different, unrelated bug. The
workaround for it is to ssh in an kill the alarm-clock process, and X
will come back. There is another bug report on that, you can probably
find it in launchpad filed against -intel.

This 359392 freeze cannot be recovered from except by power cycling.

[jippie (jph4dotcom)]

How about this little script? To continuously log the contents of the file?

{ who -b; while sleep 60; do for word in `cat /proc/dri/0/gem_objects`;
do printf "%s\t" $word; done; echo; done; } >> dri.log

JP

[cbrmichi (cbrmichi)]

i did this now for a few minutes and added to the log what i did while it was logging.

don't know whether it helps...

[cbrmichi (cbrmichi)]

update

[jippie (jph4dotcom)]

My desktop froze with UXA in little over an hour. I am reverting to
NoAccel, currently the only option I know to get my system stable. I
have no clue how to upload a file to lanchpadlibrarian :s and google
refused to tell me ... can I just attach it to my email? Let's find out ;o)

BTW: I can usually do a ACPI shutdown, which strictly spoken is a power
cycle, but at least the system is properly shut down.

Hope this helps,

JP

[telewizor (jakubch)]

@zwaldowski

>> * FIXED XORG.CONF (1.2 KiB, text/plain)
>>I don't know what it is that did it, but something that I did to my Xorg.conf fixed it all.

Just to add confusion - that Xorg.conf made my X freeze in about 5 minutes.
To add some extra confusion - I've disable UXA in it and I'm alive for more than 3 hours.

I seem to be the only person on planet Earth having real real issues with UXA, and noticeably less issues with EXA.

My gear:
Thinkpad R61i
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

[Alwin Garside (yogarine)]

> I seem to be the only person on planet Earth having real real issues
> with UXA, and noticeably less issues with EXA.

Well, UXA *is* experimental, so dont be suprised if UXA freezes on you...
EXA + Virtual 2048 2048 _does_ seem to be the magic solution. Just
take a look at my Freeze-free xorg.conf:

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 SubSection "Display"
  Virtual 2560 1024
 EndSubSection
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

You see? No exotic settings, just a high Virtual...

On Wed, Apr 29, 2009 at 1:15 PM, telewizor <email address hidden> wrote:
> @zwaldowski
>
>>>    * FIXED XORG.CONF (1.2 KiB, text/plain)
>>>I don't know what it is that did it, but something that I did to my Xorg.conf fixed it all.
>
> Just to add confusion - that Xorg.conf made my X freeze in about 5 minutes.
> To add some extra confusion - I've disable UXA in it and I'm alive for more than 3 hours.
>
> I seem to be the only person on planet Earth having real real issues
> with UXA, and noticeably less issues with EXA.
>
> My gear:
> Thinkpad R61i
> 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Alwin Garside
Email: <email address hidden>
Blog: http://www.yogarine.net
Twitter: http://twitter.com/yogarine
MSN: <email address hidden>
Skype: yogarine
Phone: [phone]
Mobile: [phone]

[Benjamin von Engelhardt (bve)]

> I seem to be the only person on planet Earth having real real issues
 > with UXA, and noticeably less issues with EXA.

I had many freezes with UXA too, not so with EXA, at least with Virtual 2048 2048 (shall I try without Virtual? I only remember freezes with UXA).

My system:
Thinkpad X300

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)
        Subsystem: Lenovo Device [17aa:20b5]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 2297
        Region 0: Memory at fa000000 (64-bit, non-prefetchable) [size=1M]
        Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 1800 [size=8]
        Capabilities: <access denied>
        Kernel modules: intelfb

00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c)
        Subsystem: Lenovo Device [17aa:20b5]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at fa100000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: <access denied>

and excerpt from xorg.conf:

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
        # Input "Synaptics Touchpad"
        SubSection "Display"
        depth 24
        virtual 2048 2048
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier "Default Layout"
        Screen "Default Screen"
        # InputDevice "Synaptics Touchpad"
        # InputDevice "Trackpoint"
EndSection

Section "Device"
        Identifier "Configured Video Device"
        Driver "intel"
        Option "AccelMethod" "EXA"
        O...

[Soeren Sonnenburg (bugreports-nn7)]

On Wed, 2009-04-29 at 07:43 +0000, jippie wrote:
> My desktop froze with UXA in little over an hour. I am reverting to
> NoAccel, currently the only option I know to get my system stable. I
> have no clue how to upload a file to lanchpadlibrarian :s and google
> refused to tell me ... can I just attach it to my email? Let's find out ;o)

Mine [8086:27ae] hangs with UXA or EXA and with Virtualsize 2048 2048
too so I am reverting to using NoAccel too :(

Note that it took like 6 hours before the hang appeared and I was using
internal and external displays in between

# cat /proc/dri/0/gem_objects
3518 objects
735432704 object bytes
4 pinned
19431424 pin bytes
202805248 gtt bytes
260313088 gtt total

No change on 2.6.30-rc3 nor 2.6.29.1 nor downgrading
xserver-xorg-video-intel to 2.6.3 .

That's the backtrace I see when gdb attaching to the machine:

(gdb) bt
#0 0xb7f35424 in __kernel_vsyscall ()
#1 0xb7c9dc49 in ioctl () from /lib/i686/cmov/libc.so.6
#2 0xb7f1dc5d in drmIoctl () from /usr/lib/libdrm.so.2
#3 0xb7f1e062 in drmCommandNone () from /usr/lib/libdrm.so.2
#4 0xb78bca3f in I830BlockHandler (i=0, blockData=0x0, pTimeout=0xbfd53628,
    pReadmask=0x81f08c0) at ../../src/i830_driver.c:2659
#5 0x0817809b in AnimCurScreenBlockHandler (screenNum=0, blockData=0x0,
    pTimeout=0xbfd53628, pReadmask=0x81f08c0) at ../../render/animcur.c:222
#6 0x08142828 in compBlockHandler (i=0, blockData=0x0, pTimeout=0xbfd53628,
    pReadmask=0x81f08c0) at ../../composite/compinit.c:158
#7 0x080902d8 in BlockHandler (pTimeout=0xbfd53628, pReadmask=0x81f08c0)
    at ../../dix/dixutils.c:384
#8 0x0812fcf4 in WaitForSomething (pClientsReady=0x9fc13f0)
    at ../../os/WaitFor.c:215
#9 0x0808c53e in Dispatch () at ../../dix/dispatch.c:367
#10 0x080719dd in main (argc=11, argv=0xbfd53774, envp=Cannot access memory at address 0x6460
)
    at ../../dix/main.c:397

Soeren

[wirechief (wirechief)]

cat /proc/dri/0/gem_objects
7676 objects
288759808 object bytes
4 pinned
4395008 pin bytes
160575488 gtt bytes
260575232 gtt total
no freeze's yet on my end.
Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
        Virtual 2048 2048
EndSection

Section "Device"

 Identifier "Onboard Intel Video"
 #Option "AccelMethod" "exa"
 #Option "monitor-VGA" "ExternalVGA"
 #Option "monitor-LVDS" "OnboardLVDS"
  Option "EXAOptimizeMigration" "true"
  Option "MigrationHeuristic" "greedy"
  Option "AccelMethod" "uxa"
         Option "Tiling" "false" # may break 3D rendering if enabled
         VideoRam 261120
EndSection

Section "ServerFlags"
 Option "DontZap" "False"
EndSection

On Wed, Apr 29, 2009 at 11:16 AM, Soeren Sonnenburg <email address hidden> wrote:
> On Wed, 2009-04-29 at 07:43 +0000, jippie wrote:
>> My desktop froze with UXA in little over an hour. I am reverting to
>> NoAccel, currently the only option I know to get my system stable. I
>> have no clue how to upload a file to lanchpadlibrarian :s and google
>> refused to tell me ... can I just attach it to my email? Let's find out ;o)
>
> Mine [8086:27ae] hangs with UXA or EXA and with Virtualsize 2048 2048
> too so I am reverting to using NoAccel too :(
>
> Note that it took like 6 hours before the hang appeared and I was using
> internal and external displays in between
>
> # cat /proc/dri/0/gem_objects
> 3518 objects
> 735432704 object bytes
> 4 pinned
> 19431424 pin bytes
> 202805248 gtt bytes
> 260313088 gtt total
>
> No change on 2.6.30-rc3 nor 2.6.29.1 nor downgrading
> xserver-xorg-video-intel to 2.6.3 .
>
>
> That's the backtrace I see when gdb attaching to the machine:
>
> (gdb) bt
> #0  0xb7f35424 in __kernel_vsyscall ()
> #1  0xb7c9dc49 in ioctl () from /lib/i686/cmov/libc.so.6
> #2  0xb7f1dc5d in drmIoctl () from /usr/lib/libdrm.so.2
> #3  0xb7f1e062 in drmCommandNone () from /usr/lib/libdrm.so.2
> #4  0xb78bca3f in I830BlockHandler (i=0, blockData=0x0, pTimeout=0xbfd53628,
>    pReadmask=0x81f08c0) at ../../src/i830_driver.c:2659
> #5  0x0817809b in AnimCurScreenBlockHandler (screenNum=0, blockData=0x0,
>    pTimeout=0xbfd53628, pReadmask=0x81f08c0) at ../../render/animcur.c:222
> #6  0x08142828 in compBlockHandler (i=0, blockData=0x0, pTimeout=0xbfd53628,
>    pReadmask=0x81f08c0) at ../../composite/compinit.c:158
> #7  0x080902d8 in BlockHandler (pTimeout=0xbfd53628, pReadmask=0x81f08c0)
>    at ../../dix/dixutils.c:384
> #8  0x0812fcf4 in WaitForSomething (pClientsReady=0x9fc13f0)
>    at ../../os/WaitFor.c:215
> #9  0x0808c53e in Dispatch () at ../../dix/dispatch.c:367
> #10 0x080719dd in main (argc=11, argv=0xbfd53774, envp=Cannot access memory at address 0x6460
> )
>    at ../../dix/main.c:397
>
> Soeren
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Bassu Khan (bashukhan)]

IN A NUTSHELL,
Like every Ubuntu release has something strange,
Jaunty has its own benefits with the graphics ;)

[Bryce Harrington (bryce)]

On Wed, Apr 29, 2009 at 01:04:24PM -0000, bve wrote:
> I had many freezes with UXA too, not so with EXA, at least with Virtual
> 2048 2048 (shall I try without Virtual? I only remember freezes with
> UXA).

No, you've got a different bug from this one.

[Bryce Harrington (bryce)]

On Wed, Apr 29, 2009 at 03:16:38PM -0000, Soeren Sonnenburg wrote:
> Mine [8086:27ae] hangs with UXA or EXA and with Virtualsize 2048 2048
> too so I am reverting to using NoAccel too :(
>
> Note that it took like 6 hours before the hang appeared and I was using
> internal and external displays in between

See if setting it to 4096 4096 makes the time to freeze take longer.

Bryce

[Bryce Harrington (bryce)]

On Wed, Apr 29, 2009 at 12:34:57PM -0000, Alwin Garside wrote:
> Well, UXA *is* experimental, so dont be suprised if UXA freezes on you...
> EXA + Virtual 2048 2048 _does_ seem to be the magic solution.

Yeah, we've always suspected there are more than just one bug causing
freezes, they just all look identical.

However, given everyone's feedback it seems we definitely do have one
bug that is triggered with mdz's repro.sh script when running with stock
xorg.conf (i.e. EXA) on i965, and goes away when upping Virtual, for
some reason. This is the issue we'll focus on here.

So if you have a freeze that doesn't fit these conditions, you should
look elsewhere.

[Launchpad Janitor (janitor)]

This bug was fixed in the package xserver-xorg-video-intel - 2:2.6.3-0ubuntu10

---------------
xserver-xorg-video-intel (2:2.6.3-0ubuntu10) karmic; urgency=low

  * Add 121_i965_default_to_virtual_2048_2048.patch, to force the default
    Virtual resolution on i965 to 2048x2048 if not otherwise specified in
    xorg.conf. This works around freeze issues seen on this hardware.
    (LP: #359392)

 -- Bryce Harrington <email address hidden> Wed, 29 Apr 2009 15:26:27 -0700

[tdashroy (tdashroy)]

Sorry I'm a little new to this, will a patch for Jaunty be released or will it only be released for Karmic?

[Bryce Harrington (bryce)]

For Jaunty, debs for testing are available here:

 http://people.ubuntu.com/~bryce/Testing/xserver-xorg-video-intel_2.6.3-0ubuntu10~bug359392~3_amd64.deb

 http://people.ubuntu.com/~bryce/Testing/xserver-xorg-video-intel_2.6.3-0ubuntu10~bug359392~3_i386.deb

It will also be available from the ppa for this bug once the build queue catches up:

 https://edge.launchpad.net/~bryceharrington/+archive/purple/

Once we have several positive confirmations on this, I'll put in the SRU for Jaunty.

[Martin Pitt (pitti)]

I'll revert the blacklisting in compiz.

[Jithin Emmanuel (jithin1987)]

What is done is kubuntu which uses kwins desktop effects. Or are they left in the wild or we do not have any kubuntu users with 965 other than me.

[Martin Pitt (pitti)]

Jithin Emmanuel [2009-04-30 8:58 -0000]:
> What is done is kubuntu which uses kwins desktop effects. Or are they
> left in the wild or we do not have any kubuntu users with 965 other than
> me.

The compiz blacklisting applied to kwin as well, since kwin used the
compiz code for detecting compositing support.

The -intel driver workaround is not GNOME specific, thus will apply
equally to Kubuntu as well.

[Julian Edwards (julian-edwards)]

On Thursday 30 April 2009 12:17:50 Martin Pitt wrote:
> The compiz blacklisting applied to kwin as well, since kwin used the
> compiz code for detecting compositing support.

It didn't stop kwin using compositing for me though.

[Jithin Emmanuel (jithin1987)]

yea me too. kwin always had desktop effects enabled.

On Thu, Apr 30, 2009 at 5:08 PM, Julian Edwards <
<email address hidden>> wrote:

> On Thursday 30 April 2009 12:17:50 Martin Pitt wrote:
> > The compiz blacklisting applied to kwin as well, since kwin used the
> > compiz code for detecting compositing support.
>
> It didn't stop kwin using compositing for me though.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Albert Einstein<http://www.brainyquote.com/quotes/authors/a/albert_einstein.html>
- "Only two things are infinite, the universe and human stupidity, and
I'm
not sure about the f...

[Dave Conniff (chronniff)]

all hail the bug fix!!!!
........reverted to jaunty kernel and applied the fix package, actually seems to also improve the performance as well. Will be testing all day
Tried to add the repo, but can't get the key to work. Will you update this at all, or is it just a temp place to get the package for now and should I not worry about having the repo?

[Rolando (rolandojr)]

I've been working all day with the fix and compiz enabled and everything is going pretty well. Performance seems even better. I got a card from the GMA X3100 series.

[Dave Conniff (chronniff)]

I agree, I have GM965 (x3100) been using it all day, have had no problems, performance boost on par with testing the cutting edge drivers in the testing kernel, and most importantly, not one freeze!!! This is quite a relief, thank you to all the people who have been working on this. (I Haven't tried UXA since installing the patch, although I wouldn't think it would help it out too much)

[wirechief (wirechief)]

my penquin now flys at mach speed with uxa, unfortunately he hits the
trees and i have to
slow him down to get to the finish line but no freezes since my last
report. i have the
xserver-xorg-video-intel_2%3a2.7.99.1+git20090427.e55d9431-0ubuntu0sarvatt_amd64.deb
installed too.

On Thu, Apr 30, 2009 at 8:56 PM, Dave Conniff <email address hidden> wrote:
> I agree, I have GM965 (x3100)  been using it all day, have had no
> problems, performance boost on par with testing the cutting edge drivers
> in the testing kernel, and most importantly, not one freeze!!! This is
> quite a relief, thank you to all the people who have been working on
> this.  (I Haven't tried UXA since installing the patch, although I
> wouldn't think it would help it out too much)
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Jithin Emmanuel (jithin1987)]

wirechief do u have any problems with uxa? In case kde it affected kde
logout

On Fri, May 1, 2009 at 6:42 AM, wirechief <email address hidden>wrote:

> my penquin now flys at mach speed with uxa, unfortunately he hits the
> trees and i have to
> slow him down to get to the finish line but no freezes since my last
> report. i have the
>
> xserver-xorg-video-intel_2%3a2.7.99.1+git20090427.e55d9431-0ubuntu0sarvatt_amd64.deb
> installed too.
>
> On Thu, Apr 30, 2009 at 8:56 PM, Dave Conniff <email address hidden>
> wrote:
> > I agree, I have GM965 (x3100) been using it all day, have had no
> > problems, performance boost on par with testing the cutting edge drivers
> > in the testing kernel, and most importantly, not one freeze!!! This is
> > quite a relief, thank you to all the people who have been working on
> > this. (I Haven't tried UXA since installing the patch, although I
> > wouldn't think it would help it out too much)
> >
> > --
> > [i965] X freezes starting on April 3rd
> > https://bugs.launchpad.net/bugs/359392
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Reach out and share life, care for others,
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Albert Einstein<http://www.brainyquote.com/quotes/authors/a/albert_einstein.html>
- "Only two things are infinite, the universe and human stupidity, and
I'm
not sure about the f...

[wirechief (wirechief)]

@Jithin Emmanuel
I will be testing in the kde probably tommrow, I want a complete
overnight on gnome after i do
my du tonight would be a good time.

On Thu, Apr 30, 2009 at 9:27 PM, Jithin Emmanuel <email address hidden> wrote:
> wirechief do u have any problems with uxa? In case kde it affected kde
> logout
>
> On Fri, May 1, 2009 at 6:42 AM, wirechief
> <email address hidden>wrote:
>
>> my penquin now flys at mach speed with uxa, unfortunately he hits the
>> trees and i have to
>> slow him down to get to the finish line but no freezes since my last
>> report. i have the
>>
>> xserver-xorg-video-intel_2%3a2.7.99.1+git20090427.e55d9431-0ubuntu0sarvatt_amd64.deb
>> installed too.
>>
>> On Thu, Apr 30, 2009 at 8:56 PM, Dave Conniff <email address hidden>
>> wrote:
>> > I agree, I have GM965 (x3100)  been using it all day, have had no
>> > problems, performance boost on par with testing the cutting edge drivers
>> > in the testing kernel, and most importantly, not one freeze!!! This is
>> > quite a relief, thank you to all the people who have been working on
>> > this.  (I Haven't tried UXA since installing the patch, although I
>> > wouldn't think it would help it out too much)
>> >
>> > --
>> > [i965] X freezes starting on April 3rd
>> > https://bugs.launchpad.net/bugs/359392
>> > You received this bug notification because you are a direct subscriber
>> > of the bug.
>> >
>>
>>
>> --
>> Reach out and share life, care for others,
>>
>> --
>> [i965] X freezes starting on April 3rd
>> https://bugs.launchpad.net/bugs/359392
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
> --
> Regards
> Jithin Emmanuel
> http://spotm.in
> Albert Einstein<http://www.brainyquote.com/quotes/authors/a/albert_einstein.html>
> - "Only two things are infinite, the universe and human stupidity, and
> I'm
> not sure about the f...
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Rolando (rolandojr)]

I just had my first freeze since my last report, but I i couldn't say if it is linked to this bug, because before the fix my card was blacklisted. I was opening a .pdf in Firefox when it happened.

(I am very new at this, but I can say that this never happened to me in intrepid)

[Bernhard (b.a.koenig)]

Thanks all for the bugfix, but I'm a bit confused. I still have compiz blacklisted. When will the blacklisting go away? Do I have to wait for a new compiz update?

[Steve Langasek (vorlon)]

Accepted xserver-xorg-video-intel into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Steve Langasek (vorlon)]

Accepted compiz into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Zachary Waldowski (zwaldowski)]

Um... the bugfix isn't working for me AT ALL. I just got the freeze twice after reinstalling Jaunty. My system is stock... the only difference from stock 9.04 is Bryce's package.

[Zack Evans (zevans23)]

The new release implements a workaround by default, which prevents the average needing to mess with xorg.conf to make the problem go away.

The flipside of this is that if you have already changed xorg.conf because your config is above average, Bryce's patch won't make a bit of difference.

I'm guessing your VirtualSize is already set to something over 2960 wide because you have a dual-screen setup of that size. Wonder if it's worth changing your VirtualSize line to 2960x2048 so both dimensions are over the magic 1600andsomething.

[Jithin Emmanuel (jithin1987)]

Surprising part is that no one knows what is happening and only thing agreed
up on is this setting works for some reason, which is also unknown I guess.
It a hack than a fix. There has to a permanent solution to this bug.

On Fri, May 1, 2009 at 10:18 PM, Steve Beattie <email address hidden> wrote:

> ** Tags added: hw-specific
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
P. J. O'Rourke<http://www.brainyquote.com/quotes/authors/p/p_j_orourke.html>
- "Cleanliness becomes more important when godliness is unlikely."

[Zachary Waldowski (zwaldowski)]

Nuh-uh, I am definitely on a stock system. I installed it from a CD image I downloaded last night, and my Xorg.conf is the standard Ubuntu one.

[Matt Zimmerman (mdz)]

I don't see 2:2.6.3-0ubuntu9 in -proposed. The source is published, but no i386 or amd64 binaries.

[Bryce Harrington (bryce)]

> Tried to add the repo, but can't get the key to work. Will you update this at all, or is it just a temp place to get the package for now and should I not worry about having the repo?

It's just a temp place for the fix, don't worry about having the repo in your sources.list.

[Geir Ove Myhr (gomyhr)]

It seems that the patch 121_i965_default_virtual_to_2048_2048.patch which was supposed to add the VirtualX and VirtualY by default from i965 users also sets this for users on GM45. See bug 370777. Is the IS_965G function really testing for 965G and above?

[Evan R. Murphy (evanrmurphy)]

The desktop effects are working like a charm over here now. Thanks for all your hard work on this.

[Soeren Sonnenburg (bugreports-nn7)]

On Wed, 2009-04-29 at 21:36 +0000, Bryce Harrington wrote:
> On Wed, Apr 29, 2009 at 03:16:38PM -0000, Soeren Sonnenburg wrote:
> > Mine [8086:27ae] hangs with UXA or EXA and with Virtualsize 2048 2048
> > too so I am reverting to using NoAccel too :(
> >
> > Note that it took like 6 hours before the hang appeared and I was using
> > internal and external displays in between
>
> See if setting it to 4096 4096 makes the time to freeze take longer.

It has taken longer (I wasn't using the machine as intensive though).

So it helps a bit but is not the cure...

Soeren

[Zachary Waldowski (zwaldowski)]

I still get it, no matter what combination I have. Stock system, stock system with proposed packages, Jaunty with 2.6.30-rc4 and Xorg-crack-pushers packages, EVERYTHING. The bug is most definitely not fixed by the new packages - I got it right after installing.

[Geir Ove Myhr (gomyhr)]

The patch that works around this bug (for most of you) seems to _override_ the virtual setting instead of only setting the default. The setting in xorg.conf is ignored, and that gives problems for anyone with a dual-head setup with side-by-side desktops (providing the total width is >2048). See bug 370777 for details.

[Valentin Neacsu (valentin.neacsu)]

I am having an issue with Jaunty on i915. Using Metacity, the CPU gets slowly but surely eaten up with no obvious process eating up the CPU cycles. "top" shows no process taking more than 5-10% CPU time, while the "System Monitor" panel applet shows the CPU at 100% usage, with "IOWait" eating up most of it. When this happens I gradually lose control of the system, where sometimes I can reboot it, while other times it just freezes trying to do it. Most programs stop responding when this happens. Switching to text mode doesn't help as bash can't get enough CPU time to initialize. I can reboot with the Magic SysRq key. I can trigger this easily while on battery, usually within 5-10 minutes of normal usage (browsing, reading PDFs etc).

My question is if this bug is related to the above described symptoms, or is it a completely different bug that's affecting me?

Thanks.

[Oded Arbel (oded-geek)]

It sounds like this problem:
https://bugzilla.redhat.com/show_bug.cgi?id=487494 which is about the X
server leaking memory, which causes swap thrashing which causes the
kernel to spend a lot of time in IO-wait until the system becomes
non-responsive. I haven't seen this with Ubuntu, but Jaunty uses the
same version of X server and about the same version of the Intel drivers
so its possible its the same problem.

Regardless, this is not relevant to this ticket.

On Sun, 2009-05-03 at 15:11 +0000, Valentin Neacsu wrote:
> I am having an issue with Jaunty on i915. Using Metacity, the CPU gets
> slowly but surely eaten up with no obvious process eating up the CPU
> cycles. "top" shows no process taking more than 5-10% CPU time, while
> the "System Monitor" panel applet shows the CPU at 100% usage, with
> "IOWait" eating up most of it. When this happens I gradually lose
> control of the system, where sometimes I can reboot it, while other
> times it just freezes trying to do it. Most programs stop responding
> when this happens. Switching to text mode doesn't help as bash can't get
> enough CPU time to initialize. I can reboot with the Magic SysRq key. I
> can trigger this easily while on battery, usually within 5-10 minutes of
> normal usage (browsing, reading PDFs etc).
>
> My question is if this bug is related to the above described symptoms,
> or is it a completely different bug that's affecting me?
>
> Thanks.
>

[Martin Pitt (pitti)]

zwaldowski [2009-05-01 15:28 -0000]:
> Um... the bugfix isn't working for me AT ALL. I just got the freeze
> twice after reinstalling Jaunty. My system is stock... the only
> difference from stock 9.04 is Bryce's package.

You actually have to install this proposed update to get the new fix.

[Martin Pitt (pitti)]

Matt Zimmerman [2009-05-01 19:14 -0000]:
> I don't see 2:2.6.3-0ubuntu9 in -proposed. The source is published, but
> no i386 or amd64 binaries.

Might have taken a little to build, but it's there now:

xserver-xorg-video-intel | 2:2.6.3-0ubuntu9.1 | jaunty-proposed | source, amd64, i386

[Joachim Nilsson (troglobit)]

Geir Ove Myhr wrote, on 05/03/2009 04:51 AM:
> The setting in xorg.conf is ignored, and that gives problems for anyone
> with a dual-head setup with side-by-side desktops (providing the total
> width is >2048).

Agreed, I too have that problem.

I have a ThinkPad T61 with Intel GM965 [8086:2a02] (rev 0c) with a native resolution of 1280x800 and as soon as I try to use my external 1920x1200 screen it now fails.

Otherwise I have no freezes (disabled UXA in my xorg.conf) or anything. Things are back to normal here with Compiz running fine. Thanks for the hard work!

Regards
 /Joachim

[Zachary Waldowski (zwaldowski)]

Martin, I thank you for your help, but I pride myself on the fact that I am neither a child nor an idiot. I have now reinstalled Ubuntu *twice* in order to test everything again, and again, and again, and AGAIN. I have enabled every damned PPA known to include a package that could have a remote possibility of helping and NOTHING has helped me. Once again, I appreciate your help and want to get this bug fixed as much as anybody, but I have no appreciation nor patience for being told that I don't care enough/aren't smart enough to be installing packages when I enable repositories. I run to check my e-mail every couple of minutes to see if there's a new update on this bug; and when there is, I waste no time in checking it, for I am hoping - no, PRAYING - to get the system working that I've used now since I got the laptop in 2007 and for some insane reason now freezes randomly on a supposedly stable system. Thank you for your time, and thanks for wasting mine.

[Martin Pitt (pitti)]

zwaldowski [2009-05-04 10:48 -0000]:
> Martin, I thank you for your help, but I pride myself on the fact that I
> am neither a child nor an idiot.

I wasn't implying you were. You just said you saw this bug on a
pristine Ubuntu installation, and mentioned nowhere that you were
using the packages from jaunty-proposed. If you were, and you still
experience the hangs, that's bad, and should count as
verification-failed. That just wasn't clear from your previous
comment.

Thanks & sorry for the noise

[erakko (erakko92)]

I don't experience any kind of freezing, but after I updated from 8.10 to 9.04, my graphics were "fucked up" with same Intel chipset as here. When booting, I get error that my graphics card, monitor and screen can't be detected properly and only way to use this computer is going to low-graphics mode. There I have this small resolution and I haven't got any solution for it either, and I think I won't be finding any for it until I get the error occured at booting away. I just wonder that does this have anything to do with this bug, or am I just wasting my time on updating this page every 10 minutes?

[Jithin Emmanuel (jithin1987)]

Using the intel package for few hours and no freeze so far.
This also seems to have fixed https://bugs.launchpad.net/bugs/338669 ,
painting problem with qt, which I saw working only with UXA.

[Maurizio (mauriziosilverii)]

I updated from 8.10 to 9.04. My video card is intel i965 on Acer Aspire 5315. I have freeze problem when compiz is running. If i set no desktop effects, the system run fine.

[Jithin Emmanuel (jithin1987)]

I was wrong about this fix fixing https://bugs.launchpad.net/bugs/338669 .

[Zachary Waldowski (zwaldowski)]

@Martin: I beg to differ. You even quoted it yourself:

> My system is stock... the only difference from stock 9.04 is Bryce's package.

> stock system with proposed packages

[Nicolas Valcarcel (nvalcarcel)]

The fix doesn't fix the problem for me, it makes thing better (freezed the system after ~15 minutes instead of ~2) but it doesn't fully fix it.

[Markus Kopp (mkopp)]

I didn't have any freeze since installing the patch. Compiz was enabled.
After enabling UXA sometimes characters were corrupted. This was the reason why i also enabled "Migration Heuristics" "Greedy". After that the corruption disappeared. Also no freezes so far.
I think increasing the virtual size is a workaround for some of us, but it's not a real Fix.

[Bryce Harrington (bryce)]

On Mon, May 04, 2009 at 07:50:14PM -0000, Markus Kopp wrote:
> I think increasing the virtual size is a workaround for some of us, but it's not a real Fix.

Note that I've never described it as a 'real fix'. If you check you'll
see I've explicitly stated it is a workaround, but a better workaround
than disabling compiz entirely on this chipset.

[Bryce Harrington (bryce)]

On Mon, May 04, 2009 at 11:33:10AM -0000, erakko wrote:
> I don't experience any kind of freezing, but
> ...
> I just wonder that does this have anything to do with this bug, or am
> I just wasting my time on updating this page every 10 minutes?

If you check the title of this bug you can see it is about a "freeze"
bug. If you do not experience any kind of freezing, you do not have
this bug, and so yes you are just wasting your time.

[Bryce Harrington (bryce)]

On Mon, May 04, 2009 at 10:48:50AM -0000, zwaldowski wrote:
> Martin, I thank you for your help, but I pride myself on the fact that I
> am neither a child nor an idiot. I have now reinstalled Ubuntu *twice*
> in order to test everything again, and again, and again, and AGAIN.

zwaldowski, while I sympathize with the fact that your freeze is not
fixed by the tricks that have fixed other people's freezes, losing your
cool at Martin is not going to result in people wanting to help you.

For what it's worth, from the non-correlation of your freeze with the
workarounds others have found affected things for them, I suspect
whatever issue you have is unrelated. Since we are focusing this bug on
the class of freeze which is mitigated by adjusting Virtual, if that
workaround does not affect your freeze, then you should look elsewhere
for a fix.

[Zachary Waldowski (zwaldowski)]

I am aware of that. In what capacity I can, I apologize to Martin and you; I had exams that morning and was not in any sort of positive mood this morning. That being said, I will not - nor will I ever, personally speaking - accept being talked at like I am a half-wit; I can only assume that neither of you would, either, in any situation where your experience (or lack thereof) is not (or is, respectively) easily impressed on others.

> I suspect whatever issue you have is unrelated..

At this point, I highly doubt that considering that everything worked fine in Intrepid and rolling back to that driver fixed things to an extent. I am having the same class of bug, and have reported my personal version in bug 345119; this bug got virtually no attention and I was told by a handful of commenters to look here for more details.

I would, honestly, be astounded if anybody marked this bug as fixed (which it's on its way to) with the silly Virtual workaround fix, particularly with many users in the comments immediately after it voicing that it is not fixing their issues. This bug is about X freezes starting on April 3rd on the i965 chipset, is it not? Where else do you expect me to go here to fix this bug?

[Noel J. Bergman (noeljb)]

Just clarifying, in case some people may be confused by their hardware, that this bug is only for people who use the Intel graphics chip, not generically others in the 965 family, e.g., on my T61p:

$ lspci | grep -E "nVidia|965"
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 0c)
01:00.0 VGA compatible controller: nVidia Corporation Quadro FX 570M (rev a1)

Mind you, many of us are seeing similar problems, with other video drivers.

[Zachary Waldowski (zwaldowski)]

Seem to have miraculously caught my system in a VT switch right as a freeze happened, copied the Xorg log and looked at it later, seems to have some things I've never seen before.

[Steve Langasek (vorlon)]

zwaldowski,

That log file shows conclusively that you were *not* running the fixed version of the xserver-xorg-video-intel package.

(II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
(--) intel(0): Chipset: "965GM"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xF8000000
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(--) intel(0): Using UXA for acceleration
(II) intel(0): 2 display pipes available.

If you were using the driver from jaunty-proposed, there would be an additional line here, saying:

 (II) Defaulting Virtual to 2048 2048 for i965.

Since this line is not present, and since I don't see any other evidence in the log that you have a manual "Virtual" setting in /etc/X11/xorg.conf, I have to conclude that you don't have the fixed driver installed.

Please check the version of the xserver-xorg-video-intel package that you have installed. Only version 2:2.6.3-0ubuntu9.1 in jaunty-proposed includes the workaround for this bug. Since the verification of this bug fix is not yet done, it has not been published to jaunty-updates where it's made available by default to users; and the binary packages for this version only became available May 1 21:05 BST, which I believe was after your first comments stating that the fix doesn't work. So perhaps you missed these updated binary packages becoming available?

[Oliver Kastler (1730-gmx)]

For what its worth, the somewhere above mentioned fix with this xorg.conf setting when using EXA:
Option "MigrationHeuristic" "greedy"
seemed to solve my freezes on a Dell inspiron 1525 with this graphic:

00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

All with a stock up to date Kubuntu 9.04

I did not use compiz, but still got these freezes, kind of randomly, even when not using the computer (yes, it was turned on, no screensaver started running, the screen just froze, and I couldn't do CTRL-ALT-F1 nor CTRL-BACKSPACE (I enabled that in the xorg.conf).

I tried with XAA and EXA before, both did freeze, UXA failed to start (didn't check any further).

[Sebastian Rühl (sebastian-ruehl)]

There is a Problem with the 121_i965_default_to_virtual_2048_2048.patch in the xserver-xorg-video-intel-2:2.6.3-0ubuntu9.1
package.
If you specify a Virtual Resolution greater than 2048_2048 in the xorg.conf it simply will be ignored.
My workaround is a package from a ppa (which I can't find anymore) xserver-xorg-video-intel-2:2.6.3-0ubuntu9 which allows me to use my monitor beside my main screen instead of above. ;)
Maybe that's just a bug in the patch...

[Martin Pitt (pitti)]

Sebastian [2009-05-05 9:52 -0000]:
> There is a Problem with the
> 121_i965_default_to_virtual_2048_2048.patch in the
> xserver-xorg-video-intel-2:2.6.3-0ubuntu9.1 package. If you specify
> a Virtual Resolution greater than 2048_2048 in the xorg.conf it
> simply will be ignored.

This was fixed in version 2.6.3-0ubuntu9.2 which is now in
jaunty-proposed for testing.

[Jithin Emmanuel (jithin1987)]

Also one more problem I cannot do a virtual terminal switch after resuming from hibernation. Contents of xorg.log just before I attempted VT switch and reverted back to VT 7.
On VT switch a blank screen is shown.

(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) Open ACPI successful (/var/run/acpid.socket)
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0d000000 (pgoffset 53248)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x00000fff: power context (4 kB)
(II) intel(0): 0x0077f000: end of stolen memory
(II) intel(0): 0x0077f000-0x0cffffff: DRI memory manager (205316 kB)
(II) intel(0): 0x0d000000-0x0fffffff: exa offscreen (49152 kB)
(II) intel(0): 0x10000000: end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x0077f000: start of memory manager
(II) intel(0): 0x0079f000-0x0179efff: depth buffer (16384 kB) Y tiled
(II) intel(0): 0x0179f000-0x0279efff: back buffer (16384 kB) X tiled
(II) intel(0): 0x0279f000-0x0379efff: front buffer (16384 kB) X tiled
(II) intel(0): 0x0379f000-0x0379ffff: overlay registers (4 kB)
(II) intel(0): 0x037a0000-0x037a9fff: HW cursors (40 kB)
(II) intel(0): 0x0d000000: end of memory manager
(WW) intel(0): ESR is 0x00000011, page table error
(WW) intel(0): PGTBL_ER is 0x00000100, display B pte
(WW) intel(0): Existing errors found in hardware state.
(II) intel(0): using SSC reference clock of 100 MHz
(II) intel(0): Selecting standard 18 bit TMDS pixel format.
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is off
(II) intel(0): Display plane A is now disabled and connected to pipe A.
(II) intel(0): Pipe B is on
(II) intel(0): Display plane B is now enabled and connected to pipe B.
(II) intel(0): Output VGA is connected to pipe none
(II) intel(0): Output LVDS is connected to pipe B
(II) intel(0): Output TMDS-1 is connected to pipe none
(II) intel(0): Output TV is connected to pipe none
(--) SynPS/2 Synaptics TouchPad touchpad found
(II) AT Translated Set 2 keyboard: Device reopened after 1 attempts.
(II) Video Bus: Device reopened after 1 attempts.
(II) Macintosh mouse button emulation: Device reopened after 1 attempts.
(II) PS/2 Generic Mouse: Device reopened after 1 attempts.
(II) CHICONY HP Basic USB Keyboard: Device reopened after 1 attempts.
(II) USB Optical Mouse: Device reopened after 1 attempts.

[Matt Zimmerman (mdz)]

I've been running with the packages from jaunty-proposed:

ii compiz 1:0.8.2-0ubuntu8.1 OpenGL window and compositing manager
ii xserver-xorg-video-intel 2:2.6.3-0ubuntu9.1 X.Org X server -- Intel i8xx, i9xx display d

for three days now without incident. I haven't had a chance to stress test it with a script yet, but am at least confident that it does not regress, and seems to avoid the crashes.

[Zachary Waldowski (zwaldowski)]

Steve, I find it hard to believe - no impossible - that I don't have the packages. Since working with this bug, I reinstalled Jaunty three times with xforcevesa enabled, and three times have installed the proposed packages each time before switching back to "intel" from "vesa". Not that this kind of confusion is new to me, but I do have the package. I'm tapping this from my phone, but I'll prove/provide my package versions when I get back to my laptop.

And, as I attempted to do yesterday and failed, I apologize for any misplaced anger or bad feelings. I had exams yesterday, and two characteristics of nervousness in me are a regrettably short temper and an impulsive checking of my e-mail. Perfect storm, right?

[Peter Imrich (peter-imrich)]

I've installed proposed intel driver package and forced compiz. My effects are back and no freezes .. My windows colleagues in the office are jealous again :)

Peter

[Peter Imrich (peter-imrich)]

I use Dell D630

[Zachary Waldowski (zwaldowski)]

zachary@zachary-laptop:~$ apt-show-versions -a -p xserver-xorg-video-intel
xserver-xorg-video-intel 2:2.6.3-0ubuntu9.1 install ok installed
xserver-xorg-video-intel 2:2.6.3-0ubuntu9 jaunty archive.linux.duke.edu
xserver-xorg-video-intel 2:2.6.3-0ubuntu9.1 jaunty-proposed archive.linux.duke.edu
xserver-xorg-video-intel/jaunty-proposed uptodate 2:2.6.3-0ubuntu9.1
zachary@zachary-laptop:~$ apt-show-versions -a -p xserver-xorg-video-intel
xserver-xorg-video-intel 2:2.6.3-0ubuntu9.1 install ok installed
xserver-xorg-video-intel 2:2.6.3-0ubuntu9 jaunty archive.linux.duke.edu
xserver-xorg-video-intel 2:2.6.3-0ubuntu9.1 jaunty-proposed archive.linux.duke.edu
xserver-xorg-video-intel/jaunty-proposed uptodate 2:2.6.3-0ubuntu9.1
zachary@zachary-laptop:~$ apt-show-versions -a -p compiz
compiz 1:0.8.2-0ubuntu8.1 install ok installed
compiz 1:0.8.2-0ubuntu8 jaunty archive.linux.duke.edu
compiz 1:0.8.2-0ubuntu8.1 jaunty-proposed archive.linux.duke.edu
compiz/jaunty-proposed uptodate 1:0.8.2-0ubuntu8.1
zachary@zachary-laptop:~$ cat /etc/xorg/X11.conf
cat: /etc/xorg/X11.conf: No such file or directory
zachary@zachary-laptop:~$ cat /etc/X11/xorg.conf
Section "Device"
 Identifier "Configured Video Device"
 Driver "vesa"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
EndSection
zachary@zachary-laptop:~$

Just got the freeze again, I'm now back with VESA as my driver.

[Jithin Emmanuel (jithin1987)]

I got my first freeze with the jaunty-proposed package. It happened after I logged in and started kvpnc. This is the only freeze I had in days and it happened pure randomly. I have a feeling that this bug is far from over.

[Marco (the-marco)]

So I had the freeze bug several times after upgrading from Ubuntu 8 to 9 (compiz and screen effects enabled).
I used an own customized xorg.conf, so it was not upgraded automatically.

Found the workarounds here and set virtual size to 2560x2048, MigrationHeuristic to greedy and AccelMethod to EXA in xorg.conf

Works without any freezes now for the last 10 days, so this seems to fix it. (using IntelMobile GME965 rev 03)

Anyway, this fixed the symptoms - but not the mysterious cause of all!

[Riki Villalba (rikivillalba)]

One question:
Is it equivalent to specify a Virtual Size of 2048 2048 in xorg.conf to use the patched xserver-xorg-video-intel?
I have a Dell Inspiron 1525 with GM965 X3100 Intel card and Kubuntu Jaunty amd64
I also have the latest repository available mesa* and libgl* packages
I use the following xorg.conf configuration and apparently fixes the freeze (previously, my desktop freezes after 20, before using Alt SysRq K K):

Section "Screen"
  Identifier "Default Screen"
  Monitor "Configured Monitor"
  Device "Configured Video Device"
  SubSection "Display"
   Virtual 2048 2048
  EndSubSection
EndSection

I also use the EXA and Greedy options.
Thanks;

[Riki Villalba (rikivillalba)]

One question:
Is it equivalent to specify a Virtual Size of 2048 2048 in xorg.conf to use the patched xserver-xorg-video-intel?
I have a Dell Inspiron 1525 with GM965 X3100 Intel card and Kubuntu Jaunty amd64.
I also have the latest repository available mesa* and libgl* packages.
Previously, my desktop freezes after 20, before using Alt SysRq K K to recover a svgalib console.
By using the following xorg.conf configuration, the freeze is apparently fixed :

Section "Screen"
  Identifier "Default Screen"
  Monitor "Configured Monitor"
  Device "Configured Video Device"
  SubSection "Display"
   Virtual 2048 2048
  EndSubSection
EndSection

I also use the EXA and Greedy options.

Thanks;

[wirechief (wirechief)]

It would make sense if someone could make a script that would test for
all the "proposed" fix's and those
users who are not meeting the test be advise that they are not running
the fix's and their results cannot be
judged valid against this bug. too many variables for an easy id of the fault..

On Tue, May 5, 2009 at 11:51 AM, Ricardo Villalba
<email address hidden> wrote:
> One question:
> Is it equivalent to specify a Virtual Size of 2048 2048 in xorg.conf to use the patched xserver-xorg-video-intel?
> I have a Dell Inspiron 1525 with GM965 X3100 Intel card and Kubuntu Jaunty amd64
> I also have the latest repository available  mesa* and libgl* packages
> I use the following xorg.conf configuration and apparently fixes the freeze (previously, my desktop freezes after  20, before using Alt SysRq K K):
>
> Section "Screen"
>  Identifier "Default Screen"
>  Monitor "Configured Monitor"
>  Device "Configured Video Device"
>  SubSection "Display"
>   Virtual 2048 2048
>  EndSubSection
> EndSection
>
> I also use the EXA and Greedy options.
> Thanks;
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Ernesto Brau (gooneto)]

This jaunty-proposed fix works for me as well. I've been using compiz for three days now without any freezes. Copmiz still feels a little sluggish, though. Is this related to this issue or is it something else?

[SebastianG (basura-twominds)]

I can confirm this workaround is working and have fixed other issues as well (Bug #345119).

However I'm now not able to change the Virtual Setting and it's fixed on 2048 x 2048.

The only configuration I have in xorg.conf is:

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
        SubSection "Display"
                Virtual 3360 2048
        EndSubSection
EndSection

I have and external monitor of 1920x1200 plus the internal LVDS of 1440x900. Since the release of this patch I'm not able to activate the external monitor.

Using randr gives me:
Screen 0: minimum 320 x 200, current 1360 x 768, maximum 2048 x 2048

On xorg.0.log I see:
(II) intel(0): Defaulting Virtual to 2048 2048 for i965.

[Geir Ove Myhr (gomyhr)]

@SebastianG: This has been fixed in 2.6.3-0ubuntu9.2 that hit
jaunty-proposed today. See bug 370777. If you don't want to wait until
it comes to your mirror, you can get a binary from
https://launchpad.net/ubuntu/jaunty/+source/xserver-xorg-video-intel/2:2.6.3-0ubuntu9.2
.

[Laurent Claessens (moky-math)]

Can someone indicate me how to apply the workaround, from a liveCD ?

I added it in my source.list :
deb http://be.archive.ubuntu.com/ubuntu/ jaunty-proposed main

I got some upgrades, but no ameliorations for the freeze. I guess that I have something else to do. There are more than 400 comments; no way for me to retrieve the workaround.
Could be useful to add a section "how to test the patch" in the description of the bug (subsection of [Patch for Jaunty]).

Thanks a lot for all

[Zachary Waldowski (zwaldowski)]

I'm not sure the exact combination (new kernel, new proposed -intel package, Xorg.conf) but the problems seems to have disappeared for the time being. My xorg.conf is as follows. It works, now, with both EXA and UXA; I use UXA to fix the long standing "dragging windows with 3D/video in them" problem.

Section "Device"
 Identifier "Configured Video Device"
 Driver "intel"
 Option "MigrationHeuristic" "greedy"
 Option "AccelMethod" "uxa"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 DefaultColorDepth 24
 Subsection "Display"
  Depth 24
  Virtual 2960 2048
 EndSubsection
EndSection

[Zachary Waldowski (zwaldowski)]

Damn! Just got my first freeze in over six hours (with bunches of standbys, hotplugs, display resizes, and 3D graphics in between), and then one within a minute of rebooting! Looks like I spoke too soon.

Bryce, your theory looks more right by the day... but, to find a fix and not a workaround... ?

[Theodore Brown (theodorejb)]

When I downloaded Ubuntu 9.04 when it first came out, I had this crash occur all the time. There must have been some update that made it lot more stable now, though. So far I have had it crash only once recently. That was when I was playing music in Rhythmbox AND running the visualization. It doesn't crash just while playing music. I had to run the visualization for a few minutes before it would crash.

[Matt Zimmerman (mdz)]

I just experienced a freeze while running:

ii compiz 1:0.8.2-0ubuntu8.1 OpenGL window and compositing manager
ii xserver-xorg-video-intel 2:2.6.3-0ubuntu9.1 X.Org X server -- Intel i8xx, i9xx display d

which means the workaround seems to have not completely avoided the issue for me, only made it less frequent.

[Noel J. Bergman (noeljb)]

> the workaround seems to have not completely avoided the issue for me, only made it less frequent.

What kind of freeze? What I've been seeing (Bug 359245) is unrelated to the Intel driver. I noticed just the other day that at least one time when I had the system freeze up, that hald had died and not restarted. Can you check to see if you see the same sort of thing?

[Martin Pitt (pitti)]

Michael, since I can't commit to the compiz bzr, would you mind reverting the 965 blacklisting in Karmic and upload? Thanks!

[supiik (peter-iring)]

Hi,

this bug occurs mostly to me when I am scrolling the window (90%)
Most often in opera. In firefox it is not so obvious but happens after several hours of work.

I have a feeling that it started after my experiments with compiz effects and UXA/EXA.

If you need more info please tell me how to get it.

Good luck
Peter

[Soeren Sonnenburg (bugreports-nn7)]

On Thu, 2009-05-07 at 18:02 +0000, Matt Zimmerman wrote:
> I just experienced a freeze while running:
>
> ii compiz 1:0.8.2-0ubuntu8.1 OpenGL window and compositing manager
> ii xserver-xorg-video-intel 2:2.6.3-0ubuntu9.1 X.Org X server -- Intel i8xx, i9xx display d
>
> which means the workaround seems to have not completely avoided the
> issue for me, only made it less frequent.

Matches my experience even with latest kernel (.30-rc5) and video-intel
from git (2.7.99+) - yes *with* uxa. Issue appears usually between 6 and
24 hours of use. I can still ssh into the machine etc...

[Theodore Brown (theodorejb)]

I just had the display freeze again and I had to do a hard restart.
Hardware: Gateway P-6860 FX notebook with nvidia 8800M GTS video card running the recommended 180 drivers (with Extra visual effects enabled).
Connected to internet via Intel 965 wireless n network card through Belkin wireless n router (WPA2 secured (I think)).
Running Ubuntu 9.04 with latest updates.
All I was running was Firefox 3.0.10 with three tabs open (I also might have had one Nautilus window open, but I can't remember), Gmail, Google Reader, and the VLC Media Player Download for Ubuntu page (http://www.videolan.org/vlc/download-ubuntu.html).
The computer had been running for about 45 min.
I had just scrolled to the top of a (very) long email in the Gmail tab, clicked the Inbox button to go to my inbox, and then switched to the VLC tab when everything froze.
I don't know if all this will help, but I tried to give as much info as possible.

[wirechief (wirechief)]

Just had a freeze, i changed from exa to uxa and had several applications open and was in the process of logging into
my gmail account when it hit.
I have upgraded to Karmic 9.10 and am using the following..
Linux wirechief-laptop 2.6.30-020630rc4-generic #020630rc4 SMP Fri May 1 08:25:59 UTC 2009 x86_64 GNU/Linux
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

ii xserver-xorg-video-intel 2:2.7.0-1ubuntu2~xup~1 X.Org X server -- Intel i8xx, i9xx display d
ii xserver-xorg-video-intel-dbg 2:2.7.0-1ubuntu2~xup~1

ii libgl1-mesa-dev 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt A free implementation of the OpenGL API -- G
ii libgl1-mesa-dri 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt A free implementation of the OpenGL API -- D
ii libgl1-mesa-dri-dbg 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Debugging symbols for the Mesa DRI modules
ii libgl1-mesa-glx 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt A free implementation of the OpenGL API -- G
ii libgl1-mesa-glx-dbg 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Debugging symbols for the Mesa GLX runtime
ic libgl1-mesa-swx11 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- r
ii libglu1-mesa 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt The OpenGL utility library (GLU)
ii libglu1-mesa-dev 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt The OpenGL utility library -- development fi
rc libosmesa6 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt Mesa Off-screen rendering extension
ii mesa-common-dev 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Developer documentation for Mesa
ii mesa-utils 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Miscellaneous Mesa GL utilities

[Jithin Emmanuel (jithin1987)]

I had freeze with xserver-xorg-video-intel from jaunty-proposed. So its not ****** fixed and I have lost hope that its gonna ever be fixed. In search of a new distro now. ( Should have done long ago)

[Jonathan Blackhall (johnny-one-eye)]

Any word on whether the crash fixes in the newly released xf86-video-intel 2.7.1 fixes this?

[Andres Mujica (andres.mujica)]

Jithin, Wirechief. without your help debugging and testing workarounds and hacks for solving this issue we weren't where we are now, i mean at the very first appearence of this bug, 4-5 freezes per day was standard now we're about several weeks without freezes.

Sure you can look for a different distribution, but as this bug is crossdistro probably you'll face it again. So please bear with us in the meantime. I'm confident that this would be solved soon. A lot of people are working on it.

Thanks again for all the patience and help that you provided here.

[wirechief (wirechief)]

I realize that this bug is present across all linux platforms, it is a
tough nut to crack and am willing to
bear out these freezes, knowing that uxa is not completely ready for
me is not a issue, I am not ready
to change course, if i should of given more information on my latest
freeze I can try to get it to come back
and provide whatever reporting i can.

On Tue, May 12, 2009 at 11:53 PM, Andres Mujica
<email address hidden> wrote:
> Jithin, Wirechief.  without your help debugging and testing workarounds
> and hacks for solving this issue we weren't where we are now, i mean at
> the very first appearence of this bug, 4-5 freezes per day was standard
> now we're about several weeks without freezes.
>
> Sure you can look for a different distribution, but as this bug is
> crossdistro probably you'll face it again.  So please bear with us in
> the meantime.  I'm confident that this would be solved soon.  A lot of
> people are working on it.
>
> Thanks again for all the patience and help that you provided here.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Reach out and share life, care for others,

[Soeren Sonnenburg (bugreports-nn7)]

On Wed, 2009-05-13 at 03:53 +0000, Andres Mujica wrote:
> Jithin, Wirechief. without your help debugging and testing workarounds
> and hacks for solving this issue we weren't where we are now, i mean at
> the very first appearence of this bug, 4-5 freezes per day was standard
> now we're about several weeks without freezes.

YMMV, once per day here.

The problem here is, that 'we' don't know whether people are working on
it and also if there is anything 'we' can do to help. Please keep us
up-to-date.

> Sure you can look for a different distribution, but as this bug is
> crossdistro probably you'll face it again. So please bear with us in
> the meantime. I'm confident that this would be solved soon. A lot of
> people are working on it.

The only thing to criticize here is that this showstopper was known
before jaunty was released, so IMHO it would have been worth delaying
jaunty (it now went through the press and might have caused more much
more damage).

[Joachim Nilsson (troglobit)]

Hi,

I just had to reply to you "off list", so to speak. That answer was very well put, thank you for taking the time to formulate and writing it!

I have been sitting here, in my corner of the world, considering doing the very same thing, but I guess I lack the proper words.

Thanks
 /Joachim - From Sweden, with the same bug, patiently awaiting the wizards to fix it. :)

Andres Mujica wrote, on 05/13/2009 05:53 AM:
> Jithin, Wirechief. without your help debugging and testing workarounds
> and hacks for solving this issue we weren't where we are now, i mean at
> the very first appearence of this bug, 4-5 freezes per day was standard
> now we're about several weeks without freezes.
>
> Sure you can look for a different distribution, but as this bug is
> crossdistro probably you'll face it again. So please bear with us in
> the meantime. I'm confident that this would be solved soon. A lot of
> people are working on it.
>
> Thanks again for all the patience and help that you provided here.
>

[Bryce Harrington (bryce)]

2.7.1 advertises some freeze fixes. I've packaged it for jaunty. It's available in the x-updates ppa:
https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/

[Soeren Sonnenburg (bugreports-nn7)]

On Wed, 2009-05-13 at 08:37 +0000, Bryce Harrington wrote:
> 2.7.1 advertises some freeze fixes. I've packaged it for jaunty. It's available in the x-updates ppa:
> https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/

The changelog sounds promising:

We have verified that several of the reported bugs of GPU crashes,
(mouse continues to move, but otherwise X is totally unresponsive), are
fixed with the commit by Keith Packard in 2.7.1 to correct the
computation of the batch space required. If you have previously reported
a GPU-crash bug in bugs.freedesktop.org, please test with 2.7.1 and
report your findings in the bug. If the crash is fixed, please celebrate
with us!

If the crash persists, please attach the output of intel_gpu_dump
available here (and hopefully packaged in your distribution of choice
soon):

 git://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools
 (Requires Linux kernel >= 2.6.30)

Thanks to everyone who has helped to improve this driver!

Thanks for packaging it so quickly and lets hope we can celebrate with
the developers :)

[Joachim Nilsson (troglobit)]

Bryce Harrington wrote, on 05/13/2009 10:37 AM:
> 2.7.1 advertises some freeze fixes. I've packaged it for jaunty. It's available in the x-updates ppa:
> https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/

Thanks, this is really incredible. Now even UXA seems to work fine, doing bizarre Compiz effects have never been this smooth before on my ThinkPad T61.

Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

# A 1920x1200 external display and a 1280x800 LCD built-in
# gives a rather large Virtual.
Section "Screen"
 Identifier "Configured Screen Device"
 Device "Configured Video Device"
 SubSection "Display"
  Virtual 3200 1200
 EndSubSection
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Option "AccelMethod" "uxa"
EndSection

The repos I use are standard Jaunty repos, including proposed updates, and this X Swat PPA. Nothing more.

Again, thank you!
 /Joachim

[Jithin Emmanuel (jithin1987)]

Will this 2.7.1 driver be made available to jaunty updates soon.

On Wed, May 13, 2009 at 3:00 PM, Joachim Nilsson <
<email address hidden>> wrote:

> Bryce Harrington wrote, on 05/13/2009 10:37 AM:
> > 2.7.1 advertises some freeze fixes. I've packaged it for jaunty. It's
> available in the x-updates ppa:
> > https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/<https://edge.launchpad.net/%7Eubuntu-x-swat/+archive/x-updates/>
>
> Thanks, this is really incredible. Now even UXA seems to work fine,
> doing bizarre Compiz effects have never been this smooth before on my
> ThinkPad T61.
>
> Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller
> [8086:2a02] (rev 0c)
>
> # A 1920x1200 external display and a 1280x800 LCD built-in
> # gives a rather large Virtual.
> Section "Screen"
> Identifier "Configured Screen Device"
> Device "Configured Video Device"
> SubSection "Display"
> Virtual 3200 1200
> EndSubSection
> EndSection
>
> Section "Device"
> Identifier "Configured Video Device"
> Option "AccelMethod" "uxa"
> EndSection
>
> The repos I use are standard Jaunty repos, including proposed updates,
> and this X Swat PPA. Nothing more.
>
> Again, thank you!
> /Joachim
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Jay Leno <http://www.brainyquote.com/quotes/authors/j/jay_leno.html> -
"Don't forget Mother's Day. Or as they call it in Beverly Hills, Dad's Third
Wife Day."

[Mario (diraimondo)]

Jithin Emmanuel wrote:
> Will this 2.7.1 driver be made available to jaunty updates soon.

I guess it is not possible: the maintainers could backport the patches
but it maybe difficult.

Mario

[vervelover (alessiopangos)]

Well, I totally understand who is seeking for a new distro, maybe one that really is for human beings. Because you favor the geeks, giving them the latest and greatest, 'cause they know what a ppa is and whatever. But you know if you were serious about a distro for human beings, you should have delayed jaunty or at least have it shipped with Intrepid's intel drivers. It's a big let down for everyone that believes in open-source being the future of computing, and sees ubuntu as the biggest hope for spreading linux in the world. But ubuntu's just not there, and maybe never will because it's more concerned about not losing its geek user base, than releasing and operating system for everyone, and perhaps ever will.

[Andres Mujica (andres.mujica)]

Jithin, please add the X Swat PPA for testing the 2.7.1 with Jaunty.

https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/

According to feedback received and SRU discussion it may go *or not* into Jaunty updates. First step is test it.

[Andres Mujica (andres.mujica)]

Verveloper: You raise very valid points here, probably we could have made a much better work.

However, as this appeared very late at the release cycle, several countermeasures were taken in order to minimize the impact of this freeze bugs; including Release Notes, blacklisting driver for Compiz, involving upstream directly into this bug, several Ubuntu developers working *and affected* with this, again, probably this wasn't enough.

But, the beauty thing here, is that everyone had learned a lot, and at the coming UDS there will be a specific session to discuss this situation and please be assured that your concern would be discussed there as well.

We do believe in Open Source, we do believe that we made software for Human Beings and our hope is that Ubuntu would help *a lot* in spreading Linux around the world. Things like this only teach us about how to accomplish this vision.

[Alwin Garside (yogarine)]

true "human beings" could also just opt to stick to 8.10 or choose the 8.04
LTS release. "Human Beings" should read release notes. And the advantage of
fixed 6 month schedules is that you can easily fall back to an earlier
release...

On May 13, 2009 2:05 PM, "vervelover" <email address hidden> wrote:

Well, I totally understand who is seeking for a new distro, maybe one
that really is for human beings. Because you favor the geeks, giving
them the latest and greatest, 'cause they know what a ppa is and
whatever. But you know if you were serious about a distro for human
beings, you should have delayed jaunty or at least have it shipped with
Intrepid's intel drivers. It's a big let down for everyone that believes
in open-source being the future of computing, and sees ubuntu as the
biggest hope for spreading linux in the world. But ubuntu's just not
there, and maybe never will because it's more concerned about not losing
its geek user base, than releasing and operating system for everyone,
and perhaps ever will.

-- [i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392 You received this...

[Laurent Claessens (moky-math)]

vervelover a écrit :
> Well, I totally understand who is seeking for a new distro, maybe one
> that really is for human beings. Because you favor the geeks, giving
> them the latest and greatest, 'cause they know what a ppa is and
> whatever. But you know if you were serious about a distro for human
> beings, you should have delayed jaunty or at least have it shipped with
> Intrepid's intel drivers. It's a big let down for everyone that believes
> in open-source being the future of computing, and sees ubuntu as the
> biggest hope for spreading linux in the world. But ubuntu's just not
> there, and maybe never will because it's more concerned about not losing
> its geek user base, than releasing and operating system for everyone,
> and perhaps ever will.
>
I do agree. Regarding bug number one, one could notice that MS leaves
more testing time between the beta version and the final version than
Ubuntu for a whole cycle.

Please, if the aim of LTS version is to provide a certified stable OS,
do not advertise the other versions, especially when there still remains
a critical crash for a widespread GPU.
Now, I'm obliged to tell all my friends I converted to Linux (namely :
Ubuntu) to not update to Jaunty because there is a critical bug that
makes the computer simply unusable.

I have nothing against the fact to *release* Jaunty with that bug, but I
don't understand why there should be a big button "DOWNLOAD UBUNTU 9.04;
enjoy an improved user experience" on the main page www.ubuntu.com.

A part of that, I'm sincerely grateful for all your work to make free
software more human. I didn't paid for Ubuntu[1] and I know the first
line of GPL : No warranty ;)

[1] Although, I paid for a Dell with Gutsy pre-installed.

[Zachary Waldowski (zwaldowski)]

I'm going to try my darndest to stay in Ubuntu all day today. While I admit that this is going to me a tentative statement in all capacities, I'm giddy enought to want to shout from the rooftops (tentatively, I remind you) that the bug is (so far) fixed in xserver-xorg-video-intel 2.7.1. FIXED, I swear. I use UXA on this laptop (in order to have windows that have 3D in them move around like they should without flickering) and I haven't received even a slowdown yet. I'm also receiving some of the best speeds I've ever gotten on this laptop in glxgears and glblur. I sure to hope 2.7.1 can somehow get in the updates repo, or at least have the fixes backported.

[Botond Szász (boteeka)]

@Alwin Garside:
Mostly agree with you, but:

> And the advantage of fixed 6 month schedules is that you can easily fall back to an earlier release...

What exactly is that * easy * fall back mechanism? Reinstall?

[Jithin Emmanuel (jithin1987)]

That's one costly fall back mechanism. Reminds me of days when I was using
windows. Just make me laugh on that so called *fall back* mechanism.

2009/5/13 Botond Szász <email address hidden>

> @Alwin Garside:
> Mostly agree with you, but:
>
> > And the advantage of fixed 6 month schedules is that you can easily
> fall back to an earlier release...
>
> What exactly is that * easy * fall back mechanism? Reinstall?
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Don Marquis <http://www.brainyquote.com/quotes/authors/d/don_marquis.html>
- "Procrastination is the art of keeping up with yesterday."

[wirechief (wirechief)]

I downloaded and installed ii xserver-xorg-video-intel 2:2.7.1-0ubuntu1~xup~1 X.Org X server -- Intel i8xx, i9xx display d
then i changed my xorg.conf so it was set to uxa... I opened firefox to check mail and got a freeze. included this
time my recent debug reporting...
Linux wirechief-laptop 2.6.30-020630rc4-generic #020630rc4 SMP Fri May 1 08:25:59 UTC 2009 x86_64 GNU/Linux
ii libgl1-mesa-dev 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt A free implementation of the OpenGL API -- G
ii libgl1-mesa-dri 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt A free implementation of the OpenGL API -- D
ii libgl1-mesa-dri-dbg 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Debugging symbols for the Mesa DRI modules
ii libgl1-mesa-glx 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt A free implementation of the OpenGL API -- G
ii libgl1-mesa-glx-dbg 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Debugging symbols for the Mesa GLX runtime
ic libgl1-mesa-swx11 7.4-0ubuntu2~bug359392~1 A free implementation of the OpenGL API -- r
ii libglu1-mesa 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt The OpenGL utility library (GLU)
ii libglu1-mesa-dev 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt The OpenGL utility library -- development fi
rc libosmesa6 7.4.1~git20090424+mesa-7-4-branch.bfd6bb31-0ubuntu0sarvatt Mesa Off-screen rendering extension
ii mesa-common-dev 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Developer documentation for Mesa
ii mesa-utils 7.5.0~git20090507+mesa-7-5-branch.6a3004b9-0ubuntu0sarvatt Miscellaneous Mesa GL utilities

[vervelover (alessiopangos)]

>true "human beings" could also just opt to stick to 8.10 or choose the 8.04
>LTS release. "Human Beings" should read release notes. And the advantage of
>fixed 6 month schedules is that you can easily fall back to an earlier
>release...

Yes, of course an LTS that cannot even play a youtube video togheter with an mp3 because of a pulseaudio bug is the solution for everything.. come on. And of course an unexperienced user that is told to upgrade to a new version of the distro straight in the update manager will not do it because he knows that this could eventually break its system. So if you want to hide the fact that something (not everything) is REALLY wrong in the way things have been done since now you're free to do that, but what I think is that things should be said. I appreciate Andres comment, I honestly think that other distros are not doing any better than ubuntu, but I'm afraid things will not change soon, because these mistakes have always been made, and nobody seems to have learned. I hope the Karmic Koala will prove me wrong..

[JP Fiset (jp-fiset)]

I have added the PPA source to my list and updated with the latest intel drivers. After rebooting, I find my mouse is a bit "jerky" when traversing complex visual elements. I have no idea if it is related, but I thought I'd check here if others are experiencing the same.

My machine used to lock up on X about twice a day. No lock up, so far, after several hours.

The accelerator is configured for "uxa".

[Zachary Waldowski (zwaldowski)]

Well, strike that, 2.7.1 doesn't solve a things. Back on Xorg-edgers, waiting for the next freeze to happen. Why is this still listed as Fix Committed?

[Jeremy Nickurak (nickurak)]

Here's a new one:

I just got a old scientific linux machine's X server to freeze with the same symptoms. The trick is that the X clients were from an Ubuntu Jaunty machine running inside Linux-KVM. The host machine does have an intel chipset, but it's using a geforce 8600 gt as its display. Not sure if it's relevant, but it sure seems interesting.

Both the host and guest machines are still up. If there's some info I can grab, let me know.

[Zachary Waldowski (zwaldowski)]

Uploading intel_gpu_dump data and some logs from Jaunty x86_64 with normal stock base, proposed updates, xorg-updates 2.7.1 Intel driver, and 2.6.30rc5 kernel from the so-called "Kernel PPA" (just the .deb's). *Sigh*... hope we can fix this eventually.

[Jithin Emmanuel (jithin1987)]

I also noticed that with uxa performance worsens with new drivers. Then I
removed uxa from xorg.conf. Still performance is not that satisfactory.
On Thu, May 14, 2009 at 4:29 AM, zwaldowski <email address hidden> wrote:

> Well, strike that, 2.7.1 doesn't solve a things. Back on Xorg-edgers,
> waiting for the next freeze to happen. Why is this still listed as Fix
> Committed?
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Vince Lombardi<http://www.brainyquote.com/quotes/authors/v/vince_lombardi.html>
- "We didn't lose the game; we just ran out of time."

[Jithin Emmanuel (jithin1987)]

This 2.7.1 drivers impact performance hugely. It makes desktop usage painfully slow.

[Joachim Nilsson (troglobit)]

Jithin Emmanuel wrote, on 05/14/2009 09:47 AM:
> This 2.7.1 drivers impact performance hugely. It makes desktop usage
> painfully slow.

I must respectfully disagree. My compiz has never been this snappy before. Stability wise it is also a lot better than the stock intel driver in Ubuntu 9.04. My system has been running flawlessly since yesterday with Compiz and UXA enabled. Otoh I only run Firefox, Thunderbird, evince a couple of terminals and Emacs.

Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c)

Really not a fun bug to triage, best of luck to you Ubunteros as well as Intel engineers!

Regards
 /Joachim

[Matthias Blaicher (blaicher)]

I am using UXA with compiz and 3464x1152 resolution, and it flies for
me.... So no regressions for here (I use UXA since jaunty beta though,
maybe I am not spoiled with speed)

[Jithin Emmanuel (jithin1987)]

I just had freeze with 2.7.1 driver without UXA.

[Hans Bull (bullinger)]

This bug affects i855, I have it on a Travelmate 290.

[Geir Ove Myhr (gomyhr)]

bullinger, this bug report is about freezes that occur on the i965 chipsets. You can take a look at
https://launchpad.net/ubuntu/+bugs?field.tag=855gm to see if any of those bugs is the same you have.
If you don't find a bug report describing your problem on the i855 chipset, you have a new bug and please file it as such (preferably using the ubuntu-bug command).

[Hans Bull (bullinger)]

still happens using 2.7.1

[Žygimantas Beručka (zygis)]

Geir Ove Myhr, I don't think there's a real need for another duplicate. I'm pretty much sure the bug is not i965 specific, the problem lies somewhere else. I can second bullinger, my system was hit by the very same constant unpredictable freezes after upgrade to 9.04. Only "NoAccel" "true" allows to avoid it (the aforementioned exa/uxa switches, etc. makes no difference here too). And yes, I have "VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)". The sad news is that no one has a clue what is happening for over a month already and this is critical.

[Geir Ove Myhr (gomyhr)]

Žygimantas Beručka, This bug report is about freezes happening on the 965GM chipset, starting with the update on April 3rd. This bug has 5 duplicates. They are all for the 965GM chipsets (I just double-checked that).

I'm not saying that you and bullinger don't have a real bug, only that commenting on this bug is not going to help. The underlying cause that makes the GPU on 965GM chipsets lock up, is probably different from the underlying cause for the freezes on your i855 chipset.

[Jithin Emmanuel (jithin1987)]

Maybe we should stop trying to do workarounds and hacks for 965 and try to
understand the bigger picture of what is actually happening.

On Thu, May 14, 2009 at 10:42 PM, Geir Ove Myhr <email address hidden> wrote:

> Žygimantas Beručka, This bug report is about freezes happening on the
> 965GM chipset, starting with the update on April 3rd. This bug has 5
> duplicates. They are all for the 965GM chipsets (I just double-checked
> that).
>
> I'm not saying that you and bullinger don't have a real bug, only that
> commenting on this bug is not going to help. The underlying cause that
> makes the GPU on 965GM chipsets lock up, is probably different from the
> underlying cause for the freezes on your i855 chipset.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Bill Cosby <http://www.brainyquote.com/quotes/authors/b/bill_cosby.html> -
"Fatherhood is pretending the present you love most is soap-on-a-rope."

[Travis Whitaker (pi-boy-travis)]

I have been using 2.7.1 driver for about 48 hours now. I don't get freezes, my 3D performance is better than Intrepid's, and I can watch flash videos without tearing again.

[Steve Langasek (vorlon)]

On Thu, May 14, 2009 at 03:14:38PM -0000, Žygimantas Beručka wrote:
> Geir Ove Myhr, I don't think there's a real need for another duplicate.

Yes, there is. Even if this ultimately turns out to be the same bug, it's
very important for our ability to triage bugs that people with different
hardware open separate bug reports, unless otherwise indicated by the
developers. Otherwise, when the freezes people are seeing *aren't* related
(and there's no evidence either way yet in the present case), lumping all
the comments in a single report just makes it incredibly hard for the
developers to extract relevant information from that report.

So please open a separate bug report for your problem.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[Soeren Sonnenburg (bugreports-nn7)]

On Fri, 2009-05-15 at 03:11 +0000, Steve Langasek wrote:
> On Thu, May 14, 2009 at 03:14:38PM -0000, Žygimantas Beručka wrote:
> > Geir Ove Myhr, I don't think there's a real need for another duplicate.
>
> Yes, there is. Even if this ultimately turns out to be the same bug, it's
> very important for our ability to triage bugs that people with different
> hardware open separate bug reports, unless otherwise indicated by the
> developers. Otherwise, when the freezes people are seeing *aren't* related
> (and there's no evidence either way yet in the present case), lumping all
> the comments in a single report just makes it incredibly hard for the
> developers to extract relevant information from that report.
>
> So please open a separate bug report for your problem.

I am not convinced as I am having *this bug* on a i945 too. Why not ssh
into the machine and get a backtrace of Xorg to see if it is the same
problem?

[Mario (diraimondo)]

Soeren Sonnenburg wrote:
> I am not convinced as I am having *this bug* on a i945 too. Why not ssh
> into the machine and get a backtrace of Xorg to see if it is the same
> problem?

I'm not so sure about my card. How can I identify it?

$ lspci | grep -i graphic
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI
Express Graphics Port (rev ff)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller (rev 07)

from xorg.log:
(II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile Intel® GM45
Express Chipset
(--) intel(0): Chipset: "Mobile Intel® GM45 Express Chipset"

Mario

[Bassu Khan (bashukhan)]

Come on guys..!
As per the description this bug apparently it cannot be fixed except the few workarounds it has!
Posting and repeating the same thing again could not lead to a resolution ;)

[Geir Ove Myhr (gomyhr)]

Soeren Sonnenburg wrote:
> I am not convinced as I am having *this bug* on a i945 too. Why not ssh
> into the machine and get a backtrace of Xorg to see if it is the same
> problem?

You may very well have the same symptoms on an i945. It just that
debugging is much easier if we keep the bug reports for different
chipsets separate, and debugging is really our goal here. Please ssh
into the machine and get a backtrace (or more importantly a GPU dump
as described in this bug report). But please upload it to a separate
bug report. If it turns out to be a duplicate of some other bug, it
can be marked as such. If it doesn't add any new information to that
duplicate bug it avoids having lots of redundant information in the
bug report, and any new information can be added in a comment to that
other report. Our goal here is to keep the bug reports simple, since
that makes debugging easier.

Mario wrote:
> I'm not so sure about my card. How can I identify it?
>
> $ lspci | grep -i graphic
> 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI
> Express Graphics Port (rev ff)
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
> Chipset Integrated Graphics Controller (rev 07)
>
> from xorg.log:
> (II) intel(0): Integrated Graphics Chipset: Intel(R) Mobile Intel® GM45
> Express Chipset
> (--) intel(0): Chipset: "Mobile Intel® GM45 Express Chipset"

You have GM45 chipset. Some of the newer chipsets don't list the
numbers and names in the lspci, so I prefer to look in Xorg.0.log.

[Mario (diraimondo)]

Geir Ove Myhr wrote:
> You have GM45 chipset. Some of the newer chipsets don't list the
> numbers and names in the lspci, so I prefer to look in Xorg.0.log.

But is it supposed to be an affected chipset? Before of the
workaround-upload I had a lot of freezes: now they are quiet rare. If I
have a further freeze should, I open a new bug report?

Mario

[Geir Ove Myhr (gomyhr)]

>> You have GM45 chipset. Some of the newer chipsets don't list the
>> numbers and names in the lspci, so I prefer to look in Xorg.0.log.
>
> But is it supposed to be an affected chipset? Before of the
> workaround-upload I had a lot of freezes: now they are quiet rare. If I
> have a further freeze should, I open a new bug report?

I don't know if it is supposed to be. That is, I don't know if the
driver treats the 965GM and GM45 differently in any way. What I do
know is that the function IS_I965G in the driver returns true for the
GM45 chipset (see my first long comment on bug 370777), so it may be
similar enough that it is the same underlying problem. The workaround
uses the IS_I965G function to decide whether to apply it or not, so it
will be applied to your GM45 chipset.

However, all the duplicates of this bug were reported on 965GM
chipsets, so I think it is best to keep it separate until proven
otherwise (or someone who knows the hardware and the driver well says
that they're basically the same). If you can get GPU dumps from a
freeze using the 2.7.1 driver from the x-updates PPA (Personal Package
Archive) and file it in a separate bug report, I think that may be
helpful.

[Laurent Claessens (moky-math)]

I still have freezes.

K-Jaunty with Compiz effects enable.

I added the following to my sources.list
deb http://archive.ubuntu.com/ubuntu/ jaunty-proposed main
deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu jaunty main

My graphical card is (from lspci)

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

Since I have only one computer, I cannot get informations by ssh.

What can I do in order to provide more complete and useful informations ?

[Jithin Emmanuel (jithin1987)]

There is something wring with these drivers. See my attached screen shots. This happens after long usage ,about 24 hrs and after restart everything is back to normal.

[Jithin Emmanuel (jithin1987)]

Any idea what's happening? I am using packages from 2.7.1 drivers from x-updates repository. and 2.6.29.3 kernel.

[Oded Arbel (oded-geek)]

I see similar issues with GM915, but only on KDE - it doesn't happen for me with GNOME. I see similar artifacts all the time in KDE4, so I think this is related to KWin and not specifically the driver.

[VladNistor (vladnistor)]

Oded Arbel, maybe your bug is unrelated. This is a driver bug and it affects both kde & gnome.
Maybe your bug is related to KWin.

[Jithin Emmanuel (jithin1987)]

Found best way to reproduce this bug. Visit this web page

http://upload.wikimedia.org/wikipedia/commons/b/b7/Singapore_port_panorama.jpg

Got from http://bugs.archlinux.org/task/14594

[Mario (diraimondo)]

Jithin Emmanuel wrote:
> Got from http://bugs.archlinux.org/task/14594

They says that the bug is still present in the 2.7.1 version of the
driver. They also speak about a possible patch for the kernel.

Mario

[Vincenzo Ciancia (vincenzo-ml)]

I have a machine affected by this bug, but also another laptop showing exactly the same form of sudden deadlocks, using an ATI radeon. Now the point is that this is a centrino laptop, and the chipset is the same of the other laptop. May this be not a bug in the video driver but somewhere else (e.g. PCI code?).

[Jonathan Aquilina (eagles051387)]

on jaunty i have been seeing the same thing but im not on an intel
chipset but an nvidia nforce 750i. i have to do a hard reboot to get
it working. im currently testing this out to see if the same issues
arises in karmic.

On 5/18/09, Vincenzo Ciancia <email address hidden> wrote:
> I have a machine affected by this bug, but also another laptop showing
> exactly the same form of sudden deadlocks, using an ATI radeon. Now the
> point is that this is a centrino laptop, and the chipset is the same of
> the other laptop. May this be not a bug in the video driver but
> somewhere else (e.g. PCI code?).
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jonathan Aquilina

[Jithin Emmanuel (jithin1987)]

Of course it will be in karmic just visit this url to test.
http://upload.wikimedia.org/wikipedia/commons/b/b7/Singapore_port_panorama.jpg

On Mon, May 18, 2009 at 5:31 PM, eagles051387 <email address hidden>wrote:

> on jaunty i have been seeing the same thing but im not on an intel
> chipset but an nvidia nforce 750i. i have to do a hard reboot to get
> it working. im currently testing this out to see if the same issues
> arises in karmic.
>
> On 5/18/09, Vincenzo Ciancia <email address hidden> wrote:
> > I have a machine affected by this bug, but also another laptop showing
> > exactly the same form of sudden deadlocks, using an ATI radeon. Now the
> > point is that this is a centrino laptop, and the chipset is the same of
> > the other laptop. May this be not a bug in the video driver but
> > somewhere else (e.g. PCI code?).
> >
> > --
> > [i965] X freezes starting on April 3rd
> > https://bugs.launchpad.net/bugs/359392
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Jonathan Aquilina
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
P. J. O'Rourke<http://www.brainyquote.com/quotes/authors/p/p_j_orourke.html>
- "Never fight an inanimate object."

[Jonathan Aquilina (eagles051387)]

dont forget though im not even on an intel chipset but an nforce 750i
chipset. it was rather prevalent for me in jaunty wiht nvidia 180.44
driver in repos but wiht the same driver in karmic it seems like it
was something else as the issue has yet to surface.

On 5/18/09, Jithin Emmanuel <email address hidden> wrote:
> Of course it will be in karmic just visit this url to test.
> http://upload.wikimedia.org/wikipedia/commons/b/b7/Singapore_port_panorama.jpg
>
> On Mon, May 18, 2009 at 5:31 PM, eagles051387
> <email address hidden>wrote:
>
>> on jaunty i have been seeing the same thing but im not on an intel
>> chipset but an nvidia nforce 750i. i have to do a hard reboot to get
>> it working. im currently testing this out to see if the same issues
>> arises in karmic.
>>
>> On 5/18/09, Vincenzo Ciancia <email address hidden> wrote:
>> > I have a machine affected by this bug, but also another laptop showing
>> > exactly the same form of sudden deadlocks, using an ATI radeon. Now the
>> > point is that this is a centrino laptop, and the chipset is the same of
>> > the other laptop. May this be not a bug in the video driver but
>> > somewhere else (e.g. PCI code?).
>> >
>> > --
>> > [i965] X freezes starting on April 3rd
>> > https://bugs.launchpad.net/bugs/359392
>> > You received this bug notification because you are a direct subscriber
>> > of the bug.
>> >
>>
>>
>> --
>> Jonathan Aquilina
>>
>> --
>> [i965] X freezes starting on April 3rd
>> https://bugs.launchpad.net/bugs/359392
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
> --
> Regards
> Jithin Emmanuel
> http://spotm.in
> P. J. O'Rourke<http://www.brainyquote.com/quotes/authors/p/p_j_orourke.html>
> - "Never fight an inanimate object."
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jonathan Aquilina

[Albert Damen (albrt)]

Based on Eric Anholt's findings about freezes due to prefetching beyond end of aperture (b.fd.o 21488), I have done some testing.

With Eric's patch applied in kernel 2.6.30-rc6 I still got the freeze. That seemed to make sense: we are using EXA, and the exa offscreen buffer is using the last page in aperture. So BO's wouldn't use the last page in our case anyways.
Then I patched -intel and pushed back the exa offscreen buffer 4 kB below end of aperture (0x0ed3f000-0x0fffefff: exa offscreen). That still gave the freeze.
Then I pushed a bit harder, now by 32MB (0x0cd40000-0x0dffffff: exa offscreen) --> No freeze anymore.

The 32MB was not a random choice: it matches the 32 MB classic texture buffer we had until beginning of April, which was sitting between exa offscreen and end of aperture. Dropping patch 118_drop_legacy3d.patch, which removed the (unused) classic texture buffer, also solves the freeze issue for me. So maybe that patch (dated 1 April) has been the trigger for this bug?

Now the question is: Is something writing or reading beyond the end of the exa offscreen buffer? Without the 32 MB unused memory after the exa offscreen buffer, that would be beyond end of aperture. How can I find what is doing that?

[Jonathan Aquilina (eagles051387)]

for me and my issue with nvidia freezing it seems to be solved in the
alpha in karmic. could this be an issue with jaunty kernel?

On 5/18/09, Albert Damen <email address hidden> wrote:
> Based on Eric Anholt's findings about freezes due to prefetching beyond
> end of aperture (b.fd.o 21488), I have done some testing.
>
> With Eric's patch applied in kernel 2.6.30-rc6 I still got the freeze. That
> seemed to make sense: we are using EXA, and the exa offscreen buffer is
> using the last page in aperture. So BO's wouldn't use the last page in our
> case anyways.
> Then I patched -intel and pushed back the exa offscreen buffer 4 kB below
> end of aperture (0x0ed3f000-0x0fffefff: exa offscreen). That still gave the
> freeze.
> Then I pushed a bit harder, now by 32MB (0x0cd40000-0x0dffffff: exa
> offscreen) --> No freeze anymore.
>
> The 32MB was not a random choice: it matches the 32 MB classic texture
> buffer we had until beginning of April, which was sitting between exa
> offscreen and end of aperture. Dropping patch 118_drop_legacy3d.patch,
> which removed the (unused) classic texture buffer, also solves the
> freeze issue for me. So maybe that patch (dated 1 April) has been the
> trigger for this bug?
>
> Now the question is: Is something writing or reading beyond the end of
> the exa offscreen buffer? Without the 32 MB unused memory after the exa
> offscreen buffer, that would be beyond end of aperture. How can I find
> what is doing that?
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Jonathan Aquilina

[Albert Damen (albrt)]

> Now the question is: Is something writing or reading beyond the end of
> the exa offscreen buffer? Without the 32 MB unused memory after the exa
> offscreen buffer, that would be beyond end of aperture. How can I find
> what is doing that?

For further testing, I enabled DEBUG_MIGRATE in the xserver an run the repro script again.
After X froze, the last line logged was:
-> 0x5750ec0 (0xffe0a00) (1280x25) (c)

Assuming the size of the pixmap is 4 bpp x 1280 x 25, this pixmap ends at FFFFE00, which is pretty close to the end of the exa offscreen buffer.

Discussion with Jesse on ubuntu-x learned the gpu might read more then the pixmap size because of prefetching or because of tiling. Prefetching would do maximum one 4kB page. As my tests yesterday showed pushing back exa offscreen with 4 kB was not enough to prevent the freeze, tiling seems the most likely cause in this case. For the GM965 tiling would extend the object to a multiple of 512 width.

Attached is the patch I am currently testing; no freeze in > 2 hours.
However, could pixmaps get a height larger then VirtualY? My logs don't show any, but I think that would need further testing.

[Matthias Blaicher (blaicher)]

On Mon, May 18, 2009 at 11:26 AM, Jithin Emmanuel <email address hidden> wrote:
> Found best way to reproduce this bug. Visit this web page
>
> http://upload.wikimedia.org/wikipedia/commons/b/b7/Singapore_port_panorama.jpg
>
> Got from http://bugs.archlinux.org/task/14594

This has now been fixed, see
https://bugs.freedesktop.org/show_bug.cgi?id=20152#c32
Maybe it can be backported, as this crash really feels like the one
described in this bug here. I doubt it is the same one, but I guess
bug reports are beeing mixed...

[Jithin Emmanuel (jithin1987)]

fixed means where? how can i get the fix.

On Wed, May 20, 2009 at 6:38 PM, Matthias Blaicher
<email address hidden>wrote:

> On Mon, May 18, 2009 at 11:26 AM, Jithin Emmanuel <email address hidden>
> wrote:
> > Found best way to reproduce this bug. Visit this web page
> >
> >
> http://upload.wikimedia.org/wikipedia/commons/b/b7/Singapore_port_panorama.jpg
> >
> > Got from http://bugs.archlinux.org/task/14594
>
> This has now been fixed, see
> https://bugs.freedesktop.org/show_bug.cgi?id=20152#c32
> Maybe it can be backported, as this crash really feels like the one
> described in this bug here. I doubt it is the same one, but I guess
> bug reports are beeing mixed...
>
> ** Bug watch added: freedesktop.org Bugzilla #20152
> https://bugs.freedesktop.org/show_bug.cgi?id=20152
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Rodney Dangerfield<http://www.brainyquote.com/quotes/authors/r/rodney_dangerfield.html>
- "I worked in a pet store and people would ask how big I would get."

[Matthias Blaicher (blaicher)]

On Wed, May 20, 2009 at 5:05 PM, Jithin Emmanuel <email address hidden> wrote:
> fixed means where? how can i get the fix.

It should be included in the next build of the xorg-edgers PPA (
https://launchpad.net/~xorg-edgers ), but be aware that once you
installed this PPA it's quiet hard to get rid of it again... Please
read the warnings on the website.

I guess it would be wise to wait for the next release of the intel
driver and use the ubuntu-x-swat PPA
(https://launchpad.net/~ubuntu-x-swat )

So, enough bug spam....

[reini (rrumberger)]

I've been running this patch (patched version 2.6.3-0ubuntu9) for
more than 24h now and haven't experienced any freezes since.

On Wednesday 20 May 2009, Albert Damen wrote:
> Attached is the patch I am currently testing; no freeze in > 2
> hours. However, could pixmaps get a height larger then VirtualY?
> My logs don't show any, but I think that would need further
> testing.
>
> ** Attachment added: "debdiff (for testing only)"
> http://launchpadlibrarian.net/26953676/avoid-aperture.debdiff

[Zachary Waldowski (zwaldowski)]

Robert (if you're listening), the xserver-xorg-video-intel from Wed, 20 May 2009 13:16:00 -0400 doesn't seem to incorporate the patch or newest git... I still get the freeze in regular usage and especially upon visiting the Wikimedia image.

reini, Albert, would somebody be willing to send me a patched package for amd64?

[Zachary Waldowski (zwaldowski)]

Oh, sorry, I meant to clarify some more (immature hitting of "submit"). I'm using all the Xorg crack pushers packages, and I currently have kernel 2.6.30-rc6 from http://kernel.ubuntu.com/~kernel-ppa/mainline/

[reini (rrumberger)]

I don't have and amd64 system. You might want to use
https://wiki.ubuntu.com/UbuntuPackagingGuide/BuildFromDebdiff to
compile your own package. That's how I did it.

Am Donnerstag 21 Mai 2009 schrieb zwaldowski:
> reini, Albert, would somebody be willing to send me a patched
> package for amd64?

[Zachary Waldowski (zwaldowski)]

Well, I'll be damned! I built an amd64 package, and it works! No freezes, beautiful Compiz, all there! Here's hoping this patch and the newest patches from git will finally get us a clean fix released before Karmic is out.

On odd note, though: my now-standard test of looking at the Wikimedia picture above was passed, but Firefox blacks out the image as soon as it finishes downloading. I'm going to wget it right now and see if the system can display it normally, otherwise, we need to get this fix in as soon as possible.

[JP Fiset (jp-fiset)]

> On odd note, though: my now-standard test of looking at the Wikimedia picture above was passed,
> but Firefox blacks out the image as soon as it finishes downloading.

I see the same side effect.
- xserver-xorg-video-intel 2:2.7.1-0ubuntu1~xup~1
- Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
- UXA

[mlissner (mlissner-michaeljaylissner)]

So is it safe to say that if the singapore picture (above) doesn't freeze our system when we have compiz on, that we don't have this bug? That's my reading of it, but I haven't read all 500 comments.

[Bernhard (b.a.koenig)]

I never had any freezes at all but my whole system is just increadibly slow with compiz. Correct me if I'm wrong but this is not just about singapore-like freezes, it's about performance and memory leaks of intel video cards.

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno gio, 21/05/2009 alle 16.03 +0000, zwaldowski ha scritto:
>
> On odd note, though: my now-standard test of looking at the Wikimedia
> picture above was passed, but Firefox blacks out the image as soon as
> it
> finishes downloading. I'm going to wget it right now and see if the
> system can display it normally, otherwise, we need to get this fix in
> as
> soon as possible.

I have the freeze mentioned in this bug, but the image loaded properly
for me in firefox. Now it is black (bug in firefox?) but if I download
it I can see it. But different programs may use xlib in different ways,
so that means nothing.

--
It is also important to note that hedgehogs do not actually hurt each
other when they get close to one another. Actually, when living in
groups, hedgehogs often sleep close to each other.
http://en.wikipedia.org/wiki/Hedgehog%27s_dilemma

[Marius Gedminas (mgedmin)]

On Fri, May 22, 2009 at 06:04:59AM -0000, Bernhard wrote:
> I never had any freezes at all but my whole system is just increadibly
> slow with compiz. Correct me if I'm wrong but this is not just about
> singapore-like freezes, it's about performance and memory leaks of intel
> video cards.

*This* bug is about freezes on i965 with EXA.

Extreme Compiz slowness ought to be a different bug, though I cannot
give you a link right now.

BTW have you tried disabling vsync in compiz and in driconf? That
helped a lot for me (using EXA; I had no extreme slowness in UXA by
which I suspect vsync is broken with UXA).

Marius Gedminas
--
But perhaps ISO's central secretariat follows just the common industry
practice pioneered by Microsoft: "We will get it right in the third
release."
 -- Markus Kuhn on ISO 10646 PDF CD-ROM edition

[Oded Arbel (oded-geek)]

I just had another crash, when I started playing a video. After I restarted the same video would play fine, so I can't actually reproduce this (it was probably related to the better then week up time I had up until now).

My setup is:
- Thinkpad T61 with i965
- ubuntu-x-swat X server with Intel 2.7.1 driver
- AccelMethod EXA with Virtual 2048x2048, EXAOptimizationMigration set and heuristic set to "greedy".

[Gustavo Narea (gnarea)]

In addition to the freezes, I also experienced display corruptions as described in another bug report. All the problems are gone after using UXA, which works like a charm.

Not sure if it's really related or not, but I can also reproduce the bug with the Wikimedia picture above in Firefox, but not in Konqueror.

 * Dell XPS M1330n.
 * VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c).

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno ven, 22/05/2009 alle 02.01 +0000, mlissner ha scritto:
> So is it safe to say that if the singapore picture (above) doesn't
> freeze our system when we have compiz on, that we don't have this bug?
> That's my reading of it, but I haven't read all 500 comments.

No I don't think it is safe to say so because I had these freezes even
while seeing the picture in firefox (dunno why it doesn't work now).
However, I can't be sure I have the same freeze.

[reini (rrumberger)]

Neither the version in proposed (2.6.3-0ubuntu9.2) nor the one from x-swat (2.7.1-0ubuntu1~xup~1) actually fix this bug. I can reproduce it by simply deceasing CPU frequency as much as possible and starting up 4 glxgears. The freeze usually occurs within one minute.
With Albert Damen's patch, the version from jaunty-proposed ran for the whole night (>6hrs) under these conditions.

[Dave Conniff (chronniff)]

I saw there was some new stuff in the xorg crack pushers ppa, so I downgraded to jaunty native from the x-update repo, and the updated into the crack-pushers repo....On my first reboot I noticed that despite my xorg config that the new builds had me using UXA, not sure if that is intended or not, but perhaps a warning about it would be nice...With the updates some of the compiz stuff feels smoother, however I experienced a lockup on launching a video using mplayer's xv Intel(R) Video Overlay option, which had been fixing the horrible screen tearing I have been getting on every driver and kernel I have tested (which is all of them I think). The lock up involved giving me aandom green screen, and no control over anyting. I am currently running kernel 2.6.29.4 because it seems to be giving me the best video performance, Keep in mind that this is in UXA now, and I haven't experienced any hard lockups like this in UXA with any of the prior drivers, although there had been plenty of memory leaks which prevented me from using UXA as my deault......I realize this is a little off this bug topic, but it happend while attempting a fix for this bug so I thought I would mention it....Also it doesn't happen every time I open a video with that option, although the systems behavior becomes odd every time I do it.................Also even more of topic, pulseaudio has been acting like a psychotic abusive drunk stepfather every time I try to play media since I switched to 2.6.29.4, randomly taking 100% of my cpu, triggering the oom and filling up my swap and fun stuff like that, not sure if it is related, but certainly adds to the fun I have been having with jaunty!!! ( relax ubuntu devs, I don't blame you, I blame whoever decided to do a complete overhaul on the intel driver right before 2 of the biggest linux distro's (fedora and ubuntu) were coming out with there latest releases

[Oded Arbel (oded-geek)]

On Tue, 2009-05-26 at 16:09 +0000, Dave Conniff wrote:

> however I experienced a
> lockup on launching a video using mplayer's xv Intel(R) Video Overlay
> option, which had been fixing the horrible screen tearing I have been
> getting on every driver and kernel I have tested (which is all of them
> I
> think). The lock up involved giving me aandom green screen, and no
> control over anyting. I am currently running kernel 2.6.29.4 because
> it
> seems to be giving me the best video performance, Keep in mind that
> this
> is in UXA now, and I haven't experienced any hard lockups like this in
> UXA with any of the prior drivers, although there had been plenty of
> memory leaks which prevented me from using UXA as my deault......I
> realize this is a little off this bug topic, but it happend while
> attempting a fix for this bug so I thought I would mention it....Also
> it
> doesn't happen every time I open a video with that option, although
> the
> systems behavior becomes odd every time I do it

I'm having a similar problem on Fedora 11
(https://bugzilla.redhat.com/show_bug.cgi?id=499245) on GMA 945. Its not
100% the same problem (for example, xv works fine for me, its SDL that
freezes), but its more likely to be related to your problem this this
launchpad ticket.

The Fedora freeze also seems to be Intel driver related. I'm really not
pointing fingers anywhere and I got relatively very little flak on my
machines compared to other people on the list, but the Intel GMA driver
scenario is pretty horrible right now - I'm actually advising people not
to upgrade and to buy non-Intel graphics.

[Geir Ove Myhr (gomyhr)]

On Tue, May 26, 2009 at 12:09 PM, Dave Conniff wrote:
> I saw there was some new stuff in the xorg crack pushers ppa, so I
> downgraded to jaunty native from the x-update repo, and the updated into
> the crack-pushers repo....On my first reboot I noticed that despite my
> xorg config that the new builds had me using UXA, not sure if that is
> intended or not, but perhaps a warning about it would be nice...

There's a very noticable warning on the PPA page:
https://launchpad.net/~xorg-edgers/+archive/ppa
The XXA and EXA code has been deleted from the git master tree, so for
any drivers above the 2.7 branch, setting AccelMethod do not change
anything. Xorg-edgers is the latest development version after all.

[Alwin Garside (yogarine)]

On May 26, 2009 7:25 PM, "Geir Ove Myhr" <email address hidden> wrote:

On Tue, May 26, 2009 at 12:09 PM, Dave Conniff wrote: > I saw there was some
new stuff in the xorg ...
There's a very noticable warning on the PPA page:
https://launchpad.net/~xorg-edgers/+archive/ppa
The XXA and EXA code has been deleted from the git master tree, so for
any drivers above the 2.7 branch, setting AccelMethod do not change
anything. Xorg-edgers is the latest development version after all.

-- [i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392 You received this...

[Dave Conniff (chronniff)]

haha.....I see I spoke out of turn.....well, I told you that would be a good idea...I guess I have been to that page so much in the past that I didn't even bother reading over any of the warnings figuring that nothing has changed, anyway, to update my experience on the new xorg crack, I am actually still using them and have had very little trouble other than the video problem I explained before......by the way, I wasn't posting to complain, I do realize I am testing unstable untested drivers, I was actually posting just to let people following this bug know about the latest drivers, and the news is actually more promising with this release than in the past

[Jason Gullifer (jgull8502)]

I've been following this bug for a while, but not as closely in the past week or too.

I have a Dell m1330 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c). I've been holding off upgrading because of the intel bugs. I'm wondering if it's relatively safe to upgrade to 9.04 now. I don't mind doing some configuring but I'm wondering if there's a condensed list of things I can try if I experience this freezing.

[Jithin Emmanuel (jithin1987)]

You better not upgrade. Wait till stable drivers are available. It also
needs 2.6.30 kernel. And I believe that is never going to be available in
jaunty, So you better wait till karmic is released. Hope it will be fixed by
then.

On Thu, May 28, 2009 at 6:19 AM, Jgull8502 <email address hidden> wrote:

> I've been following this bug for a while, but not as closely in the past
> week or too.
>
> I have a Dell m1330 Intel Corporation Mobile GM965/GL960 Integrated
> Graphics Controller (rev 0c). I've been holding off upgrading because of
> the intel bugs. I'm wondering if it's relatively safe to upgrade to 9.04
> now. I don't mind doing some configuring but I'm wondering if there's a
> condensed list of things I can try if I experience this freezing.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel
http://spotm.in
Helen Rowland<http://www.brainyquote.com/quotes/authors/h/helen_rowland.html>
- "One man's folly is another man's wife."

[Gustavo Narea (gnarea)]

Jgull8502 said:
> I have a Dell m1330 Intel Corporation Mobile GM965/GL960 Integrated
> Graphics Controller (rev 0c). I've been holding off upgrading because of
> the intel bugs. I'm wondering if it's relatively safe to upgrade to 9.04
> now. I don't mind doing some configuring but I'm wondering if there's a
> condensed list of things I can try if I experience this freezing.

I have the same hardware and, as I reported here recently, this bug is solved
with UXA:
https://wiki.ubuntu.com/X/UxaTesting

UXA works perfectly here. Just add that line to you X config, reboot and enjoy
your Ubuntu install.

UXA fixes all the bugs of the previous driver: Display corruptions and X
freezes. Plus, it doesn't introduce _any_ bugs.

So, I'd really recommend it to you.
--
Gustavo Narea <xri://=Gustavo>.
| Tech blog: =Gustavo/(+blog)/tech ~ About me: =Gustavo/about |

[Marius Gedminas (mgedmin)]

On Thu, May 28, 2009 at 11:38:38AM -0000, Gustavo Narea wrote:
> Jgull8502 said:
> > I have a Dell m1330 Intel Corporation Mobile GM965/GL960 Integrated
> > Graphics Controller (rev 0c). I've been holding off upgrading because of
> > the intel bugs. I'm wondering if it's relatively safe to upgrade to 9.04
> > now. I don't mind doing some configuring but I'm wondering if there's a
> > condensed list of things I can try if I experience this freezing.
>
> I have the same hardware and, as I reported here recently, this bug is solved
> with UXA:
> https://wiki.ubuntu.com/X/UxaTesting
>
> UXA works perfectly here. Just add that line to you X config, reboot
> and enjoy your Ubuntu install.
>
> UXA fixes all the bugs of the previous driver: Display corruptions and X
> freezes. Plus, it doesn't introduce _any_ bugs.

Caveat emptor. When I tried UXA on Intel GM965 in Jaunty, I suffered
from two show-stopper bugs: (1) memory leak that would eat up all the
RAM within a day or two, causing all applications to be swapped out and
(2) X would crash on every suspend & resume, requiring me to log in
again and restart all the apps. Both bugs affected me with stock Jaunty
driver as well as xserver-xorg-video-intel 2.7.1 from the ubuntu-x-swat
PPA.

So, I wouldn't recommend UXA as the panacea.

Marius Gedminas
--
It is a mess, pure and simple. Sucks to be away from Unix, huh?
        -- man perlfaq3

[Thomas Foss (tafoxx)]

As was mentioned before, this bug does not exist in UXA... I wouldn't really
call it a "fix", it simply never arose in that code. But there are many
unrelated valid reasons why Ubuntu doesn't use UXA yet.

On Thu, May 28, 2009 at 3:35 PM, Marius Gedminas <email address hidden> wrote:

> On Thu, May 28, 2009 at 11:38:38AM -0000, Gustavo Narea wrote:
> > Jgull8502 said:
> > > I have a Dell m1330 Intel Corporation Mobile GM965/GL960 Integrated
> > > Graphics Controller (rev 0c). I've been holding off upgrading because
> of
> > > the intel bugs. I'm wondering if it's relatively safe to upgrade to
> 9.04
> > > now. I don't mind doing some configuring but I'm wondering if there's a
> > > condensed list of things I can try if I experience this freezing.
> >
> > I have the same hardware and, as I reported here recently, this bug is
> solved
> > with UXA:
> > https://wiki.ubuntu.com/X/UxaTesting
> >
> > UXA works perfectly here. Just add that line to you X config, reboot
> > and enjoy your Ubuntu install.
> >
> > UXA fixes all the bugs of the previous driver: Display corruptions and X
> > freezes. Plus, it doesn't introduce _any_ bugs.
>
> Caveat emptor. When I tried UXA on Intel GM965 in Jaunty, I suffered
> from two show-stopper bugs: (1) memory leak that would eat up all the
> RAM within a day or two, causing all applications to be swapped out and
> (2) X would crash on every suspend & resume, requiring me to log in
> again and restart all the apps. Both bugs affected me with stock Jaunty
> driver as well as xserver-xorg-video-intel 2.7.1 from the ubuntu-x-swat
> PPA.
>
> So, I wouldn't recommend UXA as the panacea.
>
> Marius Gedminas
> --
> It is a mess, pure and simple. Sucks to be away from Unix, huh?
> -- man perlfaq3
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once...

[Soeren Sonnenburg (bugreports-nn7)]

On Thu, 2009-05-28 at 13:35 +0000, Marius Gedminas wrote:
> On Thu, May 28, 2009 at 11:38:38AM -0000, Gustavo Narea wrote:
> > Jgull8502 said:
> > > I have a Dell m1330 Intel Corporation Mobile GM965/GL960 Integrated
> > > Graphics Controller (rev 0c). I've been holding off upgrading because of
> > > the intel bugs. I'm wondering if it's relatively safe to upgrade to 9.04
> > > now. I don't mind doing some configuring but I'm wondering if there's a
> > > condensed list of things I can try if I experience this freezing.
> >
> > I have the same hardware and, as I reported here recently, this bug is solved
> > with UXA:
> > https://wiki.ubuntu.com/X/UxaTesting
> >
> > UXA works perfectly here. Just add that line to you X config, reboot
> > and enjoy your Ubuntu install.
> >
> > UXA fixes all the bugs of the previous driver: Display corruptions and X
> > freezes. Plus, it doesn't introduce _any_ bugs.
>
> Caveat emptor. When I tried UXA on Intel GM965 in Jaunty, I suffered
> from two show-stopper bugs: (1) memory leak that would eat up all the
> RAM within a day or two, causing all applications to be swapped out and
> (2) X would crash on every suspend & resume, requiring me to log in
> again and restart all the apps. Both bugs affected me with stock Jaunty
> driver as well as xserver-xorg-video-intel 2.7.1 from the ubuntu-x-swat
> PPA.

I see the exact same problems with UXA too (and kernel 2.6.30-rc7 plus
the intel driver from git for that matter).

So I guess these should be reported upstream.

[Zachary Waldowski (zwaldowski)]

Problem is that it's already reported upstream.

[RedSocrates (redsocrates)]

Just to add my own input and a few other things:

I've done two of the things suggested here that appear to have solved this problem for me. I don't know if either of them alone would have done it, since I made both changes at once. Basically, I upped my "Virtual" size to 2048 2048, and I applied Albert Damen's debdiff patch. Prior to making these changes, I suffered from the same X freezes that others have described: no CTRL+ALT+F1 to switch to a TTY, no responsiveness in X to mouse clicks or keyboard input (except for ALT+SysRq+REISUB and ALT+SysRq+K, the latter of which killed at least part of the X session but left me with an unreadable screen), but ability to move the mouse pointer. I appear to suffer from no such problems now (so far, anyway, after hours of usage under the same conditions which typically would've caused the freezing by now). I can view the panorama image provided above, and so on.

Here's the relevant portion of 'lspci -vvnn' and 'apt-show-versions -a -p xserver-xorg-video-intel' (I've attached my xorg.conf for reference as well):

$ lspci -vvnn
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 03)
 Subsystem: Hewlett-Packard Company Device [103c:30d9]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 2301
 Region 0: Memory at 51000000 (64-bit, non-prefetchable) [size=1M]
 Region 2: Memory at 40000000 (64-bit, prefetchable) [size=256M]
 Region 4: I/O ports at 30d0 [size=8]
 Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
  Address: fee0300c Data: 4199
 Capabilities: [d0] Power Management version 3
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
  Bridge: PM- B3+
 Kernel modules: intelfb

$ apt-show-versions -a -p xserver-xorg-video-intel
xserver-xorg-video-intel 2:2.6.3-0ubuntu9aperture1 install ok installed
xserver-xorg-video-intel 2:2.6.3-0ubuntu9 jaunty us.archive.ubuntu.com
xserver-xorg-video-intel 2:2.6.3-0ubuntu9 jaunty archive.ubuntu.com
xserver-xorg-video-intel 2:2.6.3-0ubuntu9aperture1 newer than version in archive

Incidentally, I previously saw (and posted on) a bug apparently similar (if not identical to) this one at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355155

[Zachary Waldowski (zwaldowski)]

Is the kernel-side fix in 2.6.30? Can it be backported to 2.6.29 or even 2.6.28 (Jaunty kernel)? How about the actual fixes for X? Can they be backported?

[santorc (saxvodafome)]

I confirmed this bug on Ubuntu9.04 with the kernel 2.6.28-11.

-----Messaggio originale-----
Da: <email address hidden> per conto di zwaldowski
Inviato: mar 02/06/2009 23.12
A: <email address hidden>
Oggetto: [Bug 359392] Re: [i965] X freezes starting on April 3rd

Is the kernel-side fix in 2.6.30? Can it be backported to 2.6.29 or
even 2.6.28 (Jaunty kernel)? How about the actual fixes for X? Can
they be backported?

--
[i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392
You received this bug notification because you are a direct subscriber
of the bug.

Status in X.org xf86-video-intel: Confirmed
Status in "compiz" source package in Ubuntu: In Progress
Status in "xserver-xorg-video-intel" source package in Ubuntu: Fix Released
Status in compiz in Ubuntu Jaunty: Fix Committed
Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
Status in compiz in Ubuntu Karmic: In Progress
Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released

Bug description:
[Problem]
Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965 users started noticing X freeze after several hours of use, triggered by application usage especially noticeable with (but not unique to) compiz enabled.

[Impact]
The freeze bug affects a subset of i965 based systems, most particularly those using compiz. Exact numbers cannot be determined, but may be as high as 25-50% based on rough estimates.

The problem is severe: An unpredictable lockup of the system that requires a power cycle to recover from. For some users it comes on within minutes, while for others it comes after a few hours of use.

[How Addressed in Development Version]
For now, the patch being proposed for Jaunty has been uploaded to Karmic.

Longer term, we plan to move from EXA to UXA once the latter is stable enough. It has been found that while UXA exhibits other kinds of freezes, we've not yet been able to reproduce this particular freeze there.

[Patch for Jaunty]
A low-risk workaround that has proven effective at eliminating freezes, or at least greatly reducing their frequency, is to increase the Virtual framebuffer size. Some users do this locally as a matter of course to gain dual-head support, so this setting has received extremely widespread testing already.

The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it is not otherwise specified. Users can still override this with their own settings, larger or smaller, as desired.

A side effect of this patch is that it also mitigates bug 158415 to a degree, which will make projector usage somewhat easier for this hardware because it will enable X to recognize higher resolutions available from the external monitor than were available on initial boot.

[Test Case]
The best method found to reproduce the bug is:
  a. Enable compiz
  b. Set your desktop to a 6x1 workspace layout
  c. Run http://launchpadlibrarian.net/25683477/repro.sh
  d. System will freeze anywhere from 1-20 min typically
  e. Power-button shutdown is required to reset the system

[Regression Potential]
In general, Virtual has been widely and extensively tested, so we do not expect this patch to trigger r...

[Bryce Harrington (bryce)]

On Wed, Jun 03, 2009 at 03:18:25PM -0000, santorc wrote:
> I confirmed this bug on Ubuntu9.04 with the kernel 2.6.28-11.

Thanks but we need no further confirmations of this bug on 2.6.28.
Please upgrade to karmic and see if the issue still exists there.

[Bernhard (b.a.koenig)]

@Bryce: I think most people here don't want to upgrade to an alpha karmic. There should be more documentation on how jaunty users can get the "supposedly better" karmic packages. I also understand zwaldowski's question like that, pls provide more info on what are the "supposedly patched" packages and how to install them on jaunty.

[José Tomás Atria (jtatria)]

+1 at Bernhard. I have been following this bug closely, and i read the
whole 300+ comments, but i got lost in regards as to which packages
are affected, and what versions should introduce fixes, apart from the
backported xserver-xorg-video-intel mentioned above.

@Bryce: could you give us a little more info on he current status of
the bug, to further help isolating the issue and the affected
packages?

thanks!

On Wed, Jun 3, 2009 at 11:51 AM, Bernhard <email address hidden> wrote:
> @Bryce: I think most people here don't want to upgrade to an alpha
> karmic. There should be more documentation on how jaunty users can get
> the "supposedly better" karmic packages. I also understand zwaldowski's
> question like that, pls provide more info on what are the "supposedly
> patched" packages and how to install them on jaunty.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
entia non sunt multiplicanda praeter necessitatem

[Zachary Waldowski (zwaldowski)]

How is this supposedly fixed in Karmic again. As per Bryce's above recommendation, I spend a chunk of my day today upgrading to Karmic. Same problem all over again, except it's almost as bad as stock Jaunty now. Freezes within five minutes of boot. Xorg-Edgers and new kernels now have no effect, now on Jaunty nor Karmic.

[Bernhard (b.a.koenig)]

AFAIK, this bug cannot be fully fixed until Intel fixes the problems in their new drivers, the introduction of http://en.wikipedia.org/wiki/Graphics_Execution_Manager seems to have failed badly.

So it's confusing to say that it's fixed in karmic. Maybe this should simply be changed.

[Soeren Sonnenburg (bugreports-nn7)]

On Thu, 2009-06-04 at 08:56 +0000, Bernhard wrote:
> AFAIK, this bug cannot be fully fixed until Intel fixes the problems in
> their new drivers, the introduction of
> http://en.wikipedia.org/wiki/Graphics_Execution_Manager seems to have
> failed badly.
>
> So it's confusing to say that it's fixed in karmic. Maybe this should
> simply be changed.

Well, as long as these bugs are not fixed

https://bugs.freedesktop.org/show_bug.cgi?id=20766
https://bugs.freedesktop.org/show_bug.cgi?id=19731
https://bugs.freedesktop.org/show_bug.cgi?id=20893

I wouldn't say there is any distribution that helps you here...

Soeren

[ichudov (igor-chudov)]

When people say "Linux is not ready for desktop", this is what they mean.

[Thomas Foss (tafoxx)]

You can say that again...

On Thu, Jun 4, 2009 at 3:17 PM, ichudov <email address hidden> wrote:

> When people say "Linux is not ready for desktop", this is what they
> mean.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The best method found to reproduce the bug is:
> a. Enable compiz
> b. Set your desktop to a 6x1 workspace layout
> c. Run http://launchpadlibrarian.net/25683477/repro.sh
> d. System will freeze anywhere from 1-20 min typically
> e. Power-button shutdown is required to reset the system
>
> [Regression Potential]
> In general, Virtual has been widely and extensively tested, so we do not
> expect this patch to trigger regressions.
>
> The patch is coded to only take effect on i965 systems, so the scope of any
> regression that might conceivably be triggered ...

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno gio, 04/06/2009 alle 13.17 +0000, ichudov ha scritto:
> When people say "Linux is not ready for desktop", this is what they
> mean.
>

As a 12-years old (as a linux user) linux user, I have to say it's true.
I hoped for a long time that Ubuntu would have been different.

In this case, putting the old driver back in the distribution and
starting to chose the right driver based on user's feedback until the
too many intel issues are solved, would be mandatory.

@Bryce, it's easy to put back the old driver in the distribution, and if
there is not enough manpower to create the whitelist, I would chose the
old one as a default. May I ask you "why not"?

The old driver is already "available" in jaunty in a PPA; but the point
here is to provide a system that works out of the box. I recall
everybody that current intel driver is also extremely slow unless you
tweak Xorg.conf. Which is not something we expect from the ordinary
_ubuntu_ user.

It was already unacceptable to have jaunty ship broken. But if in karmic
issues are not solved, please, please, rethink the decision of using the
new driver. It's just too early. If intel sees that no one wants their
new puppie, they'll start improving it.

Vincenzo

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno gio, 04/06/2009 alle 20.00 +0200, Vincenzo Ciancia ha scritto:
>
>
> In this case, putting the old driver back in the distribution and
> starting to chose the right driver based on user's feedback until the
> too many intel issues are solved, would be mandatory.
>
> @Bryce, it's easy to put back the old driver in the distribution, and
> if
> there is not enough manpower to create the whitelist, I would chose
> the
> old one as a default. May I ask you "why not"?
>

A piece is missing here "the whitelist" would be created based on user
feedback to enable the new driver only for those combinations where it
actually works. I said "works" without any attributes :)

V.

[Thomas Foss (tafoxx)]

How would one reinstall the old driver? I didn't think it was an option.
Heck, I'd downgrade back to Intrepid if I there was a way to do it. There
should be a "downgrade" button that's as big and shiny as the Jaunty upgrade
button was.
(Or maybe the upgrade buttons could just have little warning labels on the
side... like cigarettes do.)

On Thu, Jun 4, 2009 at 8:08 PM, Vincenzo Ciancia <email address hidden>wrote:

> Il giorno gio, 04/06/2009 alle 20.00 +0200, Vincenzo Ciancia ha scritto:
> >
> >
> > In this case, putting the old driver back in the distribution and
> > starting to chose the right driver based on user's feedback until the
> > too many intel issues are solved, would be mandatory.
> >
> > @Bryce, it's easy to put back the old driver in the distribution, and
> > if
> > there is not enough manpower to create the whitelist, I would chose
> > the
> > old one as a default. May I ask you "why not"?
> >
>
> A piece is missing here "the whitelist" would be created based on user
> feedback to enable the new driver only for those combinations where it
> actually works. I said "works" without any attributes :)
>
> V.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specif...

[ichudov (igor-chudov)]

On Thu, Jun 04, 2009 at 06:00:37PM -0000, Vincenzo Ciancia wrote:
> Il giorno gio, 04/06/2009 alle 13.17 +0000, ichudov ha scritto:
> > When people say "Linux is not ready for desktop", this is what they
> > mean.
> >
>
> As a 12-years old (as a linux user) linux user, I have to say it's true.
> I hoped for a long time that Ubuntu would have been different.

I am a "14 years old" Linux user, I used it as my primary OS since
1995, when I bought my first own PC I put Linux on it.

And I have to say that there are many projects in GNU/Linux that have a
great history of very careful, thoughtful software development, such
as editors, binutils, gcc, apache, perl etc. These have self tests,
etc and go through a very rigorous development process, so I never
hesitate to trust them with my business. They find bugs automatically
and fix discovered bugs.

However, I think that any sort of a project that "does not fix bugs"
may lose trust, and has a limited future, and I am greatly hoping that
Ubuntu would not take that route.

We cannot really recommend to people to "switch to pre-alpha Karmic",
either.

I do realize that 1) GUI stuff is not as amenable to automatic testing
and 2) Ubuntu is trying to do this on a shoestring budget, so the
situation is understandable, but in some ways it is unfortunate.

I am a 100% Ubuntu user, this is what I use at home and what we have
at work, so this is not meant to be jeering from sidelines. But I do
feel that I have a deep interest in seeing my platform remain a
reliable, trusted friend.

Personally, on the balance of "wanting new cool stuff" versus "wanting
to have reliable software", I tend to be skewed for the latter.

> In this case, putting the old driver back in the distribution and
> starting to chose the right driver based on user's feedback until the
> too many intel issues are solved, would be mandatory.

I tend to agree with you.

i

[reini (rrumberger)]

Am Donnerstag 04 Juni 2009 schrieb ichudov:
> On Thu, Jun 04, 2009 at 06:00:37PM -0000, Vincenzo Ciancia wrote:
> > In this case, putting the old driver back in the distribution
> > and starting to chose the right driver based on user's feedback
> > until the too many intel issues are solved, would be mandatory.
>
> I tend to agree with you.

I'd like to point out that I tried the old (i.e. intrepid) driver
version (don't remember where I found it - it was somewhere in the
ubuntu wiki AFAIR). It didn't change the freezing problem at all
(made it worse if anything).

So switching back to the old driver isn't really a very helpful
suggestion...

  --reini

[Thomas Foss (tafoxx)]

On Thu, Jun 4, 2009 at 9:59 PM, reini <email address hidden> wrote:

> Am Donnerstag 04 Juni 2009 schrieb ichudov:
> > On Thu, Jun 04, 2009 at 06:00:37PM -0000, Vincenzo Ciancia wrote:
> > > In this case, putting the old driver back in the distribution
> > > and starting to chose the right driver based on user's feedback
> > > until the too many intel issues are solved, would be mandatory.
> >
> > I tend to agree with you.
>
> I'd like to point out that I tried the old (i.e. intrepid) driver
> version (don't remember where I found it - it was somewhere in the
> ubuntu wiki AFAIR). It didn't change the freezing problem at all
> (made it worse if anything).
>
> So switching back to the old driver isn't really a very helpful
> suggestion...
>
> --reini

That's very odd... the problem definitely wasn't around in Intrepid, at
least for me.

[Noel J. Bergman (noeljb)]

> We cannot really recommend to people to "switch to pre-alpha Karmic",
> either.

I agree, for most users. But then again MOST users should not be running Jaunty. They should be running either Hardy or at most Intrepid. WHAT, you say, but Jaunty is the latest and best and released! So what? We users ARE the testers, and until a number of months of defect fixing follow release, the average user should be staying far from the leading edge. At present, with a 6 months release cycle, users should probably be considering moving to a release around the time its successor is released. Or staying with an LTS, and upgrading when the successor's .1 comes out.

Personally, I try to use the latest code as much as possible, since we ARE the testers, but I also have 4 different releases installed at all times. So I have options when something is broken.

If you are going to attempt to stay on the edge, you are just plain foolish if you are not using a multi-boot environment.

[reini (rrumberger)]

Am Donnerstag 04 Juni 2009 schrieb Thomas Foss:
> On Thu, Jun 4, 2009 at 9:59 PM, reini <email address hidden> wrote:
> > I'd like to point out that I tried the old (i.e. intrepid)
> > driver version (don't remember where I found it - it was
> > somewhere in the ubuntu wiki AFAIR). It didn't change the
> > freezing problem at all (made it worse if anything).
> >
> > So switching back to the old driver isn't really a very helpful
> > suggestion...
> >
>
> That's very odd... the problem definitely wasn't around in
> Intrepid, at least for me.

Same here. It would seem that the bug was already present but not
provoked, I guess.
Anyway, since Albert posted his patch, all my problems with the
freezing issue have gone away, so I'm not switching to
Karmic/whatever until I know that there's a patch that will work on
that platform.
And Intrepid had a few other issues that I don't want to worry about
again.

[David Nemeskey (nemeskeyd)]

Very similar bugs were present even in Hardy, such as https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/233896. I remember someone uploading X & intel packages from the never released DRI2 stuff (or sth like that) to the bug, which worked, but I don't know if they were the versions that made it into Intrepid. The thing is, to be completely on the safe side, maybe the driver for Gutsy should be considered. Which is kind of unthinkable...

[Laurent Claessens (moky-math)]

At present, with a 6 months release
> cycle, users should probably be considering moving to a release around
> the time its successor is released. Or staying with an LTS, and
> upgrading when the successor's .1 comes out.
>

By the way, this is what most of people do with Windows. Even more :
most of Windows users just stay with their OS until buying a new computer.

If we want to look in a "very end-user" perspective, a computer is only
supposed to work with the OS it was shipped with. Dell sold me a
computer which is supposed to work with Hardy, and it does work with
hardy. The fact to install a Jaunty *is not* an end-user behavior. The
first line of the GPL is very clear on that point ;)

Laurent

[reini (rrumberger)]

I guess from your post that your Hardy and Intrepid were bug-free?
Because mine sure weren't...

The most annoying bugs I experienced had this nice little phrase
somewhere near the bottom of the bug-thread. I went something like
that: "Please upgrade to intrepid to see if the the issue still
exists there." (jaunty, for those that existed in Intrepid).
Kinda like Bryce's response to santorc a few posts up...

Now, you tell me what to do when you experience *major*
inconveniences (e.g. network connection being dropped all the time
and no way to properly restore it - that was fixed by an upgrade to
jaunty, BTW; or this screen freezing issue) and being stonewalled
with the above suggestion...

[David Nemeskey (nemeskeyd)]

Noel: sorry, but I think this is BS. Ubuntu doesn't call it's newest version "unstable" or "testing", which would tell the user that it's not safe yet; quite the opposite in fact, if you read the homepage ("you'll always have the latest and greatest applications that the open source world has to offer", etc). So, it would be unrealistic not to expect users to download and try to use new one! When KDE did that with 4.0, they were booed upon by everyone; and rightfully so.

Also, there is a difference between one or two applications not working, or the whole system (from the user's point of view, X IS the system) freezing every 10 minutes. The first could be acceptable, following your rationale; the second, not.

[José Tomás Atria (jtatria)]

IMHO, please stop with all the discussion about what should have been
done, or if linux is ready for the desktop and whatnot.

We have a stable release that is recommended as stable to users. ALL users.

this stable release has a known problem with intel drivers, the
problem was reported as a bug and is being worked on. This is the
proper way to address the issue.

When a workaround is found, it should be recommended to all users, or
if it entails a regression, it should be pushed into the update path
as a temporary fix (unitl now, i haven't found the problem again with
the updated intel drivers in the jaunty backports).

"upgrade to karmic alpha" is not a viable workaround for users, so
please, recommend what to do to avoid this problem within jaunty,
while the bug is solved.

Has anyone bothered to thoroughly check which update produced the
error for the first time?

--
entia non sunt multiplicanda praeter necessitatem

[Zachary Waldowski (zwaldowski)]

I still maintain that the version available in Jaunty Proposed has not fixed my problems, nor has the Intrepid version. In fact, I still get the freezing problem after I spent two hours upgrading to Karmic the other night.

To those who defend the existence of this bug by saying we "normal users" should've all stayed on Intrepid, I find this statement insulting and incredibly unfriendly. If Ubuntu really intended for users to stay a release behind, then there wouldn't be a gigantic shiny UPGRADE button every time users check for updates. Nor would Ubuntu.com have "9.04 is out - UPGRADE NOW." Nor would UbuntuForums.org close the Intrepid-based support forums.

[José Tomás Atria (jtatria)]

is there any way to check the upgrade path to determine what else was
updated on april 3rd?

Because we are certain that the clean vanilla jaunty install doesn't
have this issue, right?

right?

On Thu, Jun 4, 2009 at 5:21 PM, zwaldowski <email address hidden> wrote:
> I still maintain that the version available in Jaunty Proposed has not
> fixed my problems, nor has the Intrepid version.  In fact, I still get
> the freezing problem after I spent two hours upgrading to Karmic the
> other night.
>
> To those who defend the existence of this bug by saying we "normal
> users" should've all stayed on Intrepid, I find this statement insulting
> and incredibly unfriendly.  If Ubuntu really intended for users to stay
> a release behind, then there wouldn't be a gigantic shiny UPGRADE button
> every time users check for updates.  Nor would Ubuntu.com have "9.04 is
> out - UPGRADE NOW."  Nor would UbuntuForums.org close the Intrepid-based
> support forums.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
entia non sunt multiplicanda praeter necessitatem

[Geir Ove Myhr (gomyhr)]

@José Tomás: Clean vanilla jaunty has this issue. It was released on
April 23rd. The development version before April 3rd did not have this
issue. It should be possible to get an alpha version from before this
date, but I don't think the in-between packages are readily available.

@zwaldowski: I don't think you qualify as a "normal user". You seem to
be far to technically apt for that. While it is pretty hard to get
bugs in Jaunty fixed now (the upstream developers aren't terribly
interested in fixing "old" stuff, the SRU process is cumbersome but
necessary to avoid breaking new things in a stable release), this is a
great time to get bugs fixed in Karmic. This is not a recommended
workaround for "normal users", but it is the way technically
knowledgable users like yourself can help make sure the problems are
addressed before the next version. If you file a new bug report
(preferably with the ubuntu-bug command) using Karmic, that will
definitely help. Karmic also has better tools for debugging freezes
like this.

[reini (rrumberger)]

Am Donnerstag 04 Juni 2009 schrieb José Tomás Atria:
> is there any way to check the upgrade path to determine what else
> was updated on april 3rd?
>
> Because we are certain that the clean vanilla jaunty install
> doesn't have this issue, right?
>
> right?

The live CD has the issue, therefore so does "clean vanilla" jaunty.

[Steve Langasek (vorlon)]

No Ubuntu developers are saying that users who want stable systems should have stayed with intrepid, nor that users who want a fixed system should upgrade to the karmic alpha. However, Launchpad Bugs is not a discussion forum, it is a tool for developers and users to communicate in order to *get bugs fixed*. If you're not prepared to help with this process by testing (including, if it comes down to it, testing with karmic alpha packages), that's ok, but then please refrain from commenting on this bug so that the communication channel can be kept clear for those who *are* in a position to help get this bug fixed.

As it stands, with 548 comments this bug log is already pretty much useless for tracking the actual freeze bug in question. One factor here appears to be that there are a number of different freezes happening, each with a different cause, but it's very difficult to distinguish between them because of the nature of the symptom in question.

Some of these freezes are fixed for people using the intel driver from jaunty-proposed; others require kernel changes which are still in the process of being prepared for jaunty; others are still present even in karmic. To be able to make sense of these bugs, we really need everyone to do the following:

1. File a separate bug report for your issue, and post the bug number here. If you already filed your own bug and it was marked as a duplicate of this one, then you don't need to do this again; but please send your follow-up comments to your individual bug report, so that as we begin to distinguish between these multiple freeze bugs, your comments stay with the right bug.
2. Follow the directions at https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-freeze-test/ to capture the information needed to diagnose your freeze, and send it to the bug report. Note that you will need to be able to ssh in from another machine in order to capture this information, so be sure you have openssh-server installed before trying to reproduce the bug!
3. If the freeze is not reproducible for you after upgrading to the 2.6.30-rc5 kernel needed for capturing the debugging information, please note that in the bug as well.
4. For *each subsequent freeze on your machine*, repeat step 2. This ensures that we don't mistakenly end up trying to debug two separate kinds of freezes on a single machine without realizing it.

Your cooperation here will go a long way towards helping us break this confused bug down into manageable chunks.

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno gio, 04/06/2009 alle 20.29 +0000, Noel J. Bergman ha scritto:
> But then again MOST users should not be
> running Jaunty. They should be running either Hardy or at most
> Intrepid.

Ubuntu was born from debian for the two purposes of having a predictable
release cycle and high usability. Ubuntu never endorsed using old
releases; instead, fixes for non-LTS and non current releases are
usually not done unless they are security fixes. In other words, using
past releases is unsupported and not adviced by ubuntu. What you are
describing above is debian.

Vincenzo

[Bernhard (b.a.koenig)]

Of course Ubuntu recommends using jaunty. But the main issue here is
the Intel driver, so you cannot purely blame Ubuntu for this
particular problem. So it may be better to continue this discussion on
the freedesktop forum or send complaint mails to Intel?

I don't want to annoy Intel devs (since we really depend on them now
more than ever), but I wouldn't be surprised if they said: "Hey, we
have this new GEM idea, let's first test it with Linux kernels before
we use it on commercial software."

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno gio, 04/06/2009 alle 18.48 +0000, Thomas Foss ha scritto:
> How would one reinstall the old driver? I didn't think it was an
> option.
> Heck, I'd downgrade back to Intrepid if I there was a way to do it.
> There
> should be a "downgrade" button that's as big and shiny as the Jaunty
> upgrade
> button was.
> (Or maybe the upgrade buttons could just have little warning labels on
> the
> side... like cigarettes do.)
>

It's easy; here is the link, it worked well for me even though compiz is
a bit slower (but I am using EXA and not UXA with the old driver because
it is not strictly necessary to use the latter).

https://wiki.ubuntu.com/ReinhardTartler/X/RevertingIntelDriverTo2.4

Check the Xorg logs before and after doing it to be sure that the driver
version changed (when the intel driver is loaded a string containing
"intel" and the version is shown in /var/log/Xorg.0.log, can't be more
precise because I am using another machine now).

Vincenzo

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno gio, 04/06/2009 alle 19.59 +0000, reini ha scritto:
>
>
> I'd like to point out that I tried the old (i.e. intrepid) driver
> version (don't remember where I found it - it was somewhere in the
> ubuntu wiki AFAIR). It didn't change the freezing problem at all
> (made it worse if anything).
>
> So switching back to the old driver isn't really a very helpful
> suggestion...
>

But to clarify: does plain intrepid work for you? I think there are at
least two different deadlockers in jaunty. I know this because I have a
machine with an ATI and with the intel centrino chipset. It deadlocked a
lot. Upgrading to the karmic kernel fixed this. OTOH, I have a machine
with an intel video card. Downgrading the video driver fixed that. So
are you sure you are experiencing the same bug?

V.

[Vincenzo Ciancia (vincenzo-ml)]

Il giorno gio, 04/06/2009 alle 21.01 +0000, José Tomás Atria ha scritto:
> IMHO, please stop with all the discussion about what should have been
> done, or if linux is ready for the desktop and whatnot.
>
> We have a stable release that is recommended as stable to users. ALL
> users.
>
> this stable release has a known problem with intel drivers, the
> problem was reported as a bug and is being worked on. This is the
> proper way to address the issue.
>

This stable release has been consciously released broken - forget the
deadlock, also extreme slowness with compiz was known since jaunty alpha
1, much earlier than the 3rd of April. The driver should not have landed
beta and should be removed from stable, that's what I am saying.

Of course since I am not an authority I think it is good to ask Bryce
who actually is an authority in Xorg/ubuntu. Maybe there are very good
reasons why we don't want the old driver in ubuntu.

V.

[reini (rrumberger)]

Am Freitag 05 Juni 2009 schrieb Vincenzo Ciancia:
> But to clarify: does plain intrepid work for you?

Yes.

> I think there
> are at least two different deadlockers in jaunty. I know this
> because I have a machine with an ATI and with the intel centrino
> chipset. It deadlocked a lot. Upgrading to the karmic kernel fixed
> this. OTOH, I have a machine with an intel video card. Downgrading
> the video driver fixed that. So are you sure you are experiencing
> the same bug?

I experience two bugs:
a) this one (where the mouse is still responsive after freeze)
b) another one (where, after the freeze, the mouse doesn't react
   anymore, either)

a) seems hasn't occured for me with the current driver since I
   applied Albert's patch. It occurred quite frequently after I
   downgraded to 2.4 (using the same link you provided above).
b) never really had a chance of occurring before I applied Albert's
   patch (since it seems quite rare) and only occurred once since.

(I will file separate reports for these bugs as soon as I get around
to it.)

[Mario (diraimondo)]

reini wrote:
> I experience two bugs:
> a) this one (where the mouse is still responsive after freeze)
> b) another one (where, after the freeze, the mouse doesn't react
> anymore, either)
>
> a) seems hasn't occured for me with the current driver since I
> applied Albert's patch. It occurred quite frequently after I
> downgraded to 2.4 (using the same link you provided above).
> b) never really had a chance of occurring before I applied Albert's
> patch (since it seems quite rare) and only occurred once since.

I can say that I have the same situation on my GM45: I used to have both
the kinds of freeze (with/without a live mouse pointer). I'm actually
using the jaunty-proposed package (2:2.6.3-0ubuntu9.2) with the personal
addition of the Albert's patch. I can say that the system is more stable
without any freeze of type A (with live mouse pointer). Sometime I have
freeze of type B: I'm able to reboot with SysReq sequences.

Mario

[Laurent Claessens (moky-math)]

I created a new bug (that has to be understood as a wishlist). I propose a solution to avoid new cases of critical regressions that could impact poor end-users who end up with an useless computer.

https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/384039

[Laurent Claessens (moky-math)]

In fact, there is already an idea in the Brainstorm database :
http://brainstorm.ubuntu.com/idea/17218/

I think that implementing it could prevent, for the future, problems like the one we are facing now.

[Martin Pitt (pitti)]

Hello all,

many thanks to Albert Damen for his comprehensive analysis. The cited
kernel patches are only for UXA and don't backport well, so we won't
backport them to Jaunty (at least not now). However, his aperture
patch already got good feedback and seems to fix the problem in a much
better way than the previous VirtualSize workaround which is currently
sitting in -proposed.

Can people who are affected by this and who run a standard
configuration (i. e. NO UXA, NO KMS, NO 2.6.30 kernel, etc.) please
enable this PPA and test the updated -intel driver there?

  https://launchpad.net/~bryceharrington/+archive/green

Please report positive and negative feedback about this package here.
(Please no further feedback about "I also have this problem", or
problems with UXA).

Thank you!

Martin

[Bernhard (b.a.koenig)]

I tested with both compiz and metacity and with many audio and video
streams simulanteously and it seems to me that this last archive green
package has seriously improved my experience, especially in that there
is no more audio and video stuttering. I never had freezes though, so
I cannot say anything about that.

[Thomas Foss (tafoxx)]

Quick question... does these freezes only happen when Compiz is enabled? I
think I have this bug (because I've got a 965GM chipset and Compiz is
disabled), but I've never had any freezes. Should I be re-enabling Compiz to
see if this patch fixes the problem, or will it remove the Compiz blacklist
automatically?

On Sat, Jun 6, 2009 at 2:55 PM, Bernhard <email address hidden> wrote:

> I tested with both compiz and metacity and with many audio and video
> streams simulanteously and it seems to me that this last archive green
> package has seriously improved my experience, especially in that there
> is no more audio and video stuttering. I never had freezes though, so
> I cannot say anything about that.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The best method found to re...

[Zachary Waldowski (zwaldowski)]

The bug has happened both ways, usually faster if one has Compiz. If you enable the proposed repo, you'll upgrade to a Compiz that doesn't have the X3100 on the blacklist. Be careful, though, as a new kernel somehow didn't get into proposed and you'll only be able to do a partial upgrade

Martin, in what capacity I've been able to test it (I'm "addicted" Xorg-edgers, but I tested a manual compile of it), the patch works beautifully.

[reini (rrumberger)]

Am Samstag 06 Juni 2009 schrieb Martin Pitt:
> Can people who are affected by this and who run a standard
> configuration (i. e. NO UXA, NO KMS, NO 2.6.30 kernel, etc.)
> please enable this PPA and test the updated -intel driver there?
>
> https://launchpad.net/~bryceharrington/+archive/green
>
> Please report positive and negative feedback about this package
> here. (Please no further feedback about "I also have this
> problem", or problems with UXA).

The package in the above repository is considered "older" than the
current version from proposed (which doesn't incorporate Albert
Damen's patch). It might be difficult for some to select the "older"
package for installation. It would be nice if somebody would somehow
bump the version or something to make the package from the above
repository the preferred package when running "apt-get upgrade".

[Bernhard (b.a.koenig)]

@Thomas Foss: I never had any freezes myself, even with compiz. But I
had enourmous problems with my video card when switching between
workspaces with many windows open, many audio streams, many flash
videos running. Try and check if you feel a difference using the new
patch. You can try using both compiz and metacity and give us your
impression.

[Bernhard (b.a.koenig)]

Yes, please. It's just an annoyance but I have the same issue as reini.

[Martin Pitt (pitti)]

Thomas Foss [2009-06-06 13:18 -0000]:
> Quick question... does these freezes only happen when Compiz is enabled? I
> think I have this bug (because I've got a 965GM chipset and Compiz is
> disabled), but I've never had any freezes. Should I be re-enabling Compiz to
> see if this patch fixes the problem, or will it remove the Compiz blacklist
> automatically?

It mostly occurs with compiz. You might also be able to reproduce it
with other 3D applications, though.

Please note that the compiz package in jaunty-proposed removed the
blacklisting of 965, so you should test both together.

[Thomas Foss (tafoxx)]

Alright, I'll give it a shot.

--Thomas

On Sat, Jun 6, 2009 at 4:56 PM, Martin Pitt <email address hidden> wrote:

> Thomas Foss [2009-06-06 13:18 -0000]:
> > Quick question... does these freezes only happen when Compiz is enabled?
> I
> > think I have this bug (because I've got a 965GM chipset and Compiz is
> > disabled), but I've never had any freezes. Should I be re-enabling Compiz
> to
> > see if this patch fixes the problem, or will it remove the Compiz
> blacklist
> > automatically?
>
> It mostly occurs with compiz. You might also be able to reproduce it
> with other 3D applications, though.
>
> Please note that the compiz package in jaunty-proposed removed the
> blacklisting of 965, so you should test both together.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The bes...

[Thomas Foss (tafoxx)]

Graphics are really smooth. Window borders have gone all wonky... not
glitching, just... different. And I can't seem to change them back.
http://dl.getdropbox.com/u/455435/LiveJournal//Metacity.png
http://dl.getdropbox.com/u/455435/LiveJournal/Compiz.png
(The "Metacity" screenshot is what the window borders used to look like all
the time, and still look like in Metacity.)

I also can't seem to grab the cube with the middle mouse button anymore...
Somehow I remember being able to rotate the cube with Ctrl+Alt+Button1 or
also with the middle mouse button... but I only see one "initiate" shortcut
setting, so I don't know how to get it back to doing both. Hmm.

Overall though I think these are small problems for which I just need to
find the right settings. I haven't seen any problems with the graphics so
far. Are there any specific tests I should do to try to provoke it?

--Thomas

On Sat, Jun 6, 2009 at 5:23 PM, Thomas <email address hidden> wrote:

> Alright, I'll give it a shot.
>
> --Thomas
>
>
> On Sat, Jun 6, 2009 at 4:56 PM, Martin Pitt <email address hidden>wrote:
>
>> Thomas Foss [2009-06-06 13:18 -0000]:
>> > Quick question... does these freezes only happen when Compiz is enabled?
>> I
>> > think I have this bug (because I've got a 965GM chipset and Compiz is
>> > disabled), but I've never had any freezes. Should I be re-enabling
>> Compiz to
>> > see if this patch fixes the problem, or will it remove the Compiz
>> blacklist
>> > automatically?
>>
>> It mostly occurs with compiz. You might also be able to reproduce it
>> with other 3D applications, though.
>>
>> Please note that the compiz package in jaunty-proposed removed the
>> blacklisting of 965, so you should test both together.
>>
>> --
>> [i965] X freezes starting on April 3rd
>> https://bugs.launchpad.net/bugs/359392
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in X.org xf86-video-intel: Confirmed
>> Status in “compiz” source package in Ubuntu: In Progress
>> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix
>> Released
>> Status in compiz in Ubuntu Jaunty: Fix Committed
>> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
>> Status in compiz in Ubuntu Karmic: In Progress
>> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>>
>> Bug description:
>> [Problem]
>> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
>> users started noticing X freeze after several hours of use, triggered by
>> application usage especially noticeable with (but not unique to) compiz
>> enabled.
>>
>> [Impact]
>> The freeze bug affects a subset of i965 based systems, most particularly
>> those using compiz. Exact numbers cannot be determined, but may be as high
>> as 25-50% based on rough estimates.
>>
>> The problem is severe: An unpredictable lockup of the system that
>> requires a power cycle to recover from. For some users it comes on within
>> minutes, while for others it comes after a few hours of use.
>>
>> [How Addressed in Development Version]
>> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>>
>> Longer term, we plan to move from EXA to U...

[Thomas Foss (tafoxx)]

When in full-screen mode in Firefox (F11), the entire screen "blinks"
whenever the little alt-text window (or whatever it's called) pops up. It's
very annoying. I think it's more of a Compiz problem than a graphics problem
in general... but it didn't do this before. Perhaps a fresh install of
Compiz will settle it down...

--Thomas

On Sat, Jun 6, 2009 at 5:51 PM, Thomas <email address hidden> wrote:

> Graphics are really smooth. Window borders have gone all wonky... not
> glitching, just... different. And I can't seem to change them back.
> http://dl.getdropbox.com/u/455435/LiveJournal//Metacity.png
> http://dl.getdropbox.com/u/455435/LiveJournal/Compiz.png
> (The "Metacity" screenshot is what the window borders used to look like all
> the time, and still look like in Metacity.)
>
> I also can't seem to grab the cube with the middle mouse button anymore...
> Somehow I remember being able to rotate the cube with Ctrl+Alt+Button1 or
> also with the middle mouse button... but I only see one "initiate" shortcut
> setting, so I don't know how to get it back to doing both. Hmm.
>
> Overall though I think these are small problems for which I just need to
> find the right settings. I haven't seen any problems with the graphics so
> far. Are there any specific tests I should do to try to provoke it?
>
> --Thomas
>
>
> On Sat, Jun 6, 2009 at 5:23 PM, Thomas <email address hidden> wrote:
>
>> Alright, I'll give it a shot.
>>
>> --Thomas
>>
>>
>> On Sat, Jun 6, 2009 at 4:56 PM, Martin Pitt <email address hidden>wrote:
>>
>>> Thomas Foss [2009-06-06 13:18 -0000]:
>>> > Quick question... does these freezes only happen when Compiz is
>>> enabled? I
>>> > think I have this bug (because I've got a 965GM chipset and Compiz is
>>> > disabled), but I've never had any freezes. Should I be re-enabling
>>> Compiz to
>>> > see if this patch fixes the problem, or will it remove the Compiz
>>> blacklist
>>> > automatically?
>>>
>>> It mostly occurs with compiz. You might also be able to reproduce it
>>> with other 3D applications, though.
>>>
>>> Please note that the compiz package in jaunty-proposed removed the
>>> blacklisting of 965, so you should test both together.
>>>
>>> --
>>> [i965] X freezes starting on April 3rd
>>> https://bugs.launchpad.net/bugs/359392
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>> Status in X.org xf86-video-intel: Confirmed
>>> Status in “compiz” source package in Ubuntu: In Progress
>>> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix
>>> Released
>>> Status in compiz in Ubuntu Jaunty: Fix Committed
>>> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
>>> Status in compiz in Ubuntu Karmic: In Progress
>>> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>>>
>>> Bug description:
>>> [Problem]
>>> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
>>> users started noticing X freeze after several hours of use, triggered by
>>> application usage especially noticeable with (but not unique to) compiz
>>> enabled.
>>>
>>> [Impact]
>>> The freeze bug affects a subset of i965 based systems, most particularly
>>> those using co...

[Tom Jaeger (thjaeger)]

This is going to happen if you "unredirect" fullscreen windows (System
-> Preferences -> CompizConfig Settings Manager -> General Options ->
General -> Unredirect Fullscreen Windows).

Thomas Foss wrote:
> When in full-screen mode in Firefox (F11), the entire screen "blinks"
> whenever the little alt-text window (or whatever it's called) pops up. It's
> very annoying. I think it's more of a Compiz problem than a graphics problem
> in general... but it didn't do this before. Perhaps a fresh install of
> Compiz will settle it down...
>
> --Thomas

[Jithin Emmanuel (jithin1987)]

I downgraded all my packages from xswat and xorg edgers to ones from
jaunty and installed this package.
One thing to notice is that its affected performance considerably
things are a lot slower and kde 4.2 is pretty mch useless without UXA
because of screen corrupting problem( Well I dont think any one is
going to care about this part).

On Sun, Jun 7, 2009 at 4:51 AM, Tom Jaeger<email address hidden> wrote:
> This is going to happen if you "unredirect" fullscreen windows (System
> -> Preferences -> CompizConfig Settings Manager -> General Options ->
> General -> Unredirect Fullscreen Windows).
>
> Thomas Foss wrote:
>> When in full-screen mode in Firefox (F11), the entire screen "blinks"
>> whenever the little alt-text window (or whatever it's called) pops up. It's
>> very annoying. I think it's more of a Compiz problem than a graphics problem
>> in general... but it didn't do this before. Perhaps a fresh install of
>> Compiz will settle it down...
>>
>> --Thomas
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel

[reini (rrumberger)]

I haven't had this kind of freeze in several hours now. I have,
however, experienced another freeze where the screen just froze and
nothing reacted anymore (no mouse movement, nothing).

I believe this to be a different bug and will report it separately as
soon as I get around to it.

For now, this should count as positive feedback for the patch in the
green repository.

Am Samstag 06 Juni 2009 schrieb Martin Pitt:
> Hello all,
>
> many thanks to Albert Damen for his comprehensive analysis. The
> cited kernel patches are only for UXA and don't backport well, so
> we won't backport them to Jaunty (at least not now). However, his
> aperture patch already got good feedback and seems to fix the
> problem in a much better way than the previous VirtualSize
> workaround which is currently sitting in -proposed.
>
> Can people who are affected by this and who run a standard
> configuration (i. e. NO UXA, NO KMS, NO 2.6.30 kernel, etc.)
> please enable this PPA and test the updated -intel driver there?
>
> https://launchpad.net/~bryceharrington/+archive/green
>
> Please report positive and negative feedback about this package
> here. (Please no further feedback about "I also have this
> problem", or problems with UXA).

[Thomas Foss (tafoxx)]

On Sun, Jun 7, 2009 at 1:21 AM, Tom Jaeger <email address hidden> wrote:

> This is going to happen if you "unredirect" fullscreen windows (System
> -> Preferences -> CompizConfig Settings Manager -> General Options ->
> General -> Unredirect Fullscreen Windows).

That fixed it... although I don't understand what it did, or why it never
did that before. :P Now if I could just get my window borders back...

>
> Thomas Foss wrote:
> > When in full-screen mode in Firefox (F11), the entire screen "blinks"
> > whenever the little alt-text window (or whatever it's called) pops up.
> It's
> > very annoying. I think it's more of a Compiz problem than a graphics
> problem
> > in general... but it didn't do this before. Perhaps a fresh install of
> > Compiz will settle it down...
> >
> > --Thomas
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: In Progress
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Committed
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Confirmed
> Status in compiz in Ubuntu Karmic: In Progress
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor...

[Oded Arbel (oded-geek)]

On Sat, 2009-06-06 at 12:15 +0000, Martin Pitt wrote:
> many thanks to Albert Damen for his comprehensive analysis. The cited
> kernel patches are only for UXA and don't backport well, so we won't
> backport them to Jaunty (at least not now). However, his aperture
> patch already got good feedback and seems to fix the problem in a much
> better way than the previous VirtualSize workaround which is currently
> sitting in -proposed.
>
> Can people who are affected by this and who run a standard
> configuration (i. e. NO UXA, NO KMS, NO 2.6.30 kernel, etc.) please
> enable this PPA and test the updated -intel driver there?
>
> https://launchpad.net/~bryceharrington/+archive/green
>
> Please report positive and negative feedback about this package here.
> (Please no further feedback about "I also have this problem", or
> problems with UXA).

After a couple of freezes with the x-swat's team drivers, I've reset
everything to current jaunty and installed the above drivers. Currently
I'm back in compiz and no freeze for the last day, and performance isn't
bad either (nothing earth shuttering, but glxgears at 850FPS is a bit
better then what I'm used to from Intel GMA).

[Joachim Nilsson (troglobit)]

On Sat, Jun 06, 2009 at 11:21:07PM -0000, Tom Jaeger wrote:
> Thomas Foss wrote:
> > When in full-screen mode in Firefox (F11), the entire screen "blinks"
> > whenever the little alt-text window (or whatever it's called) pops up. It's
> > very annoying. I think it's more of a Compiz problem than a graphics problem
> > in general... but it didn't do this before. Perhaps a fresh install of
> > Compiz will settle it down...
> This is going to happen if you "unredirect" fullscreen windows (System
> -> Preferences -> CompizConfig Settings Manager -> General Options ->
> General -> Unredirect Fullscreen Windows).

Wow, thanks! I'd also been looking for the root cause of this problem
for quite some time! :-)

Regards
 /Jocke

--
Joachim Nilsson :: http://member.fsf.org/join/
FSF Member #654 :: Join the Free Software Foundation!

[David Nemeskey (nemeskeyd)]

Installed the "green" driver yesterday, and had not freezes since then. However, the performance is abyssmal. glxgears reports 1000 fps, 700 w/ Compiz, kwin seems to be able to get the maximum, though. X.org sometimes uses as much as 70% of the cpu, and the system definitely feels like it: video lagging, mouse cursor jumping in SDL applications, etc. I know that the i965 is not the best for playing Crysis, but it should be able to handle videos and basic compositioning.

Also, as reported before, the KDE 4 screen corruption issue is there.

[Bernhard (b.a.koenig)]

The glxgears seem to have no significance at all, I usually had a more
responsive Desktop when the glxgears performance was "worse".

On Sun, Jun 7, 2009 at 12:04 PM, David Nemeskey<email address hidden> wrote:
> Installed the "green" driver yesterday, and had not freezes since then.
> However, the performance is abyssmal. glxgears reports 1000 fps, 700 w/
> Compiz, kwin seems to be able to get the maximum, though. X.org
> sometimes uses as much as 70% of the cpu, and the system definitely
> feels like it: video lagging, mouse cursor jumping in SDL applications,
> etc. I know that the i965 is not the best for playing Crysis, but it
> should be able to handle videos and basic compositioning.
>
> Also, as reported before, the KDE 4 screen corruption issue is there.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[David Nemeskey (nemeskeyd)]

True, but the other problems I mentioned are still there...

Also, I am sorry to report that I had another freeze with the "green" driver. I had set the MigrationHeuristics to greedy before (this morning), that may have something to do with it? There was no change in the performance, though.

[reini (rrumberger)]

Am Sonntag 07 Juni 2009 schrieb David Nemeskey:
> Also, I am sorry to report that I had another freeze with the
> "green" driver. I had set the MigrationHeuristics to greedy before
> (this morning), that may have something to do with it? There was
> no change in the performance, though.

There are several freezes in the intel driver - could you describe
this one in a little more detail? Was the mouse responsive?

[David Nemeskey (nemeskeyd)]

> There are several freezes in the intel driver - could you describe
> this one in a little more detail? Was the mouse responsive?

Yes, sorry, it was the that one. I am using KDE as KWin runs much smoother than compiz. The freeze happened when I started a video in Kaffeine. I could move the mouse, but that was it. The music from the video played for a few seconds until it stopped. Had to go with SysRq + reisub; SysRq + k didn't work.

[Fernando Miguel (fernandomiguel)]

Olá Tom e a todos.

On Sunday 07 June 2009 00:21:07 Tom Jaeger wrote:
> This is going to happen if you "unredirect" fullscreen windows (System
> -> Preferences -> CompizConfig Settings Manager -> General Options ->
> General -> Unredirect Fullscreen Windows).

Thanks. that fixed my prob with apps in fullscreen flashing evertime a NotifyOSD came up.

--
Hi, I'm BUGabundo, and I am Ubuntu (whyubuntu.com)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net && Ubuntu LoCoTeam Portugal http://ubuntu-pt.org
Linux user #443786 GPG key 1024D/A1784EBB

[Martin Pitt (pitti)]

Accepted xserver-xorg-video-intel into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Bernhard (b.a.koenig)]

Thanks a lot Martin, does this new proposed package include Bryce's
recent patch to bug 314928 as well?

On Sun, Jun 7, 2009 at 9:06 PM, Martin Pitt<email address hidden> wrote:
> Accepted xserver-xorg-video-intel into jaunty-proposed, the package will
> build now and be available in a few hours. Please test and give feedback
> here. See https://wiki.ubuntu.com/Testing/EnableProposed for
> documentation how to enable and use -proposed. Thank you in advance!
>
> ** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
>       Status: Confirmed => Fix Committed
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jithin Emmanuel (jithin1987)]

Is there any solution with UXA. My system is super slow and KDE 4 is useless without it because of screen corruption bug.

[Dave Neary (dneary)]

I'm also seeing this problem - X freezes, but the mouse pointer is unaffected, but all keyboard & clicks do nothing. A power cycle is needed, restarting X doesn't work, although I can do it "properly" by rebooting after sshing in.

[Zachary Waldowski (zwaldowski)]

While we're waiting for the new fix to hit the proposed repo, or if it doesn't work for you from the green PPA, I'm able to report that the latest packages from xorg-edgers totally and completely fix the freezes. If you're beyond desperate, the new Fedora 11 does as well.

[Jithin Emmanuel (jithin1987)]

@zwaldowski Are you sure fedora 11 fixes this completely. Do they use UXA?

On Wed, Jun 10, 2009 at 1:56 AM, zwaldowski<email address hidden> wrote:
> While we're waiting for the new fix to hit the proposed repo, or if it
> doesn't work for you from the green PPA, I'm able to report that the
> latest packages from xorg-edgers totally and completely fix the freezes.
> If you're beyond desperate, the new Fedora 11 does as well.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel

[Zachary Waldowski (zwaldowski)]

Jithin, I'm pretty sure it's fixed over there. I ran the 64-bit GNOME Live CD from my USB key today for nearly an hour. I did many of the things that usually reproduce the freeze, including large images in Firefox, and switching back and forth between Compiz workspaces with glxgears and Totem open. A quick cat|grep of the Xorg log shows that they indeed use UXA, and I believe it's 2.6.30, so they must be using the most recent packages baked in with 2.7.1. That delay helped them somewhat, no? Of course, that's really not helpful to me considering I hate RPM's/YUM with a passion... DEB's/DPKG is my hero.

[Zachary Waldowski (zwaldowski)]

Perhaps I spoke too soon... I've just got about five freezes in rapid succession with Xorg-Edgers on 2.6.30. Would somebody be nice enough to comment when the "Green"-PPA Intel package comes into proposed? It took a week for the 2.6.28-13 packages to propogate to Proposed, even with the depending metapackages already pushed out, so I was thinking it's probably not up yet.

[Mike.lifeguard (mikelifeguard)]

@zwaldowski:

Yes, same here. There was an update to xorg-intel stuff yesterday - I'm reasonably sure that's the cause. Prior to that, no problems. After that, freezes (though perfect performance until such a freeze). FWIW, I'm using 2.6.30-020630rc8-generic.

[reini (rrumberger)]

Am Mittwoch 10 Juni 2009 schrieb zwaldowski:
> Would somebody be
> nice enough to comment when the "Green"-PPA Intel package comes
> into proposed? It took a week for the 2.6.28-13 packages to
> propogate to Proposed, even with the depending metapackages
> already pushed out, so I was thinking it's probably not up yet.

It was there way before the new kernel (at least I have it already).

[Mike.lifeguard (mikelifeguard)]

I'm reasonbly certain that this is the update I referred to above: https://launchpad.net/~xorg-edgers/+archive/ppa/+sourcepub/647509/+listing-archive-extra

[Zachary Waldowski (zwaldowski)]

Yeah, Mike, I got freezes under that and the previous -intel build.

I just got the freshly-compiled 2.6.30 final from the "kernel-ppa" that's not actually a PPA, and I still get freezes. Rapid-fire ones, shockingly. Just like stock Jaunty.

Reini, are you sure? I use the main US servers and still have whatever version uses the VirtualSize fix (I can't recall the version number off the top of my head, I'm in the hated OS right now)

[reini (rrumberger)]

Am Mittwoch 10 Juni 2009 schrieb zwaldowski:
> Reini, are you sure? I use the main US servers and still have
> whatever version uses the VirtualSize fix (I can't recall the
> version number off the top of my head, I'm in the hated OS right
> now)

Yes, I'm surprisingly sure, considering I had to manually allow
aptitude to upgrade that package as I had locked the previous
version. Also, the version 9.2 packages aren't available anymore.

also:

reini@localhost> dpkg -l |grep xserver-xorg-video-intel
ii xserver-xorg-video-intel 2:2.6.3-0ubuntu9.3

I'm using the german mirrors & the archive.ubuntu.com ones.

[reini (rrumberger)]

Am Mittwoch 10 Juni 2009 schrieb zwaldowski:
> Reini, are you sure? I use the main US servers and still have
> whatever version uses the VirtualSize fix (I can't recall the
> version number off the top of my head, I'm in the hated OS right
> now)

Yes, I'm surprisingly sure, considering I had to manually allow
aptitude to upgrade that package as I had locked the previous
version. Also, the version 9.2 packages aren't available anymore.

also:

reini@localhost> dpkg -l |grep xserver-xorg-video-intel
ii xserver-xorg-video-intel 2:2.6.3-0ubuntu9.3

I'm using the german mirrors & the archive.ubuntu.com ones.

[Zachary Waldowski (zwaldowski)]

Well, hot damn! Let me get that installed right now...

Jithin, before you do anything drastic, I just found out the hard way that Fedora IS NOT FIXED. And they don't even have Magic SysRq's enabled! Good thing I wasn't in the middle of installing it...

[Jithin Emmanuel (jithin1987)]

Thanks zwaldowski I was planing to install it today. So every one has
the problem. Too bad fedora had it from f 10 onwards.
I am planning to give kernel 30 and xorg-edgers ppa a try. People
please continue posting their experience here so that we can lock on a
working combination for all.

On Thu, Jun 11, 2009 at 4:43 AM, zwaldowski<email address hidden> wrote:
> Well, hot damn!  Let me get that installed right now...
>
> Jithin, before you do anything drastic, I just found out the hard way
> that Fedora IS NOT FIXED.  And they don't even have Magic SysRq's
> enabled!  Good thing I wasn't in the middle of installing it...
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards
Jithin Emmanuel

[Jithin Emmanuel (jithin1987)]

On Thursday 11 Jun 2009 4:43:06 am zwaldowski wrote:
> Well, hot damn! Let me get that installed right now...
>
> Jithin, before you do anything drastic, I just found out the hard way
> that Fedora IS NOT FIXED. And they don't even have Magic SysRq's
> enabled! Good thing I wasn't in the middle of installing it...
kernel 2.6.30 + packages from xorg-edgers is working for me. So far no freeze
and everything is pretty stable. Suspend and hibernation is also working,
though desktop effects are getting disabled after that.
--
Thanks
Jithin Emmanuel

[Martin Pitt (pitti)]

Hello Bernhard,

Bernhard [2009-06-07 19:27 -0000]:
> Thanks a lot Martin, does this new proposed package include Bryce's
> recent patch to bug 314928 as well?

No, not yet. Let's test that separately.

[Zachary Waldowski (zwaldowski)]

It seems that I'm now in a weird situation. I'm on 2.6.28-13 (Jaunty proposed) kernel with the latest unstable bits from xorg-edgers. I haven't froze yet, and can load the Singapore image above with a little system slowdown. However, with the same Xorg bits on the 2.6.30-8 given out _on_ the Xorg-Edgers repo, I get the freeze. Now downloading the final 2.6.30 from our so-called Kernel PPA (not on Launchpad) to check further.

[Maurizio (mauriziosilverii)]

My situation:
Jaunty 32 bit with proposed update
xserver-xorg-video-intel 2:2:6:3-0ubuntu9.3
kernel 2.6.28-13-generic

I enable Compiz and i open the Singapore image into Firefox without system crash.
For me the bug is resolved.

[Soeren Sonnenburg (bugreports-nn7)]

On Thu, 2009-06-11 at 07:05 +0000, Jithin Emmanuel wrote:
> On Thursday 11 Jun 2009 4:43:06 am zwaldowski wrote:
> > Well, hot damn! Let me get that installed right now...
> >
> > Jithin, before you do anything drastic, I just found out the hard way
> > that Fedora IS NOT FIXED. And they don't even have Magic SysRq's
> > enabled! Good thing I wasn't in the middle of installing it...
> kernel 2.6.30 + packages from xorg-edgers is working for me. So far no freeze
> and everything is pretty stable. Suspend and hibernation is also working,
> though desktop effects are getting disabled after that.

Not here, almost always hang on resume from suspend and still random
(but rare) lockups with mouse still active.

[Jithin Emmanuel (jithin1987)]

I think the situation is improving and hope that by the time intel 2.8
driver is released everything is fixed. Except for these minor issues
I am almost happy with the current situation.

On Sun, Jun 14, 2009 at 5:38 PM, Soeren Sonnenburg<email address hidden> wrote:
> On Thu, 2009-06-11 at 07:05 +0000, Jithin Emmanuel wrote:
>> On Thursday 11 Jun 2009 4:43:06 am zwaldowski wrote:
>> > Well, hot damn!  Let me get that installed right now...
>> >
>> > Jithin, before you do anything drastic, I just found out the hard way
>> > that Fedora IS NOT FIXED.  And they don't even have Magic SysRq's
>> > enabled!  Good thing I wasn't in the middle of installing it...
>> kernel 2.6.30 + packages from xorg-edgers is working for me. So far no freeze
>> and everything is pretty stable. Suspend and hibernation is also working,
>> though desktop effects are getting disabled after that.
>
> Not here, almost always hang on resume from suspend and still random
> (but rare) lockups with mouse still active.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Thanks
Jithin Emmanuel

W. C. Fields - "If I had to live my life over, I'd live over a
saloon." - http://www.brainyquote.com/quotes/authors/w/w_c_fields.html

[Mike.lifeguard (mikelifeguard)]

If you're no longer experiencing freezes, and you're using xorg-edgers stuff, please let us know /specifically/ which version of xserver-xorg-video-intel you're running.

[Jeff Fortin Tam (kiddo)]

> If you're no longer experiencing freezes, and you're using xorg-edgers
> stuff, please let us know /specifically/ which version of
> xserver-xorg-
> video-intel you're running.

Not sure if I need to reply directly to this thread about this, but here
goes: I am using xserver-xorg-video-intel 2.7.99.901
+git20090611.6d062e9e-0ubuntu0sarvatt~jaunty

You may have noticed that this is not the latest version. The reason is
simple: I just pinned/locked my packages to prevent upgrading, fearing
that things would break (I did not have a single problem with this
driver and the version before, been using that for a few weeks or so
since I switched to jaunty).

Thus, since I'm not running the latest one, I somewhat doubt my
testimonial will be relevant, but here goes, in the hope it is useful. I
am using a Dellbuntu Inspiron 530n, which has this 3100 gpu:

00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
Integrated Graphics Controller (rev 02), Dell Device 020d

[Mike.lifeguard (mikelifeguard)]

Yes, I asked specifically because there is a(nother) regression in the latest stuff from xorg-edgers, so I was going to try everything from today and downgrade working backwards[1] until I found something that worked. But I'll give 2.7.99.901
+git20090611.6d062e9e-0ubuntu0sarvatt~jaunty a try first.

[1] http://ubuntuforums.org/showthread.php?p=7457024#post7457024

[Sebastian Geiger (lanoxx)]

I have been running with a kernel from the kernel-ppa 2.6.30
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30/
and the intel driver 2.7.1 from X updates
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
and compiz reenabled for three days now without a freeze.
I am on amd64.

Best Regards
Lanoxx

[Jithin Emmanuel (jithin1987)]

On Monday 15 Jun 2009 2:17:54 am Mike.lifeguard wrote:
> If you're no longer experiencing freezes, and you're using xorg-edgers
> stuff, please let us know /specifically/ which version of xserver-xorg-
> video-intel you're running.
I am using
xserver-xorg-video-intel
2:2.7.99.901+git20090611.6d062e9e-0ubuntu0sarvatt~jaunty

libdrm2 - 2.4.11+git20090519.f355ad89-0ubuntu0sarvatt~jaunty

xserver-xorg-core
2:1.6.1.901+git20090523+server-1.6-branch.5cd5a012-0ubuntu0sarvatt2

and kernel 2..6.30
--
Thanks
Jithin Emmanuel

[Oded Arbel (oded-geek)]

I have a regression in Karmic: after living with the "green" drivers for a couple of week and everything was fine, I upgraded to Karmic on Thursday and ever since I had multiple freezes. I don't know if this is related to this bug, but I'll assume that it is unless someone tell me otherwise:

I got only one freeze while working, and it looks exactly the same as this problem: the screen freezes but the mouse still responds and I can ssh into the machine. But most of the freezes where while the laptop was on power with the lid closed, which means the screen is actually off and when I open it several hours later nothing responds - the computer is still on but the screen is disabled and nothing I do brings it back. I haven't yet tried to ssh into the laptop when its like that as usually I need to do something right away and I have to power cycle it.

Anyway, going through syslog I found this which might be related:
Jun 20 15:17:57 sepiroth kernel: [ 9960.560081] INFO: task events/1:10 blocked for more than 120 seconds.
Jun 20 15:17:57 sepiroth kernel: [ 9960.560088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 20 15:17:57 sepiroth kernel: [ 9960.560095] events/1 D 0000000100213a35 0 10 2
Jun 20 15:17:57 sepiroth kernel: [ 9960.560108] ffff88007d3c9db0 0000000000000046 0000000000000000 0000000000013000
Jun 20 15:17:57 sepiroth kernel: [ 9960.560119] ffff88007d3c03a8 0000000000013000 0000000000013000 0000000000013000
Jun 20 15:17:57 sepiroth kernel: [ 9960.560128] 0000000000013000 0000000000013000 ffff88007d3c03a8 0000000000013000
Jun 20 15:17:57 sepiroth kernel: [ 9960.560138] Call Trace:
Jun 20 15:17:57 sepiroth kernel: [ 9960.560157] [<ffffffff806d9467>] __mutex_lock_slowpath+0xd7/0x160
Jun 20 15:17:57 sepiroth kernel: [ 9960.560170] [<ffffffff802436b1>] ? finish_task_switch+0x51/0x110
Jun 20 15:17:57 sepiroth kernel: [ 9960.560179] [<ffffffff806d9186>] mutex_lock+0x26/0x50
Jun 20 15:17:57 sepiroth kernel: [ 9960.560215] [<ffffffffa0132ec8>] i915_gem_retire_work_handler+0x38/0x90 [i915]
Jun 20 15:17:57 sepiroth kernel: [ 9960.560238] [<ffffffffa0132e90>] ? i915_gem_retire_work_handler+0x0/0x90 [i915]
Jun 20 15:17:57 sepiroth kernel: [ 9960.560248] [<ffffffff802643d5>] run_workqueue+0x95/0x170
Jun 20 15:17:57 sepiroth kernel: [ 9960.560256] [<ffffffff80264554>] worker_thread+0xa4/0x120
Jun 20 15:17:57 sepiroth kernel: [ 9960.560266] [<ffffffff80268e90>] ? autoremove_wake_function+0x0/0x40
Jun 20 15:17:57 sepiroth kernel: [ 9960.560274] [<ffffffff802644b0>] ? worker_thread+0x0/0x120
Jun 20 15:17:57 sepiroth kernel: [ 9960.560282] [<ffffffff80268a35>] kthread+0x55/0xa0
Jun 20 15:17:57 sepiroth kernel: [ 9960.560290] [<ffffffff802130ca>] child_rip+0xa/0x20
Jun 20 15:17:57 sepiroth kernel: [ 9960.560299] [<ffffffff802689e0>] ? kthread+0x0/0xa0
Jun 20 15:17:57 sepiroth kernel: [ 9960.560306] [<ffffffff802130c0>] ? child_rip+0x0/0x20

There are several copies of these over a period of about 20 minutes, each almost exactly 2 minutes after another (as can probably be deduced from the error message) before it falls silent again - I can't tell for sure whether its related to the freeze, exce...

[Jorge G (geojorg)]

I can confirm the same issue of Obed Arbel, when I close the lid i get the freezes, I don't get the freeze by doing hard work on the laptop or using compiz, I am using the lastest intel driver available. I will try to ssh to the machine next time to get some information.

[Jithin Emmanuel (jithin1987)]

I have the same issue when X freezes on laptop lid close. Problem is X is in
a infinite loop. I raised a bug upstream

https://bugs.freedesktop.org/show_bug.cgi?id=22383

On Sun, Jun 21, 2009 at 12:09 AM, Jorge G <email address hidden> wrote:

> I can confirm the same issue of Obed Arbel, when I close the lid i get
> the freezes, I don't get the freeze by doing hard work on the laptop or
> using compiz, I am using the lastest intel driver available. I will try
> to ssh to the machine next time to get some information.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Thanks
Jithin Emmanuel

Fran Lebowitz<http://www.brainyquote.com/quotes/authors/f/fran_lebowitz.html>
- "Life is something to do when you can't get to sleep."

[Oded Arbel (oded-geek)]

I got the same freeze again (with laptop screen closed) but without the syslog messages, so its probably not related.

My problem is not an immediate lockup like it seems that Jithin Emmanuel reported (though I haven't looked at the Xorg log yet) - if I just close the lid and leave it for a few minutes and open it again then its usually still ok. For me the freeze happens when I have the screen closed for a long time - several hours.

[Jithin Emmanuel (jithin1987)]

Oded For me the lock up in instantaneously. So we might be having different
issues. I am using packages from xorg-edgers PPA.
And for me also there is no messages in syslog its only in Xorg log

On Sun, Jun 21, 2009 at 12:24 PM, Oded Arbel <email address hidden> wrote:

> I got the same freeze again (with laptop screen closed) but without the
> syslog messages, so its probably not related.
>
> My problem is not an immediate lockup like it seems that Jithin Emmanuel
> reported (though I haven't looked at the Xorg log yet) - if I just close
> the lid and leave it for a few minutes and open it again then its
> usually still ok. For me the freeze happens when I have the screen
> closed for a long time - several hours.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Thanks
Jithin Emmanuel

Henny Youngman<http://www.brainyquote.com/quotes/authors/h/henny_youngman.html>
- "I told the doctor I broke my leg in two places. He told me to quit
going
to those places."

[Sebastian Geiger (lanoxx)]

I just wanted to give an update about my configuration sofar:

Uptime:
 18:58:44 up 8 days, 17:09, 5 users, load average: 0.45, 0.59, 0.71

With Kernel 2.6.30 from the kernel-ppa/mainline and intel driver 2.7.1
from x-update I have been running stable and without any issues. I have
reactived normal compiz compositing by removing compiz from the
blacklisting and activating it in the apperance menu. Also
suspend/resume works well, even a little quicker than before and with
less errors on resume.

Regards
Lanoxx

[Botond Szász (boteeka)]

I also experience this problem not only when the lid is closed but after the screen goes blank when my laptop is idle for about half an hour. It also happened once when the screensaver was active and moved the mouse to bring the screen alive, and it stopped responding, the screen went black and I had to powercycle to get control again.

I'm using the 2.6.30 kernel from kernel-ppa/mainline and intel driver 2.7.99.901 on Jaunty.

[Mike.lifeguard (mikelifeguard)]

My freezes also occur when the laptop is idle for a long time, though I don't close the lid or suspend the computer: Screensaver -> screen off (but never suspend/hibernate)...

So it certainly looks to me as though these freezes are different.

[Bernhard (b.a.koenig)]

For people having a freeze after recovery from screensaver, please refer to bug 328760.

[Martin Pitt (pitti)]

Is there anyone who could give some feedback about a Jaunty standard
configuration/kernel with the jaunty-proposed -intel driver? We need
to get some verification to get this into jaunty-updates.

I would kindly ask people to stop reporting problems with 2.6.30/UXA
here. The bug trail is long enough as it is, and problems with
2.6.30/UXA belong in separate bug reports. Thank you!

[reini (rrumberger)]

Am Montag 22 Juni 2009 schrieb Martin Pitt:
> Is there anyone who could give some feedback about a Jaunty
> standard configuration/kernel with the jaunty-proposed -intel
> driver?

Sure can. No freezes since I installed it, and I installed it as soon
as it hit the proposed repos +- a couple of hours.

[Mario (diraimondo)]

reini wrote:
> Am Montag 22 Juni 2009 schrieb Martin Pitt:
>> Is there anyone who could give some feedback about a Jaunty
>> standard configuration/kernel with the jaunty-proposed -intel
>> driver?
>
> Sure can. No freezes since I installed it, and I installed it as soon
> as it hit the proposed repos +- a couple of hours.

With driver in ubuntu-proposed I have had no more freeze (the kind with
the only the mouse pointer working) but I had other kind of freeze. I've
upgraded the kernel to 2.6.30 and I don't have freezes since one week.

My solution: kernel 2.6.30 + intel drivers in jaunty-proposed.

Mario

[Launchpad Janitor (janitor)]

This bug was fixed in the package xserver-xorg-video-intel - 2:2.6.3-0ubuntu9.3

---------------
xserver-xorg-video-intel (2:2.6.3-0ubuntu9.3) jaunty-proposed; urgency=low

  * Add patch 121_reserve-unused-memory-at-end-of-aperture.patch. This
    reserves a block of unused memory between the exa offscreen buffer and
    end of aperture, to prevent freeze with EXA on GM965 cards
    (LP: #359392).

 -- Bryce Harrington <email address hidden> Sun, 07 Jun 2009 11:34:02 -0700

[Launchpad Janitor (janitor)]

This bug was fixed in the package compiz - 1:0.8.2-0ubuntu8.1

---------------
compiz (1:0.8.2-0ubuntu8.1) jaunty-proposed; urgency=low

  * debian/patches/028_compiz_manager_blacklist: Revert change from
    1:0.8.2-0ubuntu8 to un-blacklist GM965 (8086:2a02) again. We now have a
    better workaround in the -intel driver. (LP: #359392)

 -- Martin Pitt <email address hidden> Thu, 30 Apr 2009 08:14:27 +0200

[Martin Pitt (pitti)]

965 is not blacklisted in karmic's compiz any more:

compiz (1:0.8.2-0ubuntu12) karmic; urgency=low
 [...]
  [ Michael Vogt ]
  * debian/patches/028_compiz_manager_blacklist:
    - remove GM965 from the blacklist again, the karmic intel
      driver should work fine with it
  [...]

[Martin Pitt (pitti)]

karmic's compiz does not blacklist 965 any more either.

[Thomas Foss (tafoxx)]

What about Jaunty's Compiz?

On Mon, Jun 22, 2009 at 12:21 PM, Martin Pitt <email address hidden>wrote:

> karmic's compiz does not blacklist 965 any more either.
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “compiz” source package in Ubuntu: Fix Released
> Status in “xserver-xorg-video-intel” source package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Released
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Fix Released
> Status in compiz in Ubuntu Karmic: Fix Released
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The best method found to reproduce the bug is:
> a. Enable compiz
> b. Set your desktop to a 6x1 workspace layout
> c. Run http://launchpadlibrarian.net/25683477/repro.sh
> d. System will freeze anywhere from 1-20 min typically
> e. Power-button shutdown is required to reset the system
>
> [Regression Potential]
> In general, Virtual has been widely and extensively tested, so we do not
> expect this patch to trigger regressions.
>
> The patch is coded to only take effect on i965 systems, so the scope of any
> regression that might conceivably be triggered wi...

[reini (rrumberger)]

a) seems to be fixed, too
b) please snip - your posts are seriously hard to read with >>20
   lines

Am Montag 22 Juni 2009 schrieb Thomas Foss:
> What about Jaunty's Compiz?

Am Montag 22 Juni 2009 schrieb Launchpad Bug Tracker:
> This bug was fixed in the package compiz - 1:0.8.2-0ubuntu8.1
>
> ---------------
> compiz (1:0.8.2-0ubuntu8.1) jaunty-proposed; urgency=low
>
> * debian/patches/028_compiz_manager_blacklist: Revert change
> from 1:0.8.2-0ubuntu8 to un-blacklist GM965 (8086:2a02) again. We
> now have a better workaround in the -intel driver. (LP: #359392)
>
> -- Martin Pitt <email address hidden> Thu, 30 Apr 2009
> 08:14:27 +0200

[Oded Arbel (oded-geek)]

I opened bug #390633 for intel freeze in Karmic when doing "blank screen".

Thanks for all the help, I think this issue is resolved for Jaunty and I hope it doesn't come back for Karmic.

[nwadams (nwnadams)]

i'm using kernel 2.6.28-13-generic (so jaunty stock including updates (recommended, important))
I am also using the xserver-xorg-video-intel from the jaunty proposed repo.

I've been fine over the last 24 hours under normal usage with compiz enabled and using mostly internet, videos, some wine. No freezes, lockups, crashes, nothing.

I'm 100% sure this is unrelated but sometimes when i resume from suspend it crashes x and i have to re-log in.

Is there anything i can run with my kernel that normally causes the freezes that i can do to confirm it being fixed?

[Jonathan Blackhall (johnny-one-eye)]

> What about Jaunty's Compiz?

It's not blacklisted anymore either. I've been running a stock Jaunty
system (with nothing from proposed) and I finally got my compiz back when I
installed a bunch of updates this morning.

[jippie (jph4dotcom)]

Probably still early, I know, but after 34hrs I am still in a stable kde
desktop with a load of effects enabled :o) Before it took maybe 15 to 30
minutes to hang.
I only installed the released fixes, deleted the my manually edited
xorg.conf and rebooted ... No tests with prereleased kernels, test
patches other drivers ...

Hope this helps. Thanks guys!!

JP

Bug Watch Updater wrote:
> ** Changed in: xserver-xorg-video-intel
> Status: Confirmed => Fix Released
>
>

[filsd (filsdd)]

Hi,
First thanks for all the effort to hunt this bug. =)

Not sure if this is related to this bug, but someone using Jaunty with these updates could test the program Blender 3d (Version 2.49a) and see if these artifacts still occurs?:

http://www.trollwerks.org/BrokenBlender.png
http://i42.tinypic.com/bgww8x.jpg

They occur in the Jaunty live cd without these updates.

You can download the blender on its official site. =)

[Zachary Waldowski (zwaldowski)]

Okay, where do I go next with this bug (not here on Launchpad; this issue)? Despite it being marked "Fix Released" in both Jaunty and Karmic, I still get the freeze with stock and Xorg-Edgers drivers (on Jaunty) and on today's Daily Live CD.

[Martin Pitt (pitti)]

zwaldowski [2009-07-15 0:43 -0000]:
> Okay, where do I go next with this bug (not here on Launchpad; this
> issue)? Despite it being marked "Fix Released" in both Jaunty and
> Karmic, I still get the freeze with stock and Xorg-Edgers drivers (on
> Jaunty) and on today's Daily Live CD.

If you get it with xorg-edgers and karmic daily CDs, it's a different
issue. Can you please do the steps on
https://wiki.ubuntu.com/X/Troubleshooting/Freeze and report a new bug?

[Piscium (piscium)]

This bug is marked as fixed, however with Ubuntu Karmic Alpha 5, the 3 times I logged in, the screen froze, the first and second times about 2 minutes after login, and the third time about ten minutes after login. When this happens I have to power off the PC.

I was doing different things when the screen froze, so I do not think it was the particular action that caused the freeze. I don't know if the freeze is related to this bug. As someone wrote in the bug description, there could be different bugs that manifest in the same way (freezing).

Here is my lspci output:
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)

With respect to Ubuntu 9.04 that I currently use, things are far from perfect. Watching video streaming is difficult as the image freezes often, scrolling on Firefox is slow, and most annoying of all is that once or twice a day the gnome-panel takes up 50% of CPU time, so the panel freezes. I can often unfreeze it by killing the gnome-panel process. Note however that the gnome panel freezing is less serious than the screen freezing that I experience with Karmic Alpha 5.

António

[EddieArt (arteleb1)]

This bug has been around for a very long time now--it seems over a year and a half (not just from April because I have seen related posts dating to 2008). Why is it so hard to remedy? Is it even known if this is something wrong with the latests Ubuntu releases, latest kernels, drivers, or just s.th. wrong with the intel graphics card itself?

[Geir Ove Myhr (gomyhr)]

> This bug has been around for a very long time now--it seems over a year
> and a half (not just from April because I have seen related posts dating
> to 2008).

There are lots of different bugs that lead to the same problem -
namely that the system freezes. This particular bug report is for the
freezes that started occuring on April 3rd on many systems. This
problem has been found (the driver was reading ahead too far into
unallocated memory) and fixed. There are other bugs that can cause
this (and new bugs may be introduced), but it is not the same bug.

> Why is it so hard to remedy?

Because each bug has a different fix. They're working on a workaround
upstream that will automatically restart the GPU when it hangs, but
since that a significant chunk of new code it takes time to implement.

If you're system is experiencing freezes, file it as new bug report
with `ubuntu-bug -p xserver-xorg-video-intel`, and also provide the
information described at
https://wiki.ubuntu.com/X/Troubleshooting/Freeze (Batchbuffer stuff,
etc.)

[EddieArt (arteleb1)]

Hi Geir,

Thanks a lot for your response, even if it doesn't fix the problem.
I really appreciate your trying to help although I have a different
distribution. This goes to show how great a community you all have at
Ubuntu--which is more to than I can say right now about Mint.

By the way, do these various intel graphics cards problems effect all
Debian-based distributions or does it start only at Ubuntu?

Keep up the good work.
Peace,

Eddie

<email address hidden>

On Wed, Oct 7, 2009 at 5:08 AM, Geir Ove Myhr <email address hidden> wrote:

> > This bug has been around for a very long time now--it seems over a year
> > and a half (not just from April because I have seen related posts dating
> > to 2008).
>
> There are lots of different bugs that lead to the same problem -
> namely that the system freezes. This particular bug report is for the
> freezes that started occuring on April 3rd on many systems. This
> problem has been found (the driver was reading ahead too far into
> unallocated memory) and fixed. There are other bugs that can cause
> this (and new bugs may be introduced), but it is not the same bug.
>
> > Why is it so hard to remedy?
>
> Because each bug has a different fix. They're working on a workaround
> upstream that will automatically restart the GPU when it hangs, but
> since that a significant chunk of new code it takes time to implement.
>
> If you're system is experiencing freezes, file it as new bug report
> with `ubuntu-bug -p xserver-xorg-video-intel`, and also provide the
> information described at
> https://wiki.ubuntu.com/X/Troubleshooting/Freeze (Batchbuffer stuff,
> etc.)
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Fix Released
> Status in “compiz” package in Ubuntu: Fix Released
> Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released
> Status in compiz in Ubuntu Jaunty: Fix Released
> Status in xserver-xorg-video-intel in Ubuntu Jaunty: Fix Released
> Status in compiz in Ubuntu Karmic: Fix Released
> Status in xserver-xorg-video-intel in Ubuntu Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to repr...

[Mike.lifeguard (mikelifeguard)]

Is launchpad supposed to send me 23 emails as it just did? Might be nice to not make people CCed on the bug annoyed like this :(

[Dave Conniff (chronniff)]

I just got the same thing

[EddieArt (arteleb1)]

same here
i wonder what happened

On Tue, Feb 9, 2010 at 5:07 PM, Dave Conniff <email address hidden> wrote:

> I just got the same thing
>
> --
> [i965] X freezes starting on April 3rd
> https://bugs.launchpad.net/bugs/359392
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.org xf86-video-intel: Fix Released
> Status in “compiz” package in Ubuntu: Fix Released
> Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released
> Status in “compiz” source package in Jaunty: Fix Released
> Status in “xserver-xorg-video-intel” source package in Jaunty: Fix Released
> Status in “compiz” source package in Karmic: Fix Released
> Status in “xserver-xorg-video-intel” source package in Karmic: Fix Released
>
> Bug description:
> [Problem]
> Starting around 4/3, when mesa was upgraded from 7.3 to 7.4, several i965
> users started noticing X freeze after several hours of use, triggered by
> application usage especially noticeable with (but not unique to) compiz
> enabled.
>
> [Impact]
> The freeze bug affects a subset of i965 based systems, most particularly
> those using compiz. Exact numbers cannot be determined, but may be as high
> as 25-50% based on rough estimates.
>
> The problem is severe: An unpredictable lockup of the system that requires
> a power cycle to recover from. For some users it comes on within minutes,
> while for others it comes after a few hours of use.
>
> [How Addressed in Development Version]
> For now, the patch being proposed for Jaunty has been uploaded to Karmic.
>
> Longer term, we plan to move from EXA to UXA once the latter is stable
> enough. It has been found that while UXA exhibits other kinds of freezes,
> we've not yet been able to reproduce this particular freeze there.
>
> [Patch for Jaunty]
> A low-risk workaround that has proven effective at eliminating freezes, or
> at least greatly reducing their frequency, is to increase the Virtual
> framebuffer size. Some users do this locally as a matter of course to gain
> dual-head support, so this setting has received extremely widespread testing
> already.
>
> The patch for Jaunty causes the Virtual size to be set to 2048x2048 if it
> is not otherwise specified. Users can still override this with their own
> settings, larger or smaller, as desired.
>
> A side effect of this patch is that it also mitigates bug 158415 to a
> degree, which will make projector usage somewhat easier for this hardware
> because it will enable X to recognize higher resolutions available from the
> external monitor than were available on initial boot.
>
> [Test Case]
> The best method found to reproduce the bug is:
> a. Enable compiz
> b. Set your desktop to a 6x1 workspace layout
> c. Run http://launchpadlibrarian.net/25683477/repro.sh
> d. System will freeze anywhere from 1-20 min typically
> e. Power-button shutdown is required to reset the system
>
> [Regression Potential]
> In general, Virtual has been widely and extensively tested, so we do not
> expect this patch to trigger regressions.
>
> The patch is coded to only take effect on i965 systems, so the scope of any
> regression that might conceivably be triggered...

[Steve Langasek (vorlon)]

It would be nice indeed, but some users have gotten the idea that it's appropriate to run apport-collect against bugs unsolicited, and everyone cc:ed on the bug receives notifications of the new attachments. I'm afraid there's not much that can be done about this problem in the short term.